# Project Megadodo aka planning to publish a Starlight v1 ## Work in progress pre v1 - (HiDeoo) ([PR #3335](https://github.com/withastro/starlight/pull/3335)) — Custom Search component with better a11y and keyboard support. - (HiDeoo) ([Discussion #3336](https://github.com/withastro/starlight/discussions/3336) - PR soon) — Groupless autogenarated sidebar links and autogenerated links config refactor. <details> <summary>✅ Completed</summary> - ✅ ~~i18next support ([PR #1923](https://github.com/withastro/starlight/pull/1923)) — already announced and should be merged soon~~ - ✅ ~~Improved simpler sidebar config that autogenerates from file data ([PR #1874](https://github.com/withastro/starlight/pull/1874))~~ - ✅ ~~`<LinkButton>` ([PR #1784](https://github.com/withastro/starlight/pull/1784))~~ - ✅ ~~Sidebar state persistence (added that to the Q3 breakdown document as a deliverable for myself — I think the process would be identifying what/when to persist/restore (make a document/checklist for this), either help an existing PR or make a new one and add tests for this)~~ - ✅ ~~Full SSR support ([PR #1255](https://github.com/withastro/starlight/pull/1255)) — kind of low value from a general perspective, attractive to a small fraction of users, but maybe still worth stabilising before v1 in case it requires anything breaking.~~ </details> ## Work to do pre v1 - (Chris) Assess design overhaul. Are there design things that are a11y issues (e.g. fixed UI)? Are there design things that are customisation pain points (e.g. inflexible layouts, tricky to overide styles)? Are there low effort design improvements we can comfortably make across the design system? - ~~(HiDeoo) That was a huge reason on why I created a theme for Starlight, I'm planning to write some thoughts on this at some point based on my work and what was difficult to change/override.~~ - ~~(HiDeoo) Search UI/UX improvements (I plan to start researching this soon, one of the biggest complaints I get and even prevent Starlight adoptions sometime).~~ - (HiDeoo) Bundle Starlight (I think it would be weird to use a v1 project that can [prevent you from typechecking](https://github.com/withastro/starlight/discussions/983) your project/monorepo). - (Chris) Should we spend some time thinking about sidebars? [Multiple Sidebar Support](https://github.com/withastro/starlight/discussions/959) is second only to Mermaid as most requested feature. - (HiDeoo) Deprecate support for legacy CCs. - (HiDeoo) Astro v6 support. <details> <summary>✅ Completed</summary> - ✅ ~~(Chris) Use `@layer` for styles ([PR #2322](https://github.com/withastro/starlight/pull/2322))~~ - ✅ ~~(Chris) Move route data to `Astro.locals` ([PR #2390](https://github.com/withastro/starlight/pull/2390))~~ </details> ## Work to consider pre v1 - (HiDeoo) Standardize translatable configuration value API ([`translations` property](https://starlight.astro.build/guides/sidebar/#internationalization), [`string | Record<string, string>`](https://starlight.astro.build/guides/sidebar/#internationalization-with-badges), etc.) - (HiDeoo) Should we allow for `remarkPluginFrontmatter`? <details> <summary>✅ Completed</summary> - ✅ ~~(Chris) Alignment with Astro v5/Content Collections 2.0 — need to check in with Matthew about the timing there~~ - ~~(HiDeoo) Is CC 2.0 the same as the Content Layer from this [post](https://astro.build/blog/future-of-astro-content-layer/)?~~ - ✅ ~~(Chris) Need to understand what will be needed to support Content Collections 2.0 and what it will unlock (e.g. Starlight pages from any source?)~~ - ~~(HiDeoo) Would it finally allow for the same Markdown rendering between a local CC and remote/other content?~~ - ~~(HiDeoo) Would integrations be able to define collections using CC 2.0 somehow?~~ - ~~(HiDeoo) How would this interact with Starlight, e.g. still a `<Content />`? Possible to render from MDX? How to render from a Starlight custom page~~ - ✅ ~~(HiDeoo) Translatable sidebar badges using a similar API as the one for translating site titles? ([PR #2285](https://github.com/withastro/starlight/pull/2285))~~ - ✅ ~~(HiDeoo) Built-in heading links using an approach similar/close to the Astro Docs? I've heard people installing "Copy element ID" extensions just for this ([discussion](https://github.com/withastro/starlight/discussions/1239) about this) ([PR #3033](https://github.com/withastro/starlight/pull/3033))~~ - ✅ ~~(HiDeoo) More i18n API improvements ([PR #2578](https://github.com/withastro/starlight/pull/2578))~~ </details> ## Ideas not tied to a specific release/v1 - (HiDeoo) - ([PR #3024](https://github.com/withastro/starlight/pull/3024)) — Better/broader icons support with `astro-icon` but would not be breaking. - (HiDeoo - idea from Sarah during the standup of 06/25/2024) Support for the `starlight-component` and `starlight-plugin` package.json keywords so Starlight plugins and components can be listed in https://astro.build/integrations/. - (HiDeoo) And maybe even filtered with a new Starlight filter in the UI? - (HiDeoo) No change to Astro core to support auto-adding `starlight-plugin` packages to a Starlight config. - (HiDeoo) I have some potential ideas for plugin improvements but not high priority and would not be breaking. - (HiDeoo) Evaluate if the [`starlight-auto-sidebar` plugin](https://github.com/HiDeoo/starlight-auto-sidebar) should be merged in core.