histoire-dev / histoire-dev/histoire
Add Hst.yml controls
Open
Nobody has claimed this yet.
enhancement: to triage
- Dominant language
- TypeScript
- Stars
- 3.6k
- Forks
- 212
- PR merge metrics
- No merged PRs in 30d
Description
Clear and concise description of the problem
Just started using Historie and absolutely love it!
I work often work with content objects which get passed to my components. Hst.json controls works okay for this, but it's not an ideal editing experience.
Suggested solution
Hst.yml (or .yaml) would be better for me.
Why?
- I use Astro with all content from markdown files
- My CMS is git/markdown based
Alternative
Hst.json
Additional context
No response
Validations
- Follow our Code of Conduct
- Read the Contributing Guidelines.
- Read the docs.
- Check that there isn't already an issue that requests the same feature to avoid creating a duplicate.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No implementation files, entry points, or tests are named. Start by reading the linked guide and contribution guidelines, then trace how Hst.json controls are handled. Done means equivalent Hst.yml or .yaml controls support the stated Astro and markdown workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, yaml
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100