mirror of
https://github.com/nexu-io/open-design.git
synced 2026-10-27 09:51:12 +01:00
f1a0b60c6c
* chore: unify product name display to OpenDesign repo-wide Rename the user-facing product name from "Open Design" to "OpenDesign" across documentation, web/desktop UI strings, i18n locales, prompts, plugin/skill/design-system content, changelogs, and specs, matching the landing-page rename already in flight. Deliberately excluded so installed-app identity stays untouched: - packages/release PRODUCT_NAME and everything derived from it (app bundle names, installer/registry identity, updater feeds) - tools/pack, tools/release, apps/packaged, landing page (PR #6983) - mocks/ recorded traces and LICENSE - test fixtures and comments that encode real on-disk install paths (Open Design.app, Program Files\Open Design, AppData paths) Validated with pnpm guard, pnpm typecheck, and targeted web/desktop/host test runs over the renamed strings. * fix(web): keep two-letter author monogram for CamelCase brand names authorInitials split words on whitespace only, so the renamed single-token author name "OpenDesign" produced a one-letter monogram. Treat lower-to-upper CamelCase boundaries as word breaks so the avatar fallback stays "OD". * fix(release): restore spaced Windows source artifact names in win.ps1 tools/pack still derives builder outputs from the unchanged PRODUCT_NAME ("Open Design"), so the asset script must look for the spaced filenames. Matches the mac/mac-intel/linux asset scripts, which were already kept on the original names. --------- Co-authored-by: Joey <236967869+joeylee12629-star@users.noreply.github.com>
872 B
872 B
Export To Next.js
Use this plugin when the user wants to hand an accepted OpenDesign artifact to a Next.js App Router project.
Workflow
- Decide whether the result should be a route, layout fragment, or reusable component.
- Keep components server-first unless interactivity, browser APIs, or client state require
'use client'. - Preserve the artifact's visual system while adapting image, link, font, and metadata usage to Next.js conventions.
- Prefer Tailwind CSS when the target project already supports it; otherwise keep styling local and easy to move.
- Finish with file placement notes, client/server assumptions, assets, and any data requirements.
Quality Bar
- Do not mark the whole tree as client-side unless necessary.
- Do not add framework features unrelated to the artifact handoff.
- Keep route and component boundaries easy to review.