Skip to content
This repository was archived by the owner on Oct 20, 2026. It is now read-only.

feat(parity): Jekyll finale (future posts + import) - #70

Merged
subhangadirli merged 3 commits into
mainfrom
feat/jekyll-finale
Sep 23, 2026
Merged

subhangadirli merged 3 commits into
mainfrom
feat/jekyll-finale

Conversation

@subhangadirli

Copy link
Copy Markdown
Owner

Roadmap: Jekyll parity finale (ADR-010)
Scope: --future on build/dev with discover filter, import command (posts/pages/data/config + report); not touched: Liquid conversion (documented manual), CSV, themes/assets
Steps:

  • feat(build): future filter + flags + Data rescue
  • feat(import): converter + CLI + registration
    Tests: future 2/0/0 + import 6/0/0 + help/build/dev; full 453 green; format + shards build ok
    Manual: import /tmp/jfinal/old (2 posts/1 page/1 data) -> build 5 pages + injected date verified; check flags stale scaffold link as designed
    Docs: adr/010 + cli.md (future/import) + content.md (drafts+future)
    Risk: discover now calls date() per entry (invalid dates still surface via schema path, pinned by fixtures_spec); no engine/config change

ADR-010 part 1: Context#future, discover filter, build/dev flags, Data::Error rescue.
Verified: future/build/dev specs 17/0/0.
ADR-010 part 2: posts/pages/data/config conversion, date injection, report.
Verified: import specs 7/0/0, full 453 green.
future? returns false on invalid dates so fixtures keep failing
all-together via Schema validation (pinned by fixtures_spec).
Verified: full 453 green.
@subhangadirli
subhangadirli merged commit f40a606 into main Sep 23, 2026
2 checks passed
@subhangadirli
subhangadirli deleted the feat/jekyll-finale branch September 23, 2026 07:15
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant