> For the complete documentation index, see [llms.txt](https://faction-os.gitbook.io/faction-os-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faction-os.gitbook.io/faction-os-docs/.spec_system/archive/sessions/phase15-session03-blog-and-news-editorial-polish/tasks.md). # Task Checklist **Session ID**: `phase15-session03-blog-and-news-editorial-polish` **Total Tasks**: 24 **Estimated Duration**: 3-4 hours **Created**: 2026-06-01 *** ## Legend * `[x]` = Completed * `[ ]` = Pending * `[P]` = Parallelizable (can run with other \[P] tasks) * `[S1503]` = Session reference (15=phase number, 03=session number) * `TNNN` = Task ID *** ## Progress Summary | Category | Total | Done | Remaining | | -------------- | ------ | ------ | --------- | | Setup | 3 | 3 | 0 | | Foundation | 5 | 5 | 0 | | Implementation | 12 | 12 | 0 | | Testing | 4 | 4 | 0 | | **Total** | **24** | **24** | **0** | *** ## Setup (3 tasks) Initial configuration and environment preparation. * [x] T001 \[S1503] Verify public website prerequisites, package scripts, existing content schemas, route files, and seed entries before implementation (`public-website/package.json`) * [x] T002 \[S1503] Review current publishing helpers, post layout, post cards, metadata, RSS, sitemap, and draft-filtering behavior for source-backed changes (`public-website/src/lib/content.ts`) * [x] T003 \[S1503] Review current no-claim boundaries, static website rules, external demo/docs link policy, and editorial copy constraints (`.spec_system/CONSIDERATIONS.md`) *** ## Foundation (5 tasks) Core structures and base implementations. * [x] T004 \[S1503] Extend typed publishing helpers for featured/latest selection, category grouping, category summaries, previous/next neighbors, deterministic ordering, and feed categories with types matching declared contract; exhaustive enum handling (`public-website/src/lib/content.ts`) * [x] T005 \[S1503] \[P] Create featured post component for blog/news hero entries with metadata, tags, summary, accessible article link treatment, and deterministic empty-state fallback (`public-website/src/components/content/FeaturedPost.astro`) * [x] T006 \[S1503] \[P] Create category grouping component for blog/news entries with bounded static groups, deterministic ordering, text labels, and no color-only semantics (`public-website/src/components/content/CategoryGroup.astro`) * [x] T007 \[S1503] \[P] Create publishing navigation component for blog/news cross-links and previous/next article links with platform-appropriate accessibility labels, focus management, and input support (`public-website/src/components/content/PublishingNav.astro`) * [x] T008 \[S1503] Refine shared post card, metadata, tag, and related-post primitives for featured/compact/detail contexts with mobile-safe wrapping and no layout shift (`public-website/src/components/content/PostCard.astro`) *** ## Implementation (12 tasks) Main feature implementation. * [x] T009 \[S1503] Polish `/blog` index with featured post, date, reading time, tags, category, reciprocal news cross-link, and explicit empty state (`public-website/src/pages/blog/index.astro`) * [x] T010 \[S1503] Polish blog detail route wiring for related entries, previous/next navigation, draft-safe static paths, and metadata props matching declared contract (`public-website/src/pages/blog/[...slug].astro`) * [x] T011 \[S1503] Polish `/news` index with latest update, release/changelog/category grouping, RSS affordance, reciprocal blog cross-link, and explicit empty state (`public-website/src/pages/news/index.astro`) * [x] T012 \[S1503] Polish news detail route wiring for version/category treatment, related entries, previous/next navigation, draft-safe static paths, and metadata props matching declared contract (`public-website/src/pages/news/[...slug].astro`) * [x] T013 \[S1503] Update post layout for attribution, canonical/Open Graph fallback review, article footer, related section heading, and neighbor navigation slot with stable mobile layout (`public-website/src/layouts/PostLayout.astro`) * [x] T014 \[S1503] Enrich launch/product blog seed content with updated metadata, internal links, and no-overclaim product boundary language (`public-website/src/content/blog/introducing-factionos.md`) * [x] T015 \[S1503] Enrich local-first architecture blog seed content with cross-links to security/docs and explicit no-analytics/no-hosted-default language (`public-website/src/content/blog/local-first-agent-observability.md`) * [x] T016 \[S1503] Enrich cockpit field-notes blog seed content with product/use-case links, readable headings, and no real-executor implication (`public-website/src/content/blog/why-agent-work-needs-a-cockpit.md`) * [x] T017 \[S1503] \[P] Create gamification design seed post covering battlefield/cockpit design with frontmatter, tags, category, and static product-boundary copy (`public-website/src/content/blog/battlefield-cockpit-design.md`) * [x] T018 \[S1503] \[P] Create technical explainer seed post covering hook events to cockpit flow with frontmatter, tags, category, and local-first data-boundary copy (`public-website/src/content/blog/hook-events-to-cockpit.md`) * [x] T019 \[S1503] \[P] Create publishing polish news seed update covering release and changelog categories without production-hosted validation or analytics claims (`public-website/src/content/news/website-publishing-polish.md`) * [x] T020 \[S1503] \[P] Create public-site expansion news seed update covering company and press-style categories without legal or investor claims (`public-website/src/content/news/factionos-public-site-expands.md`) *** ## Testing (4 tasks) Verification and quality assurance. * [x] T021 \[S1503] Run package typecheck and resolve any Astro or TypeScript errors from helpers, route props, content frontmatter, and component contracts (`public-website/package.json`) * [x] T022 \[S1503] Run static website build and inspect built blog/news pages, article pages, `rss.xml`, and sitemap output for non-draft entries, draft exclusion, metadata, route links, and deterministic ordering (`public-website/dist/rss.xml`) * [x] T023 \[S1503] Manually smoke desktop, tablet, 360px mobile, keyboard focus, metadata wrapping, tag wrapping, category groups, featured posts, previous/next links, RSS link, and external demo/docs links (`public-website/src/pages/blog/index.astro`) * [x] T024 \[S1503] Validate ASCII encoding, Unix LF line endings, absence of analytics/tracker/form/runtime-fetch code, and editorial no-claim copy guardrails (`public-website/src/content/blog/introducing-factionos.md`) *** ## Completion Checklist Before marking session complete: * [x] All tasks marked `[x]` * [x] All tests passing * [x] All files ASCII-encoded * [x] implementation-notes.md updated * [x] Ready for the validate workflow step *** ## Next Steps Run the implement workflow step to begin AI-led implementation. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://faction-os.gitbook.io/faction-os-docs/.spec_system/archive/sessions/phase15-session03-blog-and-news-editorial-polish/tasks.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.