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

Switch to Quarto as website builder #19

Open
2 tasks
redeboer opened this issue Oct 3, 2024 · 1 comment
Open
2 tasks

Switch to Quarto as website builder #19

redeboer opened this issue Oct 3, 2024 · 1 comment
Labels
📝 Docs Improvements or additions to documentation 🖱️ DX Improvements to the Developer Experience ❔ Question Discuss this matter in the team

Comments

@redeboer
Copy link
Member

redeboer commented Oct 3, 2024

It starts to look like Quarto is a better alternative for this repository, because it is faster in building websites with a large number of pages.

Related issues

  1. 🐛 Bug 📝 Docs
    redeboer
  2. 📝 Docs
    redeboer
@redeboer redeboer added 📝 Docs Improvements or additions to documentation 🖱️ DX Improvements to the Developer Experience labels Oct 3, 2024
@redeboer redeboer self-assigned this Oct 3, 2024
@redeboer redeboer added the ❔ Question Discuss this matter in the team label Oct 7, 2024
@redeboer redeboer removed their assignment Oct 7, 2024
@redeboer
Copy link
Member Author

redeboer commented Oct 7, 2024

A test implementation is available at https://github.com/redeboer/compwa-reports/tree/quarto. You can run it with:

quarto preview docs

For now, I am inclined to stick with the Sphinx ecosystem.

Quarto

Advantages

  • Blog post overview looks amazing, ideal for Technical Report overview
  • Great support for listing metadata, like abstract, author, etc.
  • Re-rendering is quite fast when saving
  • More active (and larger?) community
  • jupyterlab-quarto seems to be more actively maintained than jupyterlab-myst
  • Easy to activate cookie preference buttons

Disadvantages

  • No linkcheck
  • Bad support for intersphinx
  • Impossible to hide the input of specific cells
  • Impossible to hide or remove cell output
  • Code highlighting doesn't look too great
  • Links and inline code doesn't look good in the default dark themes
  • (?) Jupyter notebooks are overwritten with cell output when executed?
  • TR overview (blog post listing) does not update when updating the metadata of a TR
  • Community seems to be oriented more to R
  • No support yet on Read the Docs

Sphinx ecosystem

Advantages

  • Easily extendable and pluggable
  • Good support for Jupyter notebooks
  • No need to rewrite all the syntax

Disadvantages

  • Builds are slow

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
📝 Docs Improvements or additions to documentation 🖱️ DX Improvements to the Developer Experience ❔ Question Discuss this matter in the team
Projects
None yet
Development

No branches or pull requests

1 participant