Repository navigation
feat: add the first two talks, built with Marp and published on GitHub Pages - #2
Merged
Merged
Conversation
A talk has to be something anyone can rebuild, give and change, as the project it is about is. Marp builds a talk's Markdown into a web page, a PDF and a PowerPoint file, with its speaker notes as text, and dist/index.html lists the talks. The theme is the app's own: its Standard light palette, Fredoka and Bangers, with every text color at WCAG AA or better. The fonts come from npm and are embedded at build time, so a talk loads nothing from anywhere else. npm run check:slides holds every talk to notes on every slide and a description on every picture, so that someone else can give it and everyone can follow it. Marp's katex, @xmldom/xmldom and basic-ftp are lifted to versions with their advisories fixed. extract-zip has no fixed version; Puppeteer uses it only to download a browser, which the build never does. The slides are CC BY 4.0 and everything else MIT, as REUSE.toml says.
A pull request, a fork's included, is checked before it is merged: every file's license (reuse), the workflow (actionlint, zizmor), the slides' notes and pictures, and a full build of every talk in the runner's Chrome. A push to main also publishes the build on GitHub Pages; its runs queue rather than cancel, so a deploy is never cut off. Actions are pinned to commits and the linters to versions, and Renovate keeps them, Marp and its overrides current, waiting three days for a new version, as the website does.
…e data" Solid Memo has no talk to give, and people who don't know Solid mostly see it in demos. This 40-minute talk for developers new to Solid tells why the app was built the way it is, no server of its own and one bill, the domain at 123.75 SEK a year, and shows the app as proof that Solid can carry a polished app for anyone who wants to learn. Its parts: no server of its own, free for anyone, open from the code to the decisions, and the proof: nine pod server setups, user journeys, coverage and stable formats. It ends with ways to join in, and a code to sponsor the domain. Every figure was checked against the website's main on October 22, 2026, and the notes say which to check again before the talk. The screenshots and the logo are the website's, under its license, MIT.
Someone who finds a talk here needs to know they may give it, under which license, and what to check first; a contributor, how to build it and which rules a talk is held to. The README says the first and how the repository is made; CONTRIBUTING.md the rules, with the website's code of conduct and governance.
…on Solid The first talk explains Solid from the start, which wastes a Solid audience's time. This one is 30 minutes, questions included, for app developers, server implementers and spec authors: logging in with no backend, keeping data in someone else's pod, what differs between the nine pod server setups the app is tested against, two patterns worth taking, and what the app asks of identity providers, servers, libraries and the specs. Every claim was checked against the website's main at 6.29.18 on 2026-11-04, with the source in the speaker notes where it is not obvious.
The talk was written on 2026-10-22 and the app has moved on: the library holds 115 entries with 9 courses, the Capitals deck is at version 4 with Wikidata subjects, the deck list screenshot was taken again, and GitHub Sponsors is live. The notes also said more than the repository backs: axe runs on a phone only for the guest and reload journeys, Zenodo has not archived every release, and the servers are pinned in different ways. The notes now point to the practitioners' talk for a Solid audience.
ixuz
added
ci/cd
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What and why
Solid Memo had no talk to give. People who don't know Solid mostly see
it in demos and prototypes, and the app is meant to show the opposite: a
polished app for anyone who wants to learn, with no server of its own
and one bill, the domain. This adds the talk issue #1 asks for, the
tooling to write, build and publish it, and a second talk for people who
already build on Solid.
861dd88): each talk is Markdown in its own folder,built by Marp into a web page you can click through, a PDF and a
PowerPoint file, with the speaker notes as text.
dist/index.htmllists the talks. The theme is the app's own (its Standard palette,
Fredoka and Bangers) and every text color meets WCAG AA. The fonts are
embedded at build time, so a talk loads nothing from anywhere else.
npm run check:slideschecks that every slide has notes and everypicture has a description.
7096cd6): every pull request, forks included, runsreuse lint, actionlint and zizmor, the slide checks and a full build in therunner's Chrome. A push to
mainalso publishesdist/on GitHubPages. Actions are pinned to commits, and Renovate keeps them and Marp
up to date.
ae6dbee,606d530):the talk from Talk: "Build the app, let users keep the data" for a general tech audience #1, 40 minutes for developers who don't know Solid, in
34 slides. The outline grew from the issue's 30. Its figures were
checked again against the website's
mainat 6.29.18 on November 4,2026, and the notes say which to check before giving it.
1d52f77): who may give a talk andunder which license, how to build one, and the rules a talk is held to.
Beyond #1: "Nine server setups, no server of its own" (
0a8b058),30 minutes with questions, for app developers, server implementers and
spec authors. The first talk explains Solid from the start, which
wastes a Solid audience's time. This one covers logging in with no
backend, keeping data in someone else's pod, what differs between the
nine pod server setups, and what the app asks of the ecosystem. Every
claim was checked against the website's
mainat 6.29.18.Before merging: the repository's Pages source must be "GitHub
Actions" (Settings → Pages). Otherwise the deploy job fails on the first
push to
main.Closes: #1