move from twitter to bluesky in examples#1815
Conversation
📝 Preview Deployment🔍 Full site preview: https://deploy-preview-1815.quarto.org 🔄 Modified Documents |
|
@cderv Yes, I think we need to redo the screenshots. In addition to:
I think we should redo:
These other ones can probably remain since they are in sections that aren't as clearly linked to default template:
|
Ok. Probably a good opportunity to create a script to help us redo screenshots quickly. |
📝 Preview Deployment🔍 Full site preview: https://deploy-preview-1815.quarto.org 🔄 Modified Documents |
92e5a81 to
3fd8f09
Compare
📝 Preview Deployment🔍 Full site preview: https://deploy-preview-1815.quarto.org 🔄 Modified Documents |
3fd8f09 to
01ba64f
Compare
📝 Preview Deployment🔍 Full site preview: https://deploy-preview-1815.quarto.org 🔄 Modified Documents |
📝 Preview Deployment🔍 Full site preview: https://deploy-preview-1815.quarto.org 🔄 Modified Documents |
📝 Preview Deployment🔍 Full site preview: https://deploy-preview-1815.quarto.org 🔄 Modified Documents |
📝 Preview Deployment🔍 Full site preview: https://deploy-preview-1815.quarto.org 🔄 Modified Documents |
- Add .include-dark to tools.png, myblog.png, and 4 about-page images (trestles, solana, marquee, broadside) so dark variants render - Replace Twitter references with Bluesky in alt text - Use concise alt text matching manifest descriptions - jolla and navbar-tools already updated in prior commits
📝 Preview Deployment🔍 Full site preview: https://deploy-preview-1815.quarto.org 🔄 Modified Documents |
📝 Preview Deployment🔍 Full site preview: https://deploy-preview-1815.quarto.org 🔄 Modified Documents |
📝 Preview Deployment🔍 Full site preview: https://deploy-preview-1815.quarto.org 🔄 Modified Documents |
📝 Preview Deployment🔍 Full site preview: https://deploy-preview-1815.quarto.org 🔄 Modified Documents |
Captured from https://quarto-dev.github.io/quarto-demo/ with GitHub dropdown open, showing sidebar title, tools, search, and navigation. # Conflicts: # docs/websites/images/tools-dark.png # docs/websites/images/tools.png
- Add .include-dark to tools.png, myblog.png, and 4 about-page images (trestles, solana, marquee, broadside) so dark variants render - Replace Twitter references with Bluesky in alt text - Use concise alt text matching manifest descriptions - jolla and navbar-tools already updated in prior commits
Switch from quarto.org URL to local breadcrumbs example with matching sidebar structure (Tutorials > Tutorial Landing). Uses darkly + custom SCSS to make breadcrumb background transparent in dark mode. # Conflicts: # docs/websites/images/nav-breadcrumbs-dark.png # docs/websites/images/nav-breadcrumbs.png
Replace anchored and floating sidebar screenshots with new captures from screenshot tooling. Add dark variants and .include-dark class.
Navbar-only element capture at 1000px viewport from navbar-basic example.
nav-bar-hybrid, nav-bar-hybrid-sidebar, nav-bar-hybrid-dropdown with dark mode variants.
Enables dark mode variants for nav-bar-hybrid, nav-bar-hybrid-sidebar, and nav-bar-hybrid-dropdown screenshots.
The dark variant (nav-breadcrumbs-dark.png) was already in the PR but the .qmd reference was missing the .include-dark class.
0fa3cf7 to
0be9e78
Compare
📝 Preview Deployment🔍 Full site preview: https://deploy-preview-1815.quarto.org 🔄 Modified Documents |
Replace Twitter with Bluesky in examples and recapture website screenshots with dark mode variants - Update social media references from Twitter to Bluesky across blog posts, website docs, footer, and example projects - Recapture website navigation screenshots (sidebar-tools, breadcrumbs, navbar, hybrid-nav, reader-mode, repo-actions, about pages, myblog) with dark mode variants using `.include-dark` class - Fix fig-alt typos in website-navigation.qmd (cherry picked from commit 1cf3f47)
|
Successfully created backport PR for |
Documents the .qmd changes needed in PR #1815 to use the dark mode screenshots: add .include-dark class to image references, update alt text from Twitter to Bluesky.
…enshots Refactor about-pages to use Quarto profiles (one shared about.qmd, five _quarto-<template>.yml configs). Add sidebar-tools and myblog example projects. Add manifest entries for about-trestles, about-solana, about-marquee, about-broadside, sidebar-tools, and myblog.
- Add .include-dark to tools.png, myblog.png, and 4 about-page images (trestles, solana, marquee, broadside) so dark variants render - Replace Twitter references with Bluesky in alt text - Use concise alt text matching manifest descriptions - jolla and navbar-tools already updated in prior commits
Add developer tooling for capturing and maintaining documentation screenshots on quarto.org using Playwright. Screenshots are defined declaratively in a JSON manifest, then captured automatically — no manual screenshotting needed. The tooling lives under _tools/screenshots/ and includes: - capture.js: Playwright-based replay engine that renders pages, executes interactions (clicks, hovers, toggles), and captures screenshots with automatic light/dark variants - manifest.json: Declarative definitions for 17 screenshots (34 images with dark variants) covering about pages, navbar configs, sidebar layouts, breadcrumbs, reader mode, and repo action links - JSON Schema validation for manifest entries - Content-aware trim, crop, and clip-union post-processing via sharp - Spotlight effect for highlighting specific elements - Quarto profile support for rendering different configurations - Example projects under examples/ as minimal screenshot sources (includes quarto-demo as a git subtree) - CI compression workflow (.github/workflows/optimize-images.yml) for oxipng optimization after merge - /screenshot Claude Code skill for interactive screenshot authoring Developed alongside PR #1815 (Twitter → Bluesky migration), which served as real-world validation — all 19 screenshots in that PR were produced by this tool.
Add developer tooling for capturing and maintaining documentation screenshots on quarto.org using Playwright. Screenshots are defined declaratively in a JSON manifest, then captured automatically — no manual screenshotting needed. The tooling lives under _tools/screenshots/ and includes: - capture.js: Playwright-based replay engine that renders pages, executes interactions (clicks, hovers, toggles), and captures screenshots with automatic light/dark variants - manifest.json: Declarative definitions for 17 screenshots (34 images with dark variants) covering about pages, navbar configs, sidebar layouts, breadcrumbs, reader mode, and repo action links - JSON Schema validation for manifest entries - Content-aware trim, crop, and clip-union post-processing via sharp - Spotlight effect for highlighting specific elements - Quarto profile support for rendering different configurations - Example projects under examples/ as minimal screenshot sources (includes quarto-demo as a git subtree) - CI compression workflow (.github/workflows/optimize-images.yml) for oxipng optimization after merge - /screenshot Claude Code skill for interactive screenshot authoring Developed alongside PR #1815 (Twitter → Bluesky migration), which served as real-world validation — all 19 screenshots in that PR were produced by this tool. (cherry picked from commit b184c08)
…1976) Add developer tooling for capturing and maintaining documentation screenshots on quarto.org using Playwright. Screenshots are defined declaratively in a JSON manifest, then captured automatically — no manual screenshotting needed. The tooling lives under _tools/screenshots/ and includes: - capture.js: Playwright-based replay engine that renders pages, executes interactions (clicks, hovers, toggles), and captures screenshots with automatic light/dark variants - manifest.json: Declarative definitions for 17 screenshots (34 images with dark variants) covering about pages, navbar configs, sidebar layouts, breadcrumbs, reader mode, and repo action links - JSON Schema validation for manifest entries - Content-aware trim, crop, and clip-union post-processing via sharp - Spotlight effect for highlighting specific elements - Quarto profile support for rendering different configurations - Example projects under examples/ as minimal screenshot sources (includes quarto-demo as a git subtree) - CI compression workflow (.github/workflows/optimize-images.yml) for oxipng optimization after merge - /screenshot Claude Code skill for interactive screenshot authoring Developed alongside PR #1815 (Twitter → Bluesky migration), which served as real-world validation — all 19 screenshots in that PR were produced by this tool. (cherry picked from commit b184c08) Co-authored-by: Christophe Dervieux <christophe.dervieux@gmail.com>
This follows switch to bluesky in
We have a PR to move from twitter to bluesky in
This closes quarto-dev/quarto-cli#13204 too
We'll have more work for other support
Question
@cwickham we have several screenshot that will show result with past options:
quarto-web/docs/websites/website-navigation.qmd
Line 112 in 1559c73
Should we redo those screenshot and adapt the alt text too ?