quarto-dev / quarto-dev/quarto-cli
Make `code-tools` in or under "Other formats"
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6k
- Forks
- 458
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 41
Description
It was discussed somewhere but cannot find it again.
With the manuscript project type and "other formats" linking, it feels code-tools makes less sense in terms of purposes and aesthetics/design.
I am here suggesting to (either or both):
- move
code-toolsin a "section" such as "Other formats". - Make a "Quarto" format which would "link" the source code.
The main reason is that code-tools is less visible and not really pretty with the margin/sidebar.
---
title: "Quarto Playground"
format:
html: default
pdf: default
toc: true
code-tools: true
---
This is a playground for Quarto.
## Section 1
{{< lipsum 1 >}}
## Section 2
{{< lipsum 1 >}}
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 or tests are named. Start by locating the code-tools placement and format-linking entry points in the Quarto CLI, then compare the rendered layout with the attached example. Done means an agreed approach is implemented and the resulting code-tools or Quarto format presentation is verified.
Written by the indexing model from the issue text.
Assessment
- Domain
- design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100