Skip to content

Add featured CMS grid to navigation#13247

Merged
delucis merged 18 commits intomainfrom
hd/sarah-feature-cms
Feb 10, 2026
Merged

Add featured CMS grid to navigation#13247
delucis merged 18 commits intomainfrom
hd/sarah-feature-cms

Conversation

@delucis
Copy link
Copy Markdown
Member

@delucis delucis commented Feb 10, 2026

Description (required)

This PR updates the navigation component for CMS guides to be able to highlight featured platforms from our OSS sponsors. Starting with CloudCannon 🎉

@netlify
Copy link
Copy Markdown

netlify bot commented Feb 10, 2026

Deploy Preview for astro-docs-2 ready!

Name Link
🔨 Latest commit 23056f6
🔍 Latest deploy log https://app.netlify.com/projects/astro-docs-2/deploys/698b7ee4c608270008026aac
😎 Deploy Preview https://deploy-preview-13247--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 project configuration.

@astrobot-houston
Copy link
Copy Markdown
Contributor

astrobot-houston commented Feb 10, 2026

Lunaria Status Overview

🌕 This pull request will trigger status changes.

Learn more

By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.

You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File Note
en/guides/cms/cloudcannon.mdx Source changed, localizations will be marked as outdated.
en/guides/cms/index.mdx Source changed, localizations will be marked as outdated.
src/content/i18n/en.yml Source changed, localizations will be marked as outdated.
Warnings reference
Icon Description
🔄️ The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

@sarah11918
Copy link
Copy Markdown
Member

sarah11918 commented Feb 10, 2026

Thanks @delucis and @HiDeoo ! I'm just checking in both light and dark, various screen sizes... one initial thing: do you think we still need "More CMS Guides" now that we have both Featured CMS and All CMS? Maybe we don't need "More" at all? Or do we think that's good from an organization/hierarchy standpoint? Just feels like a lot of titles in quick succession!

image

Copy link
Copy Markdown
Member

@sarah11918 sarah11918 left a comment

Choose a reason for hiding this comment

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

I checked all the nav guides (to make sure no old logo problems were reintroduced) in Chrome, including at multiple screen sizes, and I think this all looks good to me! (Earlier comment about whether we still need that heading when each separate nav has a heading, but that's a nit and can always be updated later if we decide we don't like it!)

@delucis
Copy link
Copy Markdown
Member Author

delucis commented Feb 10, 2026

do you think we still need "More CMS Guides" now that we have both Featured CMS and All CMS? Maybe we don't need "More" at all? Or do we think that's good from an organization/hierarchy standpoint? Just feels like a lot of titles in quick succession!

Yeah I also wondered this. I think some kind of separation is good to clarify this is separate from the main content? Doesn’t have to be a heading necessarily though I guess. (We’d need to bump up the heading levels though if we did that.)

@sarah11918
Copy link
Copy Markdown
Member

I think it's fine for now! Technically, they are both "more". Happy to let you make the call, but it did stand out.

@delucis delucis merged commit 9d57eaf into main Feb 10, 2026
10 checks passed
@delucis delucis deleted the hd/sarah-feature-cms branch February 10, 2026 19:00
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