A TWiR-style newsletter repository for This Week in microVMs.
This is intentionally shaped after the public workflow used by rust-lang/this-week-in-rust:
draft/contains the next issue andDRAFT_TEMPLATE- contributors submit PRs against the current draft
content/stores published issuespublishing/owns build/email commandsjust websitebuilds a local static sitejust emailgenerates an email-ready HTML file- link style and editorial rules live in the README
just setup
cp .env.example .env
just next
just check
just website
just email
just buttondown-draftFrom the repo root:
just website
just emailOr directly from the publishing directory:
cd publishing
just website
just emailThe publishing/justfile builds a Docker image and runs the local builder inside it. This mirrors the TWiR habit of keeping publishing/build concerns isolated from the editorial repo.
To propose content for inclusion in the next newsletter, create a pull request updating the current file in draft/.
You can also open an issue using the link suggestion template.
This Week in microVMs is intended to highlight practical work in microVMs, secure sandboxes, lightweight virtualization, and AI-native runtime isolation.
Generally good:
- maintainer updates from relevant projects
- deep dives about Firecracker, Cloud Hypervisor, Kata, QEMU, KVM, Lima, Incus, Wasm sandboxes, or similar systems
- practical walkthroughs with enough technical depth
- security research about isolation, sandbox escapes, egress policy, or runtime trust boundaries
- release notes that explain why changes matter, not just raw changelogs
- talks, papers, slide decks, demos, podcasts, and videos
- calls for participation in relevant open source projects
- relevant events and jobs
Generally not good:
- pure marketing copy
- bare GitHub repo links with no explanatory writeup
- duplicated links from recent issues
- paywalled links unless clearly marked and unusually important
- links requiring email capture to access
- rants or personal attacks
- undisclosed LLM-written articles
- Link text should generally match the page title.
- Use the canonical URL.
- Remove unnecessary tracking parameters such as
utm_sourceandutm_campaign. - Prefix media where useful:
[video][audio][slides][paper][series]
- Use two-letter language prefixes for non-English content, such as
[ZH],[ES],[FR].
Editors sort community links into sub-categories:
- Official / Maintainer Updates
- Project / Tooling Updates
- Newsletters
- Research
- Observations / Thoughts
- Walkthroughs
- Security / Isolation
- AI Agent Sandboxes
- Miscellaneous
From publishing/:
just website
just emailOutputs:
publishing/output-website/
publishing/email/The email artifact is:
publishing/email/latest-email.htmlTWiR mostly treats the live draft as the queue. This repo keeps that model, but also includes queue/links.md as your personal scratchpad.
Use queue/links.md for rough capture. Move final items into draft/YYYY-MM-DD-this-week-in-microvms.md before publication.
This repo deliberately keeps the builder command-oriented:
twimvmbuilder check
twimvmbuilder build-site
twimvmbuilder build-emailLater, mvm can wrap those commands without changing the editorial workflow.
just setup # create .venv and install local builder
just new-draft 2
just check
just website
just email
just build
just serve
just publishThe builder is installed from tools/twimvmbuilder, so development stays local and editable.
new-draft now defaults to today's date:
just new-draft 2Use an explicit date when planning a future issue:
just new-draft-date 2 2026-05-20Publishing normally uses the Date: metadata already in the draft:
just publishIf the draft slipped and you want the published issue dated today:
just publish-todayOr stamp it with a specific date:
just publish-date 2026-05-20This starter includes a safe Buttondown draft integration.
One-time setup:
export BUTTONDOWN_API_KEY="..."Preview what would be sent:
just buttondown-dry-runCreate a Buttondown draft from the current issue:
just buttondown-draftFull prepare flow:
just buttondown-readyThis creates a draft only. It does not send to your subscribers. Review and send manually in Buttondown.
See docs/buttondown.md.
just email now generates conservative email-safe HTML and a plain-text fallback:
publishing/email/latest-email.html
publishing/email/latest-email.txtThe default Buttondown integration sends the generated email-safe HTML as a draft. You can also send Markdown with:
just buttondown-draft-mdSee docs/email-safe.md.
The root Justfile loads .env automatically.
just setup
cp .env.example .env
# edit .envStart the next issue:
just nextMove private queue items into the draft:
just queue-promotePreview the full ship flow without creating a Buttondown draft:
just ship-dry-runCreate a Buttondown draft:
just shipCreate a Buttondown draft and archive locally:
just ship-archiveStamp the issue date to today, create a Buttondown draft, and archive locally:
just ship-todaySee docs/easy-mode.md.
.envloading from the rootJustfilejust statusto show current draft, next issue number, and Buttondown key statusjust nextto infer the next issue number automaticallyjust queue-promoteto move strong candidates from the private queue into the current draftjust ship*commands for one-command weekly publishing prep- local
build-localpath if Docker is annoying
This starter now includes a guarded weekly GitHub Action:
.github/workflows/weekly-automation.ymlIt counts links, runs Codex when the threshold is met, builds the issue, creates a Buttondown draft, and can optionally send if BUTTONDOWN_AUTO_SEND=true.
If there are not enough links, it sends a maintainer email instead of forcing a weak issue.
See docs/github-automation.md.
The chrome-extension/ folder contains a small Manifest V3 extension that saves the current page as a GitHub issue labeled link-suggestion.
See docs/chrome-extension.md.
just website now behaves much more like this-week-in-rust:
just websiteIt builds the Docker image, generates the site, prints a loud publisher banner with the latest issue URL, and starts a server on port 8000.
Use this if you only want to build without hosting:
just website-buildSee docs/twir-like-publishing.md.
The root command surface is documented in:
docs/just-commands.mdUseful shortcuts:
just help
just status
just artifacts
just ship-dry-runThe publishing Dockerfile now only uses the directories required for this newsletter:
content/
draft/
queue/
publishing/
tools/It no longer references placeholder sources/, plugins/, or themes/ directories.
The starter no longer includes placeholder sources/, plugins/, or themes/ directories.
Those existed only to resemble the shape of the upstream this-week-in-rust repository. For this newsletter, the easiest useful publishing flow only needs:
draft/ current issue
content/ archived issues
queue/ private capture queue
publishing/ Docker publishing tools
tools/ local builderNormal weekly path:
just next
# edit draft
just check
just website
just email
just buttondown-draft
# review/send in Buttondown
just publish-todayFast non-interactive prep:
just ship-dry-run
just ship- Drafts now use YAML frontmatter.
just websiteno longer tries to delete a Docker-mounted output directory.- The Docker image no longer copies editorial directories at build time; the repo is mounted at runtime.
- GitHub Issues can now be pulled into the queue:
just issues-report
just issues-import-dry-run
just issues-import
just issues-import-acceptedSee docs/github-issues-queue.md.
just next is now weekly-first. It looks at the latest issue date in draft/ and content/, then creates the next draft seven days later.
For example, if the latest draft is:
draft/2026-05-13-this-week-in-microvms.md
then:
just nextcreates:
draft/2026-05-20-this-week-in-microvms.md
Explicit commands:
just next # create next weekly issue using latest issue date + 7 days
just next-today # explicitly create today's draft
just next-today-force # overwrite today's draft
just next-date 2026-05-20
just next-date-force 2026-05-20You can now run a live-ish preview while editing:
just watchThen open:
http://localhost:8000/It watches:
draft/
content/
queue/
templates/and rebuilds the static site when files change.
Other variants:
just watch-docker
just watch-build
just watch-port 8080