We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This issue helps keep track of withastro/starlight#415 and its corresponding PR withastro/starlight#709, which is highly relevant to our docs sites because we do customise the site header via https://gist.github.com/giuseppelt/7f918a3ac02a011d76811ae472f8bf09. This is known to be a hacky way of doing it, and if the ability to customise Starlight components becomes a first-party solution, we can update our implementations accordingly.
Depending on what the final API is, we may or may not be able to add those custom Starlight components to our shared npm library.
The text was updated successfully, but these errors were encountered:
We have updated all our documentation sites to use the proper API:
Sorry, something went wrong.
huijing
No branches or pull requests
This issue helps keep track of withastro/starlight#415 and its corresponding PR withastro/starlight#709, which is highly relevant to our docs sites because we do customise the site header via https://gist.github.com/giuseppelt/7f918a3ac02a011d76811ae472f8bf09. This is known to be a hacky way of doing it, and if the ability to customise Starlight components becomes a first-party solution, we can update our implementations accordingly.
Depending on what the final API is, we may or may not be able to add those custom Starlight components to our shared npm library.
The text was updated successfully, but these errors were encountered: