quarto-dev / quarto-dev/quarto-cli

Blog example does not contain code

Open
#8,263 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
JavaScript
Stars
6k
Forks
458
Avg merge
1d 9h
Merged PRs (30d)
41

Description

Bug description

In the blog example, posts/post-with-code says "This is a post with executable code.". However, that seems to be all the contents of the page. I was briefly confused, as I expected to find some executable code, and assumed at first something was wrong.

Could add some code to this page -- could either add code which isn't executed (which would always work), or add a jupyter example? Not sure what's prefered so not sure what suggested patch to make.

Steps to reproduce

Run quarto create project blog qqq, then look at posts/post-with-code/index.qmd

Expected behavior

Post contains some code after "This is a post with executable code"

Actual behavior

No response

Your environment

No response

Quarto check output
quarto check
Quarto 99.9.9
[✓] Checking versions of quarto binary dependencies...
      Pandoc version 3.1.11: OK
      Dart Sass version 1.69.5: OK
      Deno version 1.37.2: OK
[✓] Checking versions of quarto dependencies......OK
[✓] Checking Quarto installation......OK
      Version: 99.9.9
      Path: /home/caj/quarto/quarto-cli/package/dist/bin

[✓] Checking tools....................OK
      TinyTeX: (not installed)
      Chromium: (not installed)

[✓] Checking LaTeX....................OK
      Using: Installation From Path
      Path: /usr/bin
      Version: 2023

[✓] Checking basic markdown render....OK

[✓] Checking Python 3 installation....OK
      Version: 3.11.6
      Path: /home/caj/files/web/env/bin/python3
      Jupyter: 5.4.0
      Kernels: gap-4, python3

[✓] Checking Jupyter engine render....OK

[✓] Checking R installation...........OK
      Version: 4.3.1
      Path: /usr/lib/R
      LibPaths:
        - /home/caj/R/x86_64-pc-linux-gnu-library/4.3
        - /usr/local/lib/R/site-library
        - /usr/lib/R/site-library
        - /usr/lib/R/library
      knitr: 1.45
      rmarkdown: 2.25

[✓] Checking Knitr engine render......OK

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Open posts/post-with-code/index.qmd from a project created with quarto create project blog qqq and inspect the existing example content. Decide whether the example should contain non-executed code or a Jupyter example, then update the post so it includes code after the introductory sentence and verify the generated blog displays it.

Written by the indexing model from the issue text.

Assessment

Tech stack
jupyter
Domain
content
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.