Skip to content

docs: add 'The stack' narrative + fix site deploy (exclude planning docs)#14

Merged
lesnik512 merged 1 commit into
mainfrom
docs/stack-page
Jun 24, 2026
Merged

docs: add 'The stack' narrative + fix site deploy (exclude planning docs)#14
lesnik512 merged 1 commit into
mainfrom
docs/stack-page

Conversation

@lesnik512

Copy link
Copy Markdown
Member

Adds — "The stack" narrative

An equal-billing section on the org landing page telling the how-it-fits-together story for building a production Python service:
template → modern-dihttpwarefaststream-outboxlite-bootstrap, each with a sharp pitch. Written as new prose so it does not drift from the canonical repo descriptions in the directory lists below it.

Fixes — site deploy was broken

.github/workflows/deploy.yml runs mkdocs build --strict. The strategy spec + plans under docs/superpowers/ contain repo-relative links (e.g. CODE_OF_CONDUCT.md) that mkdocs can't resolve, so strict build — and the Pages deploy — has been failing since those docs were added (PR #13). They were also being published to modern-python.org, which is undesirable for internal planning docs.

Fix: add superpowers/ to exclude_docs. The files stay in the repo (version-controlled planning) but are no longer built or published.

Verified: mkdocs build --strict passes; site/superpowers/ is gone; the stack section renders.

Adds an equal-billing 'how it fits together' section to the org landing
page (templates -> modern-di -> httpware -> faststream-outbox ->
lite-bootstrap), with sharp per-project pitches in new prose.

Also excludes docs/superpowers/ (strategy specs + plans) from the site
build. Those files contain repo-relative links that broke
'mkdocs build --strict' — and therefore the Pages deploy — since they
were added, and they are internal planning docs that shouldn't be public.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@lesnik512 lesnik512 merged commit 2f03259 into main Jun 24, 2026
@lesnik512 lesnik512 deleted the docs/stack-page branch June 24, 2026 15:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant