quarto-dev / quarto-dev/quarto-cli
FR: Content selectors for websites
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6k
- Forks
- 458
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 41
Description
Documentation sites have frequent need to show different content based on user preference / input. Examples:
- Language selectors such as Quarto's main page "Hello, Quarto" section for choosing between Python, R, Julia, or Obserable
- Desired workflow, such as Command Line vs. API
- Documentation version (perhaps related to (https://github.com/quarto-dev/quarto-cli/issues/474)
- Role, region, or other characteristic
Quarto's support for selectively displaying content is currently limited to panel tabsets, which is not visually appropriate for modifying the content of an entire page.
A Quarto-native content selector would give users the ability to customize the page (or site) based on their preference or need.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No implementation files, tests, or entry points are named. Start by reviewing Quarto's existing panel tabsets and the related issue #474, then trace how documentation pages and sites are rendered. Done would require an agreed design and support for selectors covering the listed preference and workflow examples.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100