Yufan Personal Weblog

This is a personal weblog for Yufan Sheng which is built on Astro and hosted on zeabur.

History

The blog's source code has evolved through four stages. Initially, it was built on WordPress in 2011. In 2017, I switched to Hexo and converted all my blog posts to Markdown; the code is available in the Hexo branch. By 2024, the blog had been rewritten using Next.js with App Router; you can find this version in the Next branch. Currently, the blog has transitioned to Astro, which is located in the Astro branch.

Core Frameworks

• Node.js: The latest Node.js LTS
• Astro: Core engine
• Artalk: The self-hosted comment system
• Fuse.js: Search engine
• Postgres: The view counter and like button for all my posts

Local Development

This weblog is still under development. Many ideas and thoughts are in my checklists. You can fork and clone this project for your own use. But do so at your own risk.

The project uses npm for development. Run it locally with these commands:

# Install the dependencies by using bun.
npm install

# Init git hooks.
npx husky

# Check the newer dependencies.
npm update

# Start local development with a live preview. The weblog is hosted on http://localhost:4321
npm run dev

Postgres Database

This blog uses Postgres to store post views and favorites. For security reasons, the configuration isn't defined in the .env file. Modify the .env.example file and rename it to .env for local development.

You can create a Postgres database by installing Postgres.app. The default username is your system username, with no password.

Create and initialize the database and user with these commands:

-- Create a database.
CREATE DATABASE <db>;

-- Create a user.
CREATE USER <db_user> PASSWORD '<strong_password>';

-- Grant the connection.
GRANT CONNECT ON DATABASE <db> TO <db_user>;

-- Grant the database privilege.
GRANT ALL PRIVILEGES ON DATABASE <db> TO <db_user>;

-- If you are using Postgres 15 or above.
-- Switch to the created database and execute SQL.
GRANT ALL ON SCHEMA public TO <db_user>;

Most tables are created by the Artalk. Execute the Artalk to create the tables.

The like table should be created manually. Execute the SQL below.

-- Sequence and defined type
CREATE SEQUENCE IF NOT EXISTS atk_likes_id_seq;

-- Table Definition
CREATE TABLE "public"."atk_likes" (
  "id" int8 NOT NULL DEFAULT nextval('atk_likes_id_seq'::regclass),
  "created_at" timestamptz,
  "updated_at" timestamptz,
  "deleted_at" timestamptz,
  "token" varchar(255),
  "page_key" varchar(255),
  PRIMARY KEY ("id")
);

-- Create table index
CREATE INDEX IF NOT EXISTS "idx_atk_likes_token" ON "public"."atk_likes" ("token");

Comments Integration

This weblog use artalk as its backend comment service. But since artalk didn't provide the latest comments API. We decide to query it directly from Postgres database. So the comments and fav clicks are living in the same database.

Writing

All the posts should be placed in src/content/posts directory with MDX format. All the pages should be placed in src/content/pages directory with MDX format. You can add any scripts or other customizable features by leveraging the MDX.

Front Matter

Front-matter is a block of YAML at the beginning of the file that is used to configure settings for your writings. Front-matter is terminated by three dashes when written in YAML.

---
title: Hello World
date: 2013/7/13 20:46:25
---

Post Front Matter Settings

Setting	Description	Required	Default
id	ID (unique), used as the permalink	true	Filename
title	Title	true	Filename
date	Published date	true
updated	Updated date	false	Published date
comments	Enables comment feature for the post	false	true
tags	Tags	false	null
category	Category	true	null
summary	Post summary in plain text	false	First 140 characters
cover	The cover image	false	null
published	Whether the post should be published	false	true

Pages Front Matter Settings

Setting	Description	Required	Default
id	ID (unique), used as the permalink	true	Filename
title	Title	true	Filename
date	Published date	true
updated	Updated date	false	Published date
comments	Enables comment feature for the post	false	true
cover	The cover image	false	null
published	Whether the post should be published	false	true

Weblog Design

Almost all the design resources are placed in the file yufan.me.sketch. I mainly use the Sketch as my design tools.

The favicon is almost the same as the weblog logo. The main different is that we simplify the elements used in logo. Pick up the main park from the logo and change the dot color for readability in small icon. The background color is included in the exported favicon. That is because we want to make sure it could be viewed clearly in any browser.

The size of the favicon is following this tutorial to get it worked everywhere.

Deploy the Weblog

This weblog is deployed on the zeabur platform. You can check their documents and get your own weblog to be published without any budget at first.

Or you can host on your own machine. Use Dockerfile to build a image and run it locally.

The comment system is leverage the Artalk, a self-hosted comment system. You should host it on your own machine. But it can be modified and changed to any other comment solutions. For instance, the giscus is an opinionated choice.

TODO Checklist

• Check article grammar errors by using ChatGPT. Remain 90 posts.
• Add music to the articles. Remain 90 posts.
• Add cover for all my posts. Remain 33 posts.
• Clean up the legacy links in the weblog comments.
• External the article inner links with different target.
• Artalk integration with custom stylesheet.
• Slide share components integration.

Long Term Goals

• Add han.js support for better typography.
• Drop bootstrap, in favor of tailwind css.
• Use self developed duoshuo as the comments solution.

License

The source code of this blog is licensed under the MIT license, feel to free to use it without any legal risks.

The content of this blog's posts is licensed under the CC BY-NC-SA 4.0 license.

Logo Fonts License

The fonts used in weblog logo is M+A1 with license, UnGungseo with license, and Iroha Mochi with license.

They are the fonts that can be used in business without any charge.

Article Font License

The OPPOSans 3.0 is used for reading in my weblog. It can be used in business scenarios without any modification. I just placed it under the opposans directory for better integration. The license file is here

Open Graph Font License

The Noto Sans Simplified Chinese is used for rendering the open graph image in my weblog. It can be used in business scenarios without any modification. The license file is here

Third Party Codes License

Some codes in this project is copied from other project. I have add the comments in the files's header.

The source codes used from third party projects are:

• seo.ts from flexdinesh/blogster with license
• og.ts from yuaanlin/yual.in with permission
• images.ts from zce/velite with license
• images.ts from vercel/next.js with license