MapleMarine.aiNexus · Public Ecosystem

Ecosystem standards · v1.0

One ecosystem. One standard. Mirrored across every property.

This page is the single reference for the shared design system, naming conventions, CTA vocabulary, navigation patterns, brand voice, structured data, and SEO governance every public property in the MapleMarine.ai ecosystem must mirror. Identity and workspace access live on /identity; the surface directory lives on /portal.

Request Advisory Support

Paired reference · Directory

Corporate + Ecosystem Portal

Executive overview of MapleMarine surfaces and the public directory of every destination on Nexus.

Paired reference · Architecture

Workspace Access Strategy

How identity, billing, SSO and access governance map between Nexus and the Secure Workspace.

Design system

Shared enterprise design language

Tokens defined in src/styles.css. Every component consumes semantic tokens — no hard-coded colors anywhere in the ecosystem.

Typography

Inter (body), Poppins & Montserrat (display per platform), IBM Plex Mono (metrics). Tracking −0.02em on display.

Color & tokens

All color access via semantic tokens in src/styles.css (oklch). Per-platform brand gradients are pre-defined utilities.

CTAs & buttons

Canonical <CTA> primitive: primary (foreground pill), secondary (outlined card pill), tertiary (uppercase link), dark (accent pill on navy). One label vocabulary across all properties.

Iconography

Lucide-react only, 16/20 px stroke 1.5. No emoji in interface chrome.

Trust & hierarchy

Maritime navy gradient hero, executive spacing rhythm (py-20 md:py-28), shadow-elegant on premium cards.

Responsive grid

container-x (max 1280px). Mobile 1-col → md 2-col → lg 3/4-col. Header collapses to drawer < lg.

Naming

Canonical names

Use these exact strings. Do not abbreviate, translate or invent variants.

  • MapleMarine Nexus

    Public ecosystem hub at maplemarine.ai. Always two words.

  • Secure Workspace

    Authenticated workspace at app.maplemarine.ai. Never 'App', 'Portal', or 'Dashboard'.

  • ShipyardMaster.ai

    Flagship enterprise platform. Always with .ai suffix, no space.

  • WeldMaster+

    Welding / NDT / compliance platform. Always with the trailing +.

  • Maritime Intelligence Radar

    Intelligence product surfaced as preview on Nexus, full version on Workspace.

CTAs

Standard CTA vocabulary

A single set of labels and behaviors used across every property.

  • Launch Workspace

    Header & primary CTA across Nexus → app.maplemarine.ai.

  • Open Secure Workspace

    Card-level CTA on intelligence previews and gated content.

  • Explore ShipyardMaster.ai

    Cross-link to flagship enterprise platform.

  • Explore WeldMaster+

    Cross-link to welding/NDT/compliance platform.

  • Request Advisory Support

    Lead-generation CTA → /contact for consulting engagements.

SEO governance

Discoverability standards

Every public route in the ecosystem follows the same metadata, canonical and structured-data conventions.

Canonical consistency

Every route emits a canonical link via buildPageMeta() in src/lib/ecosystem.ts.

Sitemap & robots

Auto-generated /sitemap.xml and /robots.txt list every public route on maplemarine.ai.

Structured data

JSON-LD Organization graph on root; per-page Article/Product schema on intelligence and solution detail routes.

AI-search optimization

Plain-language H1s, semantic naming, and entity-rich descriptions to support AI answer engines.

Brand language

Voice, tone, and writing standards

Executive, maritime, technically credible. Avoid hype. Lead with outcomes, not features.

Voice

Confident, precise, operator-grade. Plain English, no jargon stacks.

Tone

Trust-first. Frame capability through compliance, safety, and measurable outcomes.

Vocabulary

'Workspace' (not app), 'briefing' (not post), 'fleet/yard' (not asset). Use the glossary above.

Numbers & units

IBM Plex Mono for metrics, tabular numerals (font-num). SI units; ISO date format.

Structured data standards

JSON-LD on every public route. Root emits an Organization graph with the ecosystem's sameAs links. Detail pages add Product, Article or BreadcrumbList as appropriate.

  • • Use absolute URLs derived from SITE_URL.
  • • Validate with Google Rich Results before publish.
  • • Mirror Organization name, logo, sameAs across every property.

Workspace redirects

Public previews on Nexus deep-link to the Secure Workspace using a single canonical URL. Future redirects must include a redirect_uri back to the originating Nexus page after authentication.

  • • Source: any preview card or hero CTA on Nexus.
  • • Target: https://app.maplemarine.ai/
  • • Always target="_blank" rel="noopener noreferrer".
  • • Use the <LaunchWorkspaceButton /> component, never hand-rolled anchors.

Paired reference · Architecture

Workspace Access Strategy

How identity, billing, SSO and access governance map between Nexus and the Secure Workspace.

Paired reference · Directory

Corporate + Ecosystem Portal

Executive overview of MapleMarine surfaces and the public directory of every destination on Nexus.

Nexus QA checklist

Validated within MapleMarine Nexus only. Other properties run their own QA against this same standard.

  • All Launch Workspace CTAs resolve to app.maplemarine.ai
  • Header/Footer architecture identical across every Nexus route
  • Naming matches the canonical glossary on every page
  • Per-route head() emits unique title, description and canonical
  • Sitemap.xml lists every public Nexus route
  • Robots.txt allows crawling and references the sitemap
  • Mobile, tablet and desktop layouts validated on each route
  • Cross-platform links use the URLs in src/lib/ecosystem.ts
  • JSON-LD Organization graph present on root
  • No workspace-only features (auth, billing, exports) on Nexus

MapleMarine Nexus governance · this page is the single reference. Future ecosystem apps must mirror these standards; this project does not modify app.maplemarine.ai, shipyardmaster.ai or weldmaster.maplemarine.ai.