seemore 1.10.5 → 1.10.7

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "seemore",
-  "version": "1.10.5",
+  "version": "1.10.7",
   "description": "Let AI write the Markdown. Let seemore show it better — zero config documentation framework.",
   "license": "MIT",
   "type": "module",

package/src/app/styles/globals.css

@@ -476,9 +476,11 @@
   }
 
   /* Page actions: the row above the article holding the export dropdown. Right-aligned so
-     it reads as chrome, not content, and stays clear of the heading it hangs over. */
+     it reads as chrome, not content, and stays clear of the heading it hangs over. No
+     bottom margin: the main column's own `gap-10` already separates it from the article,
+     and a margin here would stack on top of that gap. */
   .seemore-page-actions {
-    @apply relative mb-4 flex justify-end;
+    @apply relative flex justify-end;
   }
 
   .seemore-page-actions-trigger {
@@ -494,6 +496,19 @@
     @apply size-4;
   }
 
+  /* Mobile: the row's trigger padding reads as wasted space on a phone, and the column's
+     `gap-10` is generous for a viewport this small — tighten both below the `md`
+     breakpoint, where the TOC rail is hidden and this row is pure chrome. */
+  @media (max-width: 767.98px) {
+    .seemore-page-actions-trigger {
+      @apply px-2.5 py-1;
+    }
+
+    .seemore-main {
+      @apply gap-6;
+    }
+  }
+
   /* `top-full` is load-bearing: without it the menu keeps its static position, which in this
      flex row is beside the trigger rather than under it, so it opens over its own button. */
   .seemore-page-actions-menu {

package/src/shared/base.ts

@@ -25,6 +25,16 @@ export function isExternalHref(href: string): boolean {
   return EXTERNAL.test(href) || href.startsWith('#') || !href.startsWith('/');
 }
 
+/**
+ * True only for an href that points off this site: one with a scheme (`https:`, `mailto:`)
+ * or protocol-relative (`//host/path`). Narrower than {@link isExternalHref}, which also
+ * covers relative and hash hrefs because a base must not touch those either — a distinction
+ * that matters wherever a relative path and a remote URL have to be told apart.
+ */
+export function isRemoteHref(href: string): boolean {
+  return EXTERNAL.test(href);
+}
+
 /** Prefix a root-relative path with the base. Idempotent; leaves external hrefs alone. */
 export function withBase(base: string, href: string): string {
   const b = normaliseBase(base);