docs
docs copied to clipboard
withastro
Astro documentation
A recent question in our Discord support channel brought me to the realization that we currently don't document how you can fill slots to be used in Astro components from...
Our guides for creating non-HTML pages (aka "endpoints") are pretty tough to scan as a new user. Right now, we have: - ["non-HTML pages" listed on our **pages** docs](https://docs.astro.build/en/core-concepts/astro-pages/#non-html-pages), which...
Opening an issue to keep track of the things we need to get the new i18n process ready. This is partly for myself as I can tackle a bunch of...
We are currently only tracking changes in the Markdown pages inside the Translation Status Overview Issue, it would be nice if we also tracked the changes in the `i18n/` folder...
We currently only have the "Missing" and "Needs updating" sections, the idea is to add a third, "In Progress" section tracking open PRs affecting missing/needs updating pages. Bonus points: add...
If there are new additions to the out-of-date pages list, ping the relevant roles in `#docs-i18n` on Discord. Suggestion to do this every “Translation Tuesday”.
Capturing the idea that we should show instructions for setting up a local dev env and testing a non-internal integration (see [this comment](https://github.com/withastro/docs/pull/388#issuecomment-1112041968)) per @bholmesdev request. One will need to...
#### What kind of changes does this PR include? - New or updated content #### Description Adds information about `Astro.context`, introduced in withastro/astro#3934
- What is the `` element? - Why do we inline some scripts? - How does bundling work? - etc. Probably fits into the “Explanation” quadrant if we’re thinking with...
Here’s something that I didn’t get to while working on #954 that would be cool to add to the integration READMEs workflow. The READMEs currently use a mix of styles...