quick-remix is a small blog built with Remix. Posts are Markdown files in a posts folder, with the title in their front matter. Anyone can read them at /posts, and an admin area behind a GitHub login lists every post, with forms to create, edit and delete them.
It was built in the first days of Remix’s public release: the repository was created about two hours after Remix 1.0.4, the version it uses, was published to npm. All 17 commits are from November 22 and 23, 2021, and it hasn’t changed since. It started from Remix’s starter template, whose welcome page is still the home page, and the last commit deleted the starter’s demo routes.
What’s in it
- Posts from files.
app/post.tsreads, writes and deletes Markdown files with Node’sfs, reads the title with front-matter, and renders the body to HTML with@ryanflorence/md. Git ignores thepostsfolder, so no posts are committed. - An admin area.
/adminlists the posts in a sidebar. A new post takes a title, a slug and Markdown, and the route’s action sends back which fields are missing. Editing keeps the slug, and Delete removes the file. - GitHub login. remix-auth’s GitHub strategy signs you in and keeps your GitHub id and email in a cookie session. The admin layout’s loader sends anyone who isn’t signed in back to the home page. Logout destroys the session.


@ryanflorence/md runs code blocks through Shiki, but the colors it outputs are CSS variables that the app’s stylesheets never define, so code shows up without highlighting.


How it’s built
It’s Remix 1.0.4 with React 17 and TypeScript, served by the Remix App Server. Routes are files under app/routes, with loaders and actions that run on the server, and the post forms use Remix’s <Form>. While a form submits, useTransition switches its button to “Creating…” or “Updating…”. The starter’s stylesheets set the look, including a dark theme that follows the system setting.

Deployment attempts
The history shows two deployment setups added and removed on the first night: a pm2 config that builds and starts the app in production mode, and a Fly.io app called quickmix, with a Dockerfile on Node 16. The next morning, a commit named “test self deploy” changed the home page heading to “Welcome to Remix testing!”, and the next commit changed it back. The repository doesn’t record where it ended up running.
Running it today
With Node 16, npm install still works (its postinstall runs remix setup node), and npm run build followed by npm start serves it on port 3000. The server needs GITHUB_CLIENT_ID, GITHUB_CLIENT_SECRET, GITHUB_CALLBACK_URL and SESSION_SECRET, which .env.sample lists, and signing in needs a GitHub OAuth app.
For the screenshots, those variables were local placeholders and nothing contacted GitHub. The admin pages were opened with a session cookie signed locally for a sample user, demo@example.com, and the three posts are samples created through the admin form.
The creation date shown here is the GitHub repository’s UTC creation date. The screenshots were captured by running the project locally with sample posts and a locally signed session in place of the GitHub login, and the code card shows a real file from the repository.