coilysiren/website

Watch

Surface /writing/ from the homepage #98

New issue

Closed

opened 2026-08-10 20:08:02 +00:00 by coilyco-ops · 1 comment

coilyco-ops commented

2026-08-10 20:08:02 +00:00

Collaborator

Context

src/writing.njk builds a real page at /writing/, but src/index.njk contains no link to it and the page is noindex, nofollow. The writing surface is effectively unreachable except by someone who already knows the URL.

Required outcome

Once the promotion flag lands and /writing/ lists the three promoted posts, the homepage links to it so a first-time visitor can find the writing.

Acceptance criteria

src/index.njk links to /writing/ in a placement consistent with the existing portfolio-first composition.
The link does not disturb the hero or the Active portfolio section's role as the primary subject.
The navigation treatment matches the existing about / hiring / resume pattern rather than introducing a new one.
ward exec build, ward exec lint, and ward exec pre-commit-all pass.
Cypress smoke still passes.

Dependencies

Blocked on the promotion-flag issue. Linking to a nine-post noindex listing is not the intended end state.

Non-goals

Homepage visual redesign. Issue #93 owns hierarchy decisions.
Adding post teasers or excerpts to the homepage itself.

## Context `src/writing.njk` builds a real page at `/writing/`, but `src/index.njk` contains no link to it and the page is `noindex, nofollow`. The writing surface is effectively unreachable except by someone who already knows the URL. ## Required outcome Once the promotion flag lands and `/writing/` lists the three promoted posts, the homepage links to it so a first-time visitor can find the writing. ## Acceptance criteria * `src/index.njk` links to `/writing/` in a placement consistent with the existing portfolio-first composition. * The link does not disturb the hero or the Active portfolio section's role as the primary subject. * The navigation treatment matches the existing `about` / `hiring` / `resume` pattern rather than introducing a new one. * `ward exec build`, `ward exec lint`, and `ward exec pre-commit-all` pass. * Cypress smoke still passes. ## Dependencies Blocked on the promotion-flag issue. Linking to a nine-post `noindex` listing is not the intended end state. ## Non-goals * Homepage visual redesign. Issue #93 owns hierarchy decisions. * Adding post teasers or excerpts to the homepage itself.

coilyco-ops added the

priority

autonomy

headless

labels

2026-08-10 20:09:40 +00:00

coilyco-ops referenced this issue from a commit

2026-08-25 06:43:20 +00:00

feat: promote three posts behind one front matter flag

coilyco-ops referenced this issue from a commit

2026-08-25 06:55:32 +00:00

fix: make /writing/ indexable, per #97's acceptance

coilyco-ops commented

2026-08-25 07:18:34 +00:00

Author

Collaborator

Closing without doing it. Kai's call, 2026-08-25.

The premise expired. This issue was written on 2026-08-10, when its rationale was that "the writing surface is effectively unreachable except by someone who already knows the URL." That was accurate then. It is not now.

#97 landed today. /writing/ and all three promoted posts are indexable, in the sitemap, and carry BlogPosting structured data. The discovery problem this issue existed to fix is solved for the case that matters, which is a stranger finding the work through search rather than through the homepage.

And it would reverse a deliberate decision. docs/pages.md records the homepage composition as ending "after the products rather than repeating Writing and hiring calls to action". Implementing this issue would undo that without the issue noting that it exists.

What is being advertised is also thin. One current post and two archival ones:

2026-04-19   stochastic-design-iteration        4 months
2023-10-11   azure-openai-terraform             ~3 years
2020-01-12   on-permissions-models              ~6 years

A "Writing" call to action pointing at that, sitting beside shipped products, undersells rather than sells.

Revisit condition

Reopen if Kai starts publishing regularly. A writing surface is worth linking before the volume arrives rather than after, so this is a timing judgement rather than a permanent no. Three posts is not the moment.

The alternative, recorded rather than done

If the homepage ever does surface writing, the stronger move is probably not this one. The hero claims "I build agentic engineering platforms", and stochastic-design-iteration is about co-authoring a design document with an LLM. That single post is evidence for the claim the page already makes, and linking a claim to its proof beats linking an archive index.

That is a homepage hierarchy change and #93 owns hierarchy, so it belongs there rather than here.

Not affected

#99's feed is unblocked by #97 and does not depend on this. A feed is how practitioners subscribe, and that path never went through the homepage.

## Closing without doing it. Kai's call, 2026-08-25. **The premise expired.** This issue was written on 2026-08-10, when its rationale was that "the writing surface is effectively unreachable except by someone who already knows the URL." That was accurate then. It is not now. `#97` landed today. `/writing/` and all three promoted posts are indexable, in the sitemap, and carry `BlogPosting` structured data. The discovery problem this issue existed to fix is solved for the case that matters, which is a stranger finding the work through search rather than through the homepage. **And it would reverse a deliberate decision.** `docs/pages.md` records the homepage composition as ending "after the products rather than repeating Writing and hiring calls to action". Implementing this issue would undo that without the issue noting that it exists. **What is being advertised is also thin.** One current post and two archival ones: ``` 2026-04-19 stochastic-design-iteration 4 months 2023-10-11 azure-openai-terraform ~3 years 2020-01-12 on-permissions-models ~6 years ``` A "Writing" call to action pointing at that, sitting beside shipped products, undersells rather than sells. ## Revisit condition Reopen if Kai starts publishing regularly. A writing surface is worth linking **before** the volume arrives rather than after, so this is a timing judgement rather than a permanent no. Three posts is not the moment. ## The alternative, recorded rather than done If the homepage ever does surface writing, the stronger move is probably not this one. The hero claims "I build agentic engineering platforms", and `stochastic-design-iteration` is about co-authoring a design document with an LLM. That single post is evidence for the claim the page already makes, and linking a claim to its proof beats linking an archive index. That is a homepage hierarchy change and `#93` owns hierarchy, so it belongs there rather than here. ## Not affected `#99`'s feed is unblocked by `#97` and does not depend on this. A feed is how practitioners subscribe, and that path never went through the homepage.

coilyco-ops closed this issue

2026-08-25 07:18:43 +00:00

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

coilysiren/website#98

No description provided.

Rows
Columns