docs(work): map html examples navigation slices
Add a northstar and ready vertical slices for making html_examples start at an index, splitting implemented examples into focused pages, proving infinite-scroll by scrolling, and keeping smoke/docs/requirements aligned.
This commit is contained in:
@@ -0,0 +1,57 @@
|
||||
---
|
||||
id: SLICE-0017
|
||||
type: slice
|
||||
status: ready
|
||||
parent: NS-0004
|
||||
title: Keep html_examples requirements and docs aligned with page restructuring
|
||||
refs:
|
||||
- AGENTS.md
|
||||
- REQUIREMENTS.md
|
||||
- examples/html_examples/README.md
|
||||
---
|
||||
|
||||
## Objective
|
||||
|
||||
After the index, per-page routes, and true scroll-triggered infinite-scroll behavior are implemented, make the durable requirement/doc authority match the shipped behavior or explicitly record that requirements were unaffected.
|
||||
|
||||
## Authority
|
||||
|
||||
- `AGENTS.md` requires behavior changes to update `REQUIREMENTS.md` in the same change when durable product obligations, acceptance, safety/recovery behavior, or verification duties change.
|
||||
- `REQUIREMENTS.md` already contains constraints for htmx-equivalent examples, enhanced page navigation, and browser smoke. req: htmx_equivalents/001 req: htmx_equivalents/003 req: htmx_equivalents/005 req: page_swap/007 req: page_swap/008 req: test/006
|
||||
- Workledger evidence should reflect implemented or blocked state once the restructuring slices complete.
|
||||
|
||||
## Close when
|
||||
|
||||
- If restructuring changes durable obligations for the pattern gallery, `REQUIREMENTS.md` is updated in the same change with stable requirement IDs and redgate-valid rows.
|
||||
- If no durable obligation changes, the implementation handoff says `REQUIREMENT IMPACT: none` and explains why the existing `htmx_equivalents/*`, `examples/*`, `page_swap/*`, and `test/*` requirements already cover the behavior.
|
||||
- README and workledger evidence point to the actual page/route/smoke proof rather than the old single-page gallery shape.
|
||||
- No requirement row is added only to satisfy tooling; requirements remain checkable obligations, not implementation notes.
|
||||
|
||||
## Allowed files
|
||||
|
||||
- `REQUIREMENTS.md`
|
||||
- `AGENTS.md` only if stable agent guidance truly changes
|
||||
- `examples/html_examples/README.md`
|
||||
- `work/northstars/NS-0004-html-examples-navigation.md`
|
||||
- `work/slices/SLICE-0013-html-examples-index-landing.md`
|
||||
- `work/slices/SLICE-0014-html-examples-per-example-pages.md`
|
||||
- `work/slices/SLICE-0015-infinite-scroll-standalone-page.md`
|
||||
- `work/slices/SLICE-0016-html-examples-smoke-and-readme.md`
|
||||
|
||||
## Verification
|
||||
|
||||
- `redgate list`
|
||||
- `redgate refs`
|
||||
- `redgate health --strict`
|
||||
- `redgate lint` if `REQUIREMENTS.md` changes or the slice claims maintainability cleanup
|
||||
- `workledger check && workledger list`
|
||||
|
||||
## Non-goals
|
||||
|
||||
- Do not perform broad redgate lint cleanup outside html_examples/page navigation requirements.
|
||||
- Do not rewrite existing requirements just because wording can be polished.
|
||||
- Do not add new product commitments for deferred/integration-owned/refused examples.
|
||||
|
||||
## Evidence
|
||||
|
||||
Ready; no implementation evidence yet.
|
||||
Reference in New Issue
Block a user