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

112 lines
4.3 KiB
JSON
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
{
"$schema": "https://open-design.ai/schemas/plugin.v1.json",
"specVersion": "1.0.0",
"name": "example-html-ppt-graphify-dark-graph",
"title": "Write a Feature Business Case like a Principal PM",
"title_i18n": {
"en": "Write a Feature Business Case like a Principal PM",
"zh-CN": "像 Principal PM 一样写功能商业论证",
"zh-TW": "像 Principal PM 一样写功能商业论证"
},
"version": "0.1.0",
"publishedAt": "2026-05-12T07:18:16Z",
"description": "OpenDesign's feature business case for the plugin marketplace: the user pain, options, tradeoffs, and the measure of success. Built as a decision-grade product management deck for PM, eng, design, leadership.",
"description_i18n": {
"en": "OpenDesign's feature business case for the plugin marketplace: the user pain, options, tradeoffs, and the measure of success. Built as a decision-grade product management deck for PM, eng, design, leadership.",
"zh-CN": "像 Principal PM 一样写功能商业论证——一份可商业交付的产品管理 Deck,围绕真实主题、证据链与决策目标组织。",
"zh-TW": "像 Principal PM 一样写功能商业论证——一份可商业交付的产品管理 Deck,围绕真实主题、证据链与决策目标组织。"
},
"license": "MIT",
"author": {
"name": "OpenDesign",
"url": "https://github.com/nexu-io"
},
"homepage": "https://github.com/nexu-io/open-design/tree/main/plugins/_official/examples/html-ppt-graphify-dark-graph",
"tags": [
"example",
"first-party",
"deck",
"engineering",
"web",
"untitled",
"graph-deck",
"dark-graph",
"dev-tool-launch",
"cli-launch",
"data-viz-launch",
"ai",
"copilot",
"workflow",
"html-ppt-graphify-dark-graph",
"enterprise-ai-literacy",
"product-management",
"pm-feature-business-case-deck",
"product",
"roadmap",
"architecture",
"decision-deck",
"commercial-slide-agent"
],
"compat": {
"agentSkills": [
{
"path": "./SKILL.md"
}
]
},
"od": {
"kind": "scenario",
"taskKind": "new-generation",
"mode": "deck",
"scenario": "product",
"surface": "web",
"preview": {
"type": "html",
"entry": "./example.html"
},
"useCase": {
"query": {
"en": "Create \"Write a Feature Business Case like a Principal PM\" as a decision-grade Product management deck in this template's own visual system. Subject: OpenDesign's feature business case for the plugin marketplace: the user pain, options, tradeoffs, and the measure of success. Audience: PM, eng, design, leadership. First ask only for missing essentials: audience, decision target, source-of-truth materials, deadline, and must-keep numbers. Then produce the slide plan, written slides, visual direction, speaker-ready structure, and a critic pass against this rubric: can cross-functional reviewers agree on the next irreversible step.",
"zh-CN": "像 Principal PM 一样写功能商业论证。像 Principal PM 一样写功能商业论证——一份可商业交付的产品管理 Deck,围绕真实主题、证据链与决策目标组织。 主题:OpenDesign's feature business case for the plugin marketplace: the user pain, options, tradeoffs, and the measure of success. 先确认受众、决策目标、素材来源、截止时间和必须保留的数据,再输出叙事主线、页面规划、逐页文案、视觉方向和按评审标准自检的版本。"
},
"exampleOutputs": [
{
"path": "./example.html",
"title": "Write a Feature Business Case like a Principal PM",
"title_i18n": {
"en": "Write a Feature Business Case like a Principal PM",
"zh-CN": "像 Principal PM 一样写功能商业论证",
"zh-TW": "像 Principal PM 一样写功能商业论证"
}
}
]
},
"context": {
"skills": [
{
"path": "./SKILL.md"
}
],
"assets": [
"./example.html"
]
},
"pipeline": {
"stages": [
{
"id": "generate",
"atoms": [
"file-write",
"live-artifact"
]
}
]
},
"capabilities": [
"prompt:inject",
"fs:write"
],
"category": "product-management"
}
}