adobe / adobe/spectrum-design-data
Write evaluation doc: Bikeshed prototype vs current 11ty spec
- Dominant language
- Rust
- Stars
- 153
- Forks
- 35
- Avg merge
- 7h 54m
- Merged PRs (30d)
- 111
Description
Part of #1006.
Once the prototype at `https://garthdb.github.io/design-data-spec/` is live, fill in an evaluation doc comparing it against the current spec on each of the six decision criteria from #1006.
Conclusion should be one of:
- **(a) Migrate** — adopt Bikeshed as the canonical spec toolchain
- **(b) Cherry-pick** — keep 11ty but adopt specific Bikeshed ideas (dfn autolinking, biblio refs, etc.)
- **(c) Shelve** — current 11ty pipeline is good enough; Bikeshed overhead not worth it
This deliverable drives the final spec tooling decision.
Contributor guide
Research direction
Read the six decision criteria in #1006, then inspect the prototype at https://garthdb.github.io/design-data-spec/ and the current 11ty spec. Compare both approaches against every criterion and document whether to migrate, cherry-pick specific ideas, or shelve Bikeshed.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, tooling
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100