patternfly / patternfly/patternfly-org
add metadata on md files to store the version
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 74
- Forks
- 147
- Avg merge
- 4d 11h
- Merged PRs (30d)
- 2
Description
Followup for https://github.com/patternfly/patternfly/issues/5376
we have access to pageData via ## This is the {pageData.id} component
@mcoker https://github.com/patternfly/patternfly/pull/5434#discussion_r1160917866
Jira Issue: PF-597
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
Start with the linked parseMD.js location and inspect how pageData is exposed for Markdown pages. Read the referenced PatternFly issue and pull request discussion to determine which version metadata is required and where it should be stored. Done means Markdown files carry the agreed version metadata and the documentation framework can access it through the relevant page data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100