Document dependencies and roadmap
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 11
- Forks
- 22
- Avg merge
- 7d 3h
- Merged PRs (30d)
- 2
Description
Similarly to https://cxwiki.sap.com/display/prodandtech/Technical+Roadmap, we should document the direct dependencies for Spartacus.
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 by reviewing the linked Technical Roadmap and the existing Spartacus documentation to identify the expected structure and current direct dependencies. Done means the direct dependencies and roadmap are documented in the repository, with coverage aligned to the referenced roadmap.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100