new Astro docs roadmap
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 159
- Forks
- 63
- Avg merge
- 7h 26m
- Merged PRs (30d)
- 2
Description
Hi @Indyandie , I'll write here a checklist of required and optional things (that I see as of now) to do in order to move from our current website to the Astro one:
- import all the API v2 sections as they appear now (https://pokeapi.co/docs/v2). Or find a way to have the same info on the OpenAPI section. One thing that the OpenAPI section seems to be lacking is the the types of the objects
- The front-page try-it-now
Optional:
- A translation system
- A section for writing how-to guides
Contributor guide
No contributing guide indexed for this repository
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 current Astro documentation site against the API v2 and OpenAPI sections linked in the issue. The remaining checklist items are a translation system and a how-to guide section; confirm their scope and the project’s documentation entry points before defining completion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation, web-dev
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100