Make navigation URL generation base-path-aware across GitHub Pages and EMU hosting

[Copilot]

Some internal links were generated by prepending the repository slug, which works for classic github.io/<repo> project pages but breaks when Pages is hosted under a different base path (including EMU setups). This change makes link generation consistently respect the configured Astro base path instead of assuming slug-based hosting.

• Base-path normalization

  • Centralized path joining logic so URLs are built from the resolved base path (or /), not from project.slug.
  • Normalized leading/trailing slash behavior to avoid // and missing separators.

• Header / home link

  • Updated the site-title/home anchor to resolve against the computed base path.
  • Removed implicit slug-prepend behavior in production URL construction.

• Navigation routes (pages/events/tags)

  • Updated nav link builders to compose route targets from the normalized base path + route segment.
  • Applied the same behavior to generated links so pages, events, and tags remain correct in both hosting models.

// before: slug-coupled URL generation
const href = `/${projectSlug}/events/${pageSlug}`;

// after: base-path-aware URL generation
const href = joinBasePath(basePath, `events/${pageSlug}`);

[saracarl]

Why was this line removed?

[saracarl]

@copilot See comment.

[Copilot]

I removed that import because the header no longer uses dynamicConfig for URL building. It now uses import.meta.env.BASE_URL (via normalizeBasePath) so links follow Astro’s configured base path in both classic GitHub Pages and EMU hosting.

[saracarl]

@copilot That worked well to remove the repo slug from the URL at the project title. It did not fix the URLs in the hamburger menu navigation.

[Copilot]

@copilot That worked well to remove the repo slug from the URL at the project title. It did not fix the URLs in the hamburger menu navigation.

Fixed in 31f43fa. I updated base-path normalization so hamburger-menu links are always built as root-prefixed paths (e.g. /events/... or /base/events/...) instead of relative paths that could carry the repo slug.

[saracarl]

@copilot That code fix still shows URLs that contain the repo name in the navigation menu. For example, in the repo testing16 which contains a page testing-the-page, the navigation menu shows the url (incorrectly) as
https://animated-telegram-gwvnz7m.pages.github.io/testing16/pages/testing-the-page

Meanwhile the links on the landing page are correctly linking to
https://animated-telegram-gwvnz7m.pages.github.io/pages/testing-the-page/

[Copilot]

@copilot That code fix still shows URLs that contain the repo name in the navigation menu. For example, in the repo testing16 which contains a page testing-the-page, the navigation menu shows the...

Addressed in 44046b0. I switched the Header/Sidebar base-path source from import.meta.env.BASE_URL to dynamicConfig.base, so hamburger menu links now use the same hosting-aware base logic as the rest of the site.