docs: update generated reference styling#9031
Conversation
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request introduces custom styling to the project's TypeDoc-generated documentation to ensure it aligns with the updated documentation design. It includes the addition of a stylesheet and updates to the TypeDoc configuration to incorporate these styles and refine navigation links. Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request introduces a custom CSS stylesheet (docs/reference.css) to style the TypeDoc reference documentation and updates typedoc.json to apply this stylesheet, update the titleLink to /, and add a link to the main documentation. The review feedback suggests rounding high-precision decimal values in the lab() color variables within the new CSS file to improve readability and maintainability.
mikehardy
left a comment
There was a problem hiding this comment.
LGTM functionality wise and I trust your CSS a precise 100.000% more than mine so if you're happy with the CSS that works for me.
Typedoc publishes on release so it matches shipped code, and we're due for one shortly so we'll get to see this live soon but not immediately on this merge
|
close/open cycle to restart actions after github actions outage |
Add custom css overrides to the typedoc generated output to align with new docs