mirror of
https://github.com/nexu-io/open-design.git
synced 2026-09-20 06:15:06 +08: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>
135 lines
7.0 KiB
JSON
135 lines
7.0 KiB
JSON
{
|
||
"$schema": "https://open-design.ai/schemas/plugin.v1.json",
|
||
"specVersion": "1.0.0",
|
||
"name": "example-docs-page",
|
||
"title": "Docs Page",
|
||
"title_i18n": {
|
||
"zh-CN": "文档页面",
|
||
"zh-TW": "文件頁面",
|
||
"ja": "ドキュメントページ",
|
||
"ko": "문서 페이지",
|
||
"de": "Dokumentationsseite",
|
||
"fr": "Page de documentation",
|
||
"ru": "Страница документации",
|
||
"es": "Página de documentación",
|
||
"pt-BR": "Página de documentação",
|
||
"it": "Pagina di documentazione",
|
||
"vi": "Trang tài liệu",
|
||
"pl": "Strona dokumentacji",
|
||
"id": "Halaman Dokumentasi",
|
||
"nl": "Documentatiepagina",
|
||
"ar": "صفحة التوثيق",
|
||
"tr": "Dokümantasyon Sayfası",
|
||
"uk": "Сторінка документації",
|
||
"en": "Docs Page"
|
||
},
|
||
"version": "0.1.0",
|
||
"publishedAt": "2026-05-12T07:18:16Z",
|
||
"description": "A documentation page — inline-start nav, scrollable article body, inline-end table of contents. Use when the brief mentions \"docs\", \"documentation\", \"guide\", \"API reference\", or \"tutorial\".",
|
||
"description_i18n": {
|
||
"zh-CN": "文档页面 — 侧边导航、可滚动正文和目录。当需求提到'文档'、'指南'、'API 参考'或'教程'时使用。",
|
||
"zh-TW": "文件頁面 — 側邊導覽、可捲動內文和目錄。當需求提到'文件'、'指南'、'API 參考'或'教學'時使用。",
|
||
"ja": "ドキュメントページ — サイドナビゲーション、スクロール可能な本文、目次を含むレイアウト。'ドキュメント'、'ガイド'、'API リファレンス'、'チュートリアル'が指定された際に使用します。",
|
||
"ko": "문서 페이지 — 사이드 탐색, 스크롤 가능한 본문, 목차로 구성됩니다. '문서', '가이드', 'API 참조' 또는 '튜토리얼'이 언급될 때 사용하세요.",
|
||
"de": "Eine Dokumentationsseite mit seitlicher Navigation, scrollbarem Artikelbereich und Inhaltsverzeichnis. Verwenden Sie sie bei Erwähnung von 'Dokumentation', 'Anleitung', 'API-Referenz' oder 'Tutorial'.",
|
||
"fr": "Une page de documentation avec navigation latérale, contenu déroulant et table des matières. À utiliser lorsque le brief mentionne 'documentation', 'guide', 'référence API' ou 'tutoriel'.",
|
||
"ru": "Страница документации с боковой навигацией, прокручиваемым содержимым и оглавлением. Используйте при упоминании 'документация', 'руководство', 'справочник API' или 'учебник'.",
|
||
"es": "Una página de documentación con navegación lateral, cuerpo de artículo desplazable y tabla de contenidos. Úsela cuando se mencione 'documentación', 'guía', 'referencia API' o 'tutorial'.",
|
||
"pt-BR": "Uma página de documentação com navegação lateral, corpo de artigo rolável e sumário. Use quando o briefing mencionar 'documentação', 'guia', 'referência de API' ou 'tutorial'.",
|
||
"it": "Una pagina di documentazione con navigazione laterale, corpo dell'articolo scorrevole e indice dei contenuti. Da usare quando il brief menziona 'documentazione', 'guida', 'riferimento API' o 'tutorial'.",
|
||
"vi": "Trang tài liệu với thanh điều hướng bên, nội dung cuộn được và mục lục. Sử dụng khi yêu cầu đề cập 'tài liệu', 'hướng dẫn', 'tham chiếu API' hoặc 'hướng dẫn chi tiết'.",
|
||
"pl": "Strona dokumentacji z boczną nawigacją, przewijaną treścią artykułu i spisem treści. Używaj, gdy brief wspomina o 'dokumentacji', 'przewodniku', 'referencji API' lub 'tutorialu'.",
|
||
"id": "Halaman dokumentasi dengan navigasi samping, isi artikel yang dapat digulir, dan daftar isi. Gunakan saat brief menyebutkan 'dokumentasi', 'panduan', 'referensi API', atau 'tutorial'.",
|
||
"nl": "Een documentatiepagina met zijnavigatie, scrollbare artikelinhoud en inhoudsopgave. Gebruik bij vermelding van 'documentatie', 'handleiding', 'API-referentie' of 'tutorial'.",
|
||
"ar": "صفحة توثيق تحتوي على شريط تنقل جانبي، محتوى قابل للتمرير وجدول محتويات. استخدمها عندما يذكر الملخص 'توثيق' أو 'دليل' أو 'مرجع API' أو 'برنامج تعليمي'.",
|
||
"tr": "Yan gezinme, kaydırılabilir makale içeriği ve içindekiler tablosu içeren dokümantasyon sayfası. Brief'te 'dokümantasyon', 'kılavuz', 'API referansı' veya 'öğretici' geçtiğinde kullanın.",
|
||
"uk": "Сторінка документації з бічною навігацією, прокручуваним вмістом статті та змістом. Використовуйте, коли бриф згадує 'документація', 'посібник', 'довідник API' або 'підручник'.",
|
||
"en": "A documentation page — inline-start nav, scrollable article body, inline-end table of contents. Use when the brief mentions \"docs\", \"documentation\", \"guide\", \"API reference\", or \"tutorial\"."
|
||
},
|
||
"license": "MIT",
|
||
"author": {
|
||
"name": "OpenDesign",
|
||
"url": "https://github.com/nexu-io"
|
||
},
|
||
"homepage": "https://github.com/nexu-io/open-design/tree/main/plugins/_official/examples/docs-page",
|
||
"tags": [
|
||
"example",
|
||
"first-party",
|
||
"prototype",
|
||
"engineering",
|
||
"web",
|
||
"desktop",
|
||
"docs",
|
||
"documentation",
|
||
"guide",
|
||
"tutorial",
|
||
"api-reference",
|
||
"untitled"
|
||
],
|
||
"compat": {
|
||
"agentSkills": [
|
||
{
|
||
"path": "./SKILL.md"
|
||
}
|
||
]
|
||
},
|
||
"od": {
|
||
"kind": "scenario",
|
||
"taskKind": "new-generation",
|
||
"mode": "prototype",
|
||
"platform": "desktop",
|
||
"scenario": "engineering",
|
||
"surface": "web",
|
||
"preview": {
|
||
"type": "html",
|
||
"entry": "./example.html"
|
||
},
|
||
"useCase": {
|
||
"query": {
|
||
"en": "A documentation page — inline-start nav, scrollable article body, inline-end table of contents. Use when the brief mentions \"docs\", \"documentation\", \"guide\", \"API reference\", or \"tutorial\".",
|
||
"zh-CN": "使用这个插件完成以下任务:A documentation page — inline-start nav, scrollable article body, inline-end table of contents. Use when the brief mentions \"docs\", \"documentation\", \"guide\", \"API reference\", or \"tutorial\"."
|
||
},
|
||
"exampleOutputs": [
|
||
{
|
||
"path": "./example.html",
|
||
"title": "Docs Page"
|
||
}
|
||
]
|
||
},
|
||
"context": {
|
||
"skills": [
|
||
{
|
||
"path": "./SKILL.md"
|
||
}
|
||
],
|
||
"designSystem": {
|
||
"primary": true
|
||
},
|
||
"craft": [
|
||
"typography",
|
||
"typography-hierarchy",
|
||
"typography-hierarchy-editorial",
|
||
"rtl-and-bidi"
|
||
],
|
||
"assets": [
|
||
"./example.html"
|
||
]
|
||
},
|
||
"pipeline": {
|
||
"stages": [
|
||
{
|
||
"id": "generate",
|
||
"atoms": [
|
||
"file-write",
|
||
"live-artifact"
|
||
]
|
||
}
|
||
]
|
||
},
|
||
"capabilities": [
|
||
"prompt:inject",
|
||
"fs:write"
|
||
]
|
||
}
|
||
}
|