docs(site): refine SDD messaging and overhaul comparison page (#49)

* fix(docs): overhaul comparison page with balanced competitor analysis

Rewrite comparison page with factual, balanced competitor analysis.
Add specific competitor details, fix comparison table links, and
update CSS styles for improved table readability.

* docs(site): refine SDD workflow messaging across site pages

Emphasize SDD as a teachable workflow and refine messaging across
common questions, developer experience, index, reference materials,
and video overview pages for clarity and consistency.

* docs(site): refine comparison page external references

Add safe external-link attributes, normalize HTML code markup, and expand the bottom-line section with broader context about alternative structured development frameworks.

Co-Authored-By: AI Assistant <no-reply@example.com>

* docs(site): refresh docs page layouts and styling

Improve the public documentation pages so key workflow sections are easier to scan and page-specific content feels more intentional. This keeps the docs site visually consistent while making supporting examples and structure explanations clearer.

Co-Authored-By: OpenCode <no-reply@example.com>

* docs(site): add next-step navigation across docs pages

Connect the public docs pages with clearer next actions and tighten supporting page presentation so readers can move through the workflow story more naturally. This improves the docs site's flow without changing the underlying content model.

Co-Authored-By: OpenCode <no-reply@example.com>

* docs(site): emphasize spec-first workflow across docs

Add reference material links and tighten site copy around the cspell example so visitors can inspect the workflow directly. Reinforce why specification and task breakdown do the highest-leverage work before implementation begins.

Co-Authored-By: OpenCode <no-reply@example.com>

* docs(site): clarify spec lifecycle across workflow pages

Explain where SDD fits in the broader delivery process so specs, tasks, and proofs are understood as implementation-time scaffolding instead of permanent product docs. Also tune the homepage section styling so the new lifecycle framing reads cleanly within the site's visual rhythm.

Co-Authored-By: OpenCode <no-reply@example.com>

---------

Co-authored-by: AI Assistant <no-reply@example.com>

Author: ryderstorm