After experiencing the frustration of losing blog content on various platforms, I've realized the importance of owning my content data. As a result, I've migrated my blog to GitHub Pages. However, I've encountered issues with popular static blog setups like Hugo + PaperModX, which don't handle math equations well and have complex requirements for image paths.

To address these challenges and to have the freedom to customize my blog extensively, I've developed QuipQuick, my own static blog engine. For a live deployment of this engine, please visit my blog.

Features

• Full support for inline and block math equations.
• Integration with Google Analytics.
• Ability to easily link to GitHub Discussions.
• Embedding of YouTube videos in blog posts.
• RSS feed.
• Footnote.
• Customizable theme.
• Code block with syntax highlighting.
• Images are resized for quick loading.
• Image sources.

Install

cargo install --git https://github.com/shi-yan/QuipQuick.git

Usage

To use QuipQuick, you'll need to set up two folders. One folder will contain all your raw content, including markdown files, images, and the manifest file quipquick.toml. This folder should be version controlled in a private git repo. The second folder will be a target folder to hold the generated HTML pages. This folder will be deployed as GitHub Pages.

1. Create a New Blog Boilerplate

quipquick new

This command will set up a new blog template for you to start writing. Here is the folder structure:

• quipquick.toml This is the manifest file, it contains the global settings for your blog and a list of content folders. Each content folder contains the content (markdown and images) of a single blog post.
• template This is the template folder, feel free to modify what's inside to update the theme.
• dummy_post This is an example of a content folder. Within this folder, there should be a content.md file for the markdown content and images used by the markdown. In the manifest file quipquick.toml, the content array should contain the content folder names. If a content folder is not included in the array, the post is considered a draft and won't be published.
• logo.png This is a logo image. This image will be used as the icon when you share your blog on social media or for the RSS feed.

2. Create a new post

quipquick write

This command generates a content folder based on the title of your post and update the manifest file.

1. Publish your blog

quipquick pub

After publishing, the target folder should contain the updated HTML pages ready for deployment. You'll need to push these changes to GitHub to deploy your blog as GitHub Pages.

Customize theme

After the blog boilerplate has been generate using the new command, there will be a template folder. Within the folder, you can find two html templates and one stylesheet. The template are written in the handlebars template syntax. You can modify these files to change the theme.

Syntax

QuipQuick's markdown parser is based on markdown-rs, which supports the CommonMark syntax with a few extensions. This guide focuses on QuipQuick's specific extensions; for CommonMark syntax, please refer to the official document.

I made a few extensions with the principle of augmenting the markdown parser by adding features on top of the CommonMark syntax, without modifying the parser itself:

1. Embed YouTube Videos:

 \```youtube
 <youtube_video_id>
 \```

Replace <youtube_video_id> with the actual ID of the YouTube video.

2. Image Sources:

QuipQuick allows you to credit image sources for images used in your blog. Use the following syntax:

![alt_text|<source_1_url>|<source_2_url>](<image_url>)

Replace alt_text with the alternative text for the image and source_1_url and source_2_url ... with the URLs of the image sources. image_url should be the URL of the image you are embedding.

Note: QuipQuick does not support image captions; the alternative text serves as the image caption.