Add Features nav dropdown and enable TOC on features page#293
Add Features nav dropdown and enable TOC on features page#293cindyytong wants to merge 2 commits intomainfrom
Conversation
- Convert Features nav to dropdown with category links (Overview, Data Apps & AI Tools, Data Explorer & Visualization, Connections & Publishing, Enterprise) - Enable table of contents on features page for easier navigation - Minor whitespace cleanup in features.qmd 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
✅ Deploy Preview for positron-posit-co ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
The Snowflake privacy policy and terms of service URLs block automated checks, causing CI failures. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
RE: feedback from @petetronic for TOC for features. I added in links in the Features nav bar and a TOC back on /features. Thye only link to the JTBD sections rather than all of the features. Since there are ~20+ features it will be a huge TOC if I added in the dropdown. The cards are a way to group these features and the guides toc does have future drill down by features and workflows Open to more feedback on how to iterate here. My understanding for this request is to provide folks new to positron a quick way to skim through features and learn about value prop. |
juliasilge
left a comment
juliasilge
left a comment
There was a problem hiding this comment.
I like adding toc: true on this page but I'm not sure about the nav bar entries; I am afraid they are not connected enough with what's in those sections. Should we re-organize somehow, if we think top nav is important? Or just stick with the TOC in the page?
I'll say that I personally don't feel super committed to making top nav more detailed for a page like this that's more for browsing than finding specific info (like in contrast with what we have for "guides"). I'm very happy for us to find a way to make it work, though, if other folks think it's important!
| with: | ||
| file_types: .qmd | ||
| exclude_patterns: https://cdn.posit.co/positron/prereleases/,https://positron.posit.co/images/,https://github.com/posit-dev/positron/issues | ||
| exclude_patterns: https://cdn.posit.co/positron/prereleases/,https://positron.posit.co/images/,https://github.com/posit-dev/positron/issues,https://www.snowflake.com/en/legal/ |
There was a problem hiding this comment.
I know this flakes fairly often, but it is a real external URL that we do want to check. I'd rather us have to re-run the linting than to never check this again.
| - text: "Data Apps & AI Tools" | ||
| href: features.qmd#bridge-the-exploration-and-production-divide | ||
| - text: "Data Explorer & Visualization" | ||
| href: features.qmd#explore-and-analyze-with-speed | ||
| - text: "Connections & Publishing" | ||
| href: features.qmd#develop-with-confidence |
There was a problem hiding this comment.
I'm not sure about these first three. The "Enterprise" one definitely makes sense but these other three sets of groups of not very homogeneous and feel like they don't match what's in the sections.
Do we think it's doable to come up with nav entries that make sense with these groups? Should we rearrange the groups so they are more homogeneous? Make more groups so we can link to them in a more straightforward way?
2 participants
Summary
Test plan
🤖 Generated with Claude Code