Files
Joey-nexu f1a0b60c6c chore: unify product name display to OpenDesign repo-wide (#6998)
* 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>
2026-08-18 07:09:45 +00:00

1.3 KiB

name, description, triggers, od
name description triggers od
od-plugin-publish-github Publish a local OpenDesign plugin to a new public GitHub repository using gh CLI.
publish plugin
github repo
open source plugin
mode platform scenario
utility desktop plugin-sharing

Publish Plugin to GitHub

Use this workflow when the active project contains a copied plugin folder and the user wants it published as a new public GitHub repository.

Workflow

  1. Read the active plugin inputs. plugin_context_path is the copied plugin folder relative to the project working directory.
  2. Inspect open-design.json, SKILL.md, and any compatibility metadata in the copied folder.
  3. Call the local daemon endpoint instead of hand-rolling GitHub commands: curl -sS -X POST "$OD_DAEMON_URL/api/projects/$OD_PROJECT_ID/plugins/publish-github" -H 'content-type: application/json' -d '{"path":"<plugin_context_path>"}'
  4. Read the JSON response. If ok is true, report the final repository URL and any useful log/validation summary.
  5. If the endpoint fails, report its message, code, and useful log lines. When authentication is missing, tell the user to run gh auth login --hostname github.com.

Prefer the manifest name as the repository slug. If that repository already exists, choose the next clear slug and mention the rename.