Support Quarto column layout classes in posts

Several ported posts use Quarto's column layout features — either .column-* CSS classes on divs or #| column: code cell options — which aren't currently supported by the Hugo site.

Spotted on: /blog/quarto/2022-02-17-advanced-layout/

Affected posts

Quarto

• quarto/2022-02-17-advanced-layout
• quarto/2024-07-02-beautiful-tables-in-typst
• quarto/2024-11-25-1.6-release
• quarto/2025-07-24-parameterized-reports-python
• quarto/2026-03-05-pdf-accessibility-and-standards

Shiny

• shiny/announcing-new-r-shiny-ui-components
• shiny/bslib-0.9.0
• shiny/bslib-dashboards
• shiny/bslib-tooltips
• shiny/chromote-0.5.0
• shiny/conf-2025-shinytalks
• shiny/dynamic-accordion-panels
• shiny/introducing-component-layouts
• shiny/responsive-shiny-layouts
• shiny/shiny-assistant
• shiny/shiny-express
• shiny/shiny-python-0.5.0
• shiny/shiny-python-0.6.0
• shiny/shiny-python-1.2-brand-yml
• shiny/shiny-python-1.4
• shiny/shiny-python-chatstream
• shiny/shiny-r-1.8.0
• shiny/weather-lookup-about
• shiny/weather-lookup-bslib
• shiny/weather-lookup-caching

Start by comparing the listed Quarto and Shiny post paths, especially the spotted advanced-layout post, to identify both .column-* classes and #| column: options in the rendered content. Trace the Hugo rendering and styling entry points that handle those posts; done means the affected pages display the intended column layouts for both forms.