Skip to content

docs(pages): add current product documentation hub - #650

Closed
seonghobae wants to merge 2 commits into
developfrom
docs/pages-product-hub
Closed

docs(pages): add current product documentation hub#650
seonghobae wants to merge 2 commits into
developfrom
docs/pages-product-hub

Conversation

@seonghobae

@seonghobae seonghobae commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

Superseded by canonical README/public-surface lane

Closed without merge after preserving the complete unique delta in #651.

  • docs/index.html from this branch is now present on docs/readme-product-first-20260902;
  • the Pages staging update that publishes docs/index.html, docs/user-guide.md, docs/api.md, docs/deploy.md, and docs/security.md is also present there;
  • ScopeWeave's existing Actions-based GitHub Pages deployment model remains intact;
  • no application/runtime/authentication/persistence/dependency/repository-settings behavior was discarded.

Canonical successor: #651 exact head 62dfd3523428ef4aba47964b19ae9f5cadb423eb at closure. It owns the product-first root README and the deployable public documentation hub together, eliminating drift between separate README and Pages writers.

This closure itself is not merge evidence for #651; the successor must reacquire all exact-head checks/reviews after the fold.

@seonghobae seonghobae added the documentation Improvements or additions to documentation label Sep 1, 2026 — with ChatGPT Codex Connector

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Devin Review found 2 potential issues.

Devin Review

Comment thread docs/index.html
Comment on lines +46 to +49
<a class="card" href="user-guide.md"><strong>User guide</strong><span>Plan, edit, analyze, import/export, and use the planner.</span></a>
<a class="card" href="api.md"><strong>API reference</strong><span>Cloud/SaaS endpoints and integration contracts.</span></a>
<a class="card" href="deploy.md"><strong>Deployment guide</strong><span>Runtime configuration and deployment boundaries.</span></a>
<a class="card" href="security.md"><strong>Security notes</strong><span>Authentication, tenancy, secrets, and fail-closed expectations.</span></a>

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Documentation cards expose raw Markdown

The four cards link to .md files in an unprocessed Pages artifact. Browsers display Markdown source instead of rendered product documentation.

Prompt for agents
The documentation hub in docs/index.html links directly to docs/user-guide.md, docs/api.md, docs/deploy.md, and docs/security.md. The Pages workflow uploads _site as a static artifact and performs no Markdown-to-HTML build, so these URLs expose source Markdown. Add a rendering step that produces HTML for these documents and update the cards to those outputs, or link to an existing renderer such as the repository's GitHub blob pages. Ensure all generated files are included in the uploaded artifact and relative links continue to work under the /scopeweave/docs/ project path.
Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

Comment thread docs/index.html
Comment on lines +8 to +24
<style>
:root { color-scheme: light dark; font-family: Inter, ui-sans-serif, system-ui, -apple-system, BlinkMacSystemFont, "Segoe UI", sans-serif; }
body { margin: 0; line-height: 1.6; }
main { max-width: 920px; margin: 0 auto; padding: 48px 24px 72px; }
h1 { font-size: clamp(2.2rem, 7vw, 4.6rem); line-height: 1; margin: 0 0 20px; letter-spacing: -0.04em; }
h2 { margin-top: 42px; }
.lede { font-size: 1.18rem; max-width: 760px; }
.status { border-left: 4px solid currentColor; padding: 12px 16px; margin: 28px 0; opacity: .86; }
.grid { display: grid; grid-template-columns: repeat(auto-fit, minmax(230px, 1fr)); gap: 14px; margin: 22px 0; }
.card { display: block; border: 1px solid currentColor; border-radius: 14px; padding: 18px; text-decoration: none; }
.card strong { display: block; margin-bottom: 6px; }
.card span { opacity: .75; }
.actions { display: flex; flex-wrap: wrap; gap: 12px; margin: 28px 0; }
.actions a { border: 1px solid currentColor; border-radius: 999px; padding: 9px 14px; text-decoration: none; }
code { font-family: ui-monospace, SFMono-Regular, Menlo, Consolas, monospace; }
footer { margin-top: 56px; opacity: .72; font-size: .95rem; }
</style>

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔍 Documentation hub embeds its stylesheet

The <style> block bypasses the repository rule to extend styles.css. Move these rules into a staged stylesheet to keep client presentation centralized.

Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

@seonghobae seonghobae added priority: medium Normal-priority or P2 work status: needs-review Open pull request requiring current-head review or checks labels Sep 1, 2026 — with ChatGPT Codex Connector
@seonghobae seonghobae closed this Sep 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation priority: medium Normal-priority or P2 work status: needs-review Open pull request requiring current-head review or checks

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant