Skip to content
New issue

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

[nav.ts] New sidebar sections: built-ins and add-ons #5213

Merged
merged 4 commits into from
Oct 27, 2023

Conversation

sarah11918
Copy link
Member

@sarah11918 sarah11918 commented Oct 27, 2023

Description (required)

Adds two new sections to our main sidebar: Built-ins and Add-ons.

This intends to better highlight the natural progression of learning about Astro: Basics > not basic, but included stuff you probably want > things you can add-on that are part of our story: framework islands and hyping our rendering options

Play around and see what you think!

Current Docs -> Proposal:
Screenshot 2023-10-27 10 30 52Screenshot 2023-10-27 10 29 57

@netlify
Copy link

netlify bot commented Oct 27, 2023

Deploy Preview for astro-docs-2 ready!

Name Link
🔨 Latest commit 2a84059
🔍 Latest deploy log https://app.netlify.com/sites/astro-docs-2/deploys/653bf4bef745970007a5ec1c
😎 Deploy Preview https://deploy-preview-5213--astro-docs-2.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link
Member

@natemoo-re natemoo-re left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this clarifies the structure a lot! Big fan of this change.

Don't consider my comments blocking at all! Approved.

},
{ text: 'Server-side Rendering', slug: 'guides/server-side-rendering', key: 'guides/server-side-rendering' },
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is my only complaint! Seems like Server-side Rendering should be under Built-ins. I know this section is getting revamped, but I don't think it's an add-on.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, I see there is discussion happening in Discord about this point.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mirroring discussion on Discord: because it requires adding an adapter, conceptually this falls closer to UI Frameworks because it doesn't work without something that needs to be astro added. So, literally, adding something for SSR to work is what makes it an add on. This category would be restricted to things very closely coupled to Astro's core offering, like our official packages where we also document their usage.

So noted, but as @delucis mentioned, from the outside looking in, "all you know is adding X makes SSR work" and I don't think this placement diminishes that it is something that is built into Astro core (but is helpful in understanding that it needs to be "unlocked" in order to actually use it.

And yes, I'd like this page to eventually be replaced with our Rendering Modes page, which maybe DOES go into basics, and then maybe we also keep an SSR page here that is devoted mostly to adding the adapter, marking individual pages in or out of pre-rendering etc.

src/i18n/en/nav.ts Outdated Show resolved Hide resolved
@ElianCodes
Copy link
Member

Big fan of the change!

Copy link
Member

@ElianCodes ElianCodes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The new sidebar feels and looks really nice!

@wassfila
Copy link
Contributor

wassfila commented Oct 27, 2023

  • I like how this new clustering helps already place the user context when looking for docs, it just brings the wish for more, for example adding a cms is also adding integrations so it feels like it should be in add-ons but then it's also a recipe.

  • same comment as above regarding the ssr as add-ons, impression jumped to me when I saw it. I understand that some adapters are addon, but node js is built in I think, but I might be wrong. So this brings to think on the definition of add-ons vs built-in.

  • one thing that triggers thoughts about add-ons vs built-ins, users might confuse them with officially supported and maintained vs provided by the community or third party, which come in mind when reading the heading "Official integrations", so it's an "official add on". If only there was a good spot where it's poosible to explain what is built in and what is add on, maybe in the intro of each first page in each category.

those are just thoughts, all in all, it got much better over time.

@sarah11918
Copy link
Member Author

@wassfila Even the Node adapter has to be added! (FYI)

@sarah11918
Copy link
Member Author

Final decision after consultation with the team:

SSR label in sidebar changed to "SSR Adapters" in keeping with the idea of the adapter being the "add on", and less to imply stuff about our actual rendering modes.

This is a non-content/breaking change that only moves items in the sidebar. But, the plan is to augment this and allow us to include a "Rendering Mode" explanatory page in basics, and eventually this SSR page will in fact be geared towards enabling and using the adapters

@sarah11918 sarah11918 merged commit bc3c917 into main Oct 27, 2023
10 checks passed
@sarah11918 sarah11918 deleted the sidebar-new-sections branch October 27, 2023 17:53
NinuzIBZ added a commit to NinuzIBZ/docs that referenced this pull request Feb 1, 2024
The file `nav.ts` has been updated to align with the English language documentation based on this commits withastro#4876 , withastro#5183 , withastro#5213 , withastro#5271 , withastro#5187 , withastro#4667 , withastro#5541 , withastro#5605 , withastro#5499 , withastro#6470 , withastro#6620
@NinuzIBZ NinuzIBZ mentioned this pull request Feb 1, 2024
yanthomasdev added a commit that referenced this pull request Feb 5, 2024
The file `nav.ts` has been updated to align with the English language documentation based on this commits #4876 , #5183 , #5213 , #5271 , #5187 , #4667 , #5541 , #5605 , #5499 , #6470 , #6620

Co-authored-by: Yan Thomas <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants