Earlier this year in July, I gave a short Experience Talk at JuliaCon. In a related blog post I explained how the introduction of Quarto made my ...
For further actions, you may consider blocking this person and/or reporting abuse
Nice overview! Me and my team have jumped to Quarto after reading your summer blog post - never looked back! A lot of html reports and revealjs presentations for our stakeholders.
A tip we learned: if you write a lot of code (our case for data analyses/EDA), it’s easier to stay in .jl and convert to .qmd with Literate.jl (PR: github.com/fredrikekre/Literate.jl...) with VSCode tasks
Thanks, Jan - great to hear that this has worked out well for you and your team.
Very interesting you mention Literate.jl, actually. At the JuliaLang Eindhoven Meetup last night, I had the chance to discuss the potential for a Pluto.jl <-> Quarto conversion with the folks behind Pluto. The PR you linked might actually go a long way in terms of making that possible, since Pluto notebooks are just .jl files (with a bit of magic on top). Have a few other commitments in the coming weeks, but will give turn back to this.
I would be intereste in Pluto <-> Quarto as well :)
Quite an informative article with many things to try for newcomers.
Did you try if it would be possible to install Quarto within Colab & try to run the notebook using Colab & generate the final document?
Thanks! I don’t think there is an actual Quarto plugin for Colab, but you can of course always work with Jupyter notebooks in Colab and still use them with Quarto. In the article I recommend to use .qmd files, but Colab is actually one reason people might still also like to use .ipynb. Fortunately, converting .qmd to .ipynb and vice versa is seamless.
I guess python tooling is a priority for Colab as of now. Perhaps someone will bridge the gap between Quarto & Colab soon.
Quarto in documenter.jl looks super interesting – I could not see how you actually run quarto on these – do you do that manually before pushing to GitHub? Or is that done on CI?
Hi @kellertuer - good question! So far i've relied on conventional Quarto workflows (so just
quarto renderthe whole thing locally). Should be straightforward to use CI for that, but I actually like to do this locally and see if everything renders well. Hope this helps!I see your point, especially for longer computations in a tutorial pre-rendering locally might be nice – but if one could store the
_freezeas an artefact then that might still be quite fast. I might experiment with that once I get a little more familiar with Quarto (currently fighting my starting steps).A question concerning the use of forem: How did you get the phrase “Originally published at Medium” below the author name?
Hi Roland, this was auto-generated, since I imported the article from Medium. @logankilpatrick pinned post describes how to link your forem account to an existing Medium account or blog. Hope this helps!
Hi Patrick, thanks for your rapid answer!
I've already read the articles of @logankilpatrick on how to use forem, but I haven't found a description on how to import a Medium article. I've only read that you can do this, but not how. Can you give me a hint, on how to do that or on a article that explains the process?
Oh I see! You can find this under Settings > Extensions: forem.julialang.org/settings/exten....
Ah, thank you very much! 👍