Reorder + rename "Info" to "About", add CDCF/SALI/FOLIO disclaimer, drop redundant Browse Projects button

[JohnRDOrazio]

Problem

Three small but related cleanups to the global header and the /info page.

1. "Info" is in the wrong place in the nav order

components/layout/header.tsx:10-15 defines the nav as:

const navLinks = [
  { href: "/", label: "Projects" },
  { href: "/info", label: "Info" },
  { href: "/docs", label: "Documentation" },
  { href: "/api-docs", label: "API Reference" },
];

"Info" is the second item, sandwiched between the most-used link (Projects) and the working docs (Documentation / API Reference). It's an "About this product" link — that's a meta-page, conventionally placed at the end of the nav, not near the top.

2. "Info" is the wrong label

"Info" is generic and slightly anonymous. "About" is the standard convention for a page that describes the product, who maintains it, and how it came about — and it scans better next to "API Reference" / "Documentation".

3. The About page should disclose maintainership and origin

The /info page (app/info/page.tsx) currently presents the product as if it sprung from nowhere. It should mention:

• The project is maintained by the Catholic Digital Commons Foundation.
• It was born out of a collaboration with SALI and FOLIO (the legal-ontology projects that motivated OntoKit's early development).
• A link to the CDCF website.

This is the right page for that context — putting it on / would clutter the projects list, putting it deeper inside Documentation makes it harder to find.

4. The "Browse Projects" button is redundant

app/info/page.tsx:21-26 renders a primary button:

<Link href="/" className="...primary-600...">
  Browse Projects
</Link>

…which duplicates the "Projects" link in the global header that's visible on every page. The CTA pair on the About page should be more like "View on GitHub" + "Visit CDCF" (the second from this issue's other ask), not "Browse Projects" + "View on GitHub".

Proposal

Header reorder + rename

 const navLinks = [
   { href: "/", label: "Projects" },
-  { href: "/info", label: "Info" },
   { href: "/docs", label: "Documentation" },
   { href: "/api-docs", label: "API Reference" },
+  { href: "/info", label: "About" },
 ];

Reading order becomes Projects → Documentation → API Reference → About — the conventional "primary action, working docs, meta" sequence.

Page route stays /info for now to avoid breaking external links; only the visible label changes. A redirect from /about → /info (or vice versa, if we choose to migrate the route too) is a follow-up if any external link to /about exists.

About page content additions

Add a "Maintainership & origins" section near the bottom of app/info/page.tsx (after the feature grid, before any footer):

<section className="mt-16 rounded-xl border border-slate-200 dark:border-slate-700 p-6">
  <h2 className="text-lg font-semibold text-slate-900 dark:text-white">
    Maintainership and origins
  </h2>
  <p className="mt-3 text-sm text-slate-600 dark:text-slate-400">
    OntoKit is maintained by the{" "}
    <a
      href="https://catholicdigitalcommons.foundation"
      target="_blank"
      rel="noopener noreferrer"
      className="text-primary-600 hover:underline dark:text-primary-400"
    >
      Catholic Digital Commons Foundation
    </a>
    . It grew out of a collaboration with the{" "}
    <a href="https://github.com/sali-legal-standards" target="_blank" rel="noopener noreferrer" className="...">
      SALI
    </a>{" "}
    /{" "}
    <a href="https://github.com/alea-institute" target="_blank" rel="noopener noreferrer" className="...">
      FOLIO
    </a>{" "}
    legal-ontology projects, which provided the early motivating use cases.
  </p>
</section>

Exact CDCF / SALI / FOLIO URLs to be confirmed during implementation; the structure above is what matters.

Replace "Browse Projects" with something About-page-appropriate

 <Link
-  href="/"
+  href="https://catholicdigitalcommons.foundation"
+  target="_blank"
+  rel="noopener noreferrer"
   className="rounded-lg bg-primary-600 px-6 py-3 text-sm font-semibold text-white..."
 >
-  Browse Projects
+  Visit CDCF
 </Link>
 <Link
   href="https://github.com/CatholicOS/ontokit-web"
   ...
 >
   View on GitHub
 </Link>

The header's "Projects" link continues to do what "Browse Projects" did — no functionality lost.

Done criteria

• Header nav reads: Projects, Documentation, API Reference, About.
• Visiting /info shows the new "About" page header label and is linked from the new "About" nav item.
• About page contains a maintainership section naming CDCF and SALI / FOLIO with valid links.
• "Browse Projects" button removed; replaced with "Visit CDCF" (or similar) primary CTA.
• No 404s from internal navigation; the /info route is unchanged.

Out of scope

• Migrating the route from /info to /about. Worth doing eventually for URL consistency with the visible label, but a next.config.ts redirect is a separate, trivial follow-up that doesn't gate this issue.
• A full org-style footer with copyright, sponsors, etc. The maintainership section in the About page is the right level of disclosure for now.
• Internationalization of the About copy. We don't i18n any other static page yet; this isn't the place to start.

Related

Other v0.5.0 polish items: #204, #205, #206, #207, #208, #209, #210. Small enough to bundle with any of them; About-page content edits are an easy companion to chrome polish.