fix: support language dynamic slug in OneNavigation

[syi0808]

Cause

The #228 issue was caused by one Navigation's link being fixed as a Korean link.
To fix this, I modified it so that It can put language dynamic plugs in the link.

📝 Key Changes

• Add language dynamic slug in ONE_NAVIGATION_ITEMS
• Create new navigationItems with dynamic slugs replaced

🖼️ Before and After Comparison

Before

issue.mov

After

2025-04-29.7.37.12.mov

Resolve #228

[vercel]

@syi0808 is attempting to deploy a commit to the Toss Team on Vercel.

A member of the Team first needs to authorize it.

[syi0808]

If we want to prevent human error with TypeScript out of necessity, we can do the following, but it seems to be too much for me personally.

type AllowedSlug = 'lang';

type ValidateDynamic<S extends string> =
  S extends `${infer _Start}{${infer Param}}${infer Rest}`
    ? Param extends AllowedSlug
      ? ValidateDynamic<Rest> extends never
        ? never
        : S
      : never
    : S;

export interface NavItem<H extends string = string> {
  path: string;
  href: ValidateDynamic<H>;
  tooltip: {
    ko: string;
    en: string;
  };
  icon: string;
}

function defineNavItem<H extends string>(
  item: Omit<NavItem<H>, 'href'> & { href: ValidateDynamic<H> }
) {
  return item as NavItem<H>;
}

const ONE_NAVIGATION_ITEMS: NavItem[] = [
  defineNavItem({
    ...

[milooy]

Thank you 👍
Can you rebase with latest main branch and check again?
Bundling Fundamental documentation is merged in only Korean.

It'll be great if we can link like this

• (Ko) One nav > Bundling Fundamentals > Real Documentation
• (!Ko) One nav > Bundling Fundamentals > Coming soon / Translation needed (in eng)

[syi0808]

@milooy I implemented the action you suggested as follows.

1. Set the bundling project to support other languages, and temporarily take action on index.md as the coming-soon page.
2. Add {lang} to the href property of the new one navigation items.

[milooy]

👍