Welcome to LeviFREE's Blog

1. Article Structure Check (3 mins)#

First, confirm if the content has an “actionable” structure, rather than just being a chronological account.

Minimum structural recommendations:

1. Problem Definition: What scenario does this article solve?
2. Prerequisites: Environment, versions, dependencies.
3. Step-by-step Process: Every step should be reproducible.
4. Troubleshooting Section: At least 3 common errors.
5. Summary: Applicable boundaries and next-step recommendations.

If more than 2 of these are missing, the article is usually not mature enough.

2. Information Density Check (2 mins)#

Quickly judge “is there substance”:

• Does it contain copyable commands?
• Does it explain why parameters are configured that way?
• Does it cover failure branches (not just the happy path)?
• Are clear version details provided?

The criterion: Readers shouldn’t have to “guess what you’re talking about.”

3. Basic SEO Check (3 mins)#

Before publishing a Jekyll article, verify at least these items:

• Does the title clearly express the topic and target audience?
• Does the subtitle fill in context?
• Are tags consistent with the body (avoid spamming tags)?
• Does the first paragraph explain the value within 80-120 words?
• Are there at least two H2 (##) headers?

If your site has internal search, the title and first paragraph determine the ceiling of your click-through rate.

4. Credibility Check (2 mins)#

Technical articles must establish credibility. At minimum, achieve:

• Mark the applicable OS for commands (macOS/Linux/Windows).
• Mark versions (e.g., Node 20, Python 3.12).
• Add warnings for high-risk operations.
• Cite sources for referenced materials (official documentation preferred).

The higher the credibility, the higher the reader retention time and return rate.

5. Compliance Check (2 mins)#

If you rely on ad monetization, you cannot skip this step.

• Does it contain misleading titles?
• Does it contain potentially non-compliant directions (attacks, bypasses, infringement)?
• Does it contain “conclusive assertions without evidence”?
• Are there obvious traces of scraping?

For uncertain paragraphs, it’s better to delete them than to gamble with moderation.

6. Jekyll Site-Level Check (2 mins)#

Quick check post-publish:

• Does the page render normally?
• Are internal links clickable?
• Are image paths correct?
• Did the article enter the archive page?
• Did feed.xml update?

You can run this locally first:

1
bundle exec jekyll serve

Then manually open the article to check the mobile layout and syntax highlighting.

7. A Copy-and-Paste Pre-Publish Template#

You can place this block directly at the top of your drafts:

1
[Pre-Publish Check]
2
- [ ] Is the title accurate and unexaggerated?
3
- [ ] Does the first paragraph clarify the target reader and benefits?
4
- [ ] Are prerequisites and version info included?
5
- [ ] Are there copyable commands and examples?
6
- [ ] Are there common errors and troubleshooting tips?
7
- [ ] Are risky operations marked?
8
- [ ] Are internal links and images checked?
9
- [ ] Has mobile reading experience been verified?
10
- [ ] Has it passed compliance checks?

When you consistently execute this for 20 articles, the quality of your articles will stabilize significantly.

8. Suggested Weekly Rhythm#

If you are a solo webmaster, you can use this rhythm:

• Monday: Topic selection and material organization.
• Wednesday: Write the body and code examples.
• Friday: Self-check + Publish.
• Weekend: Review data (search impressions, time on page, bounce rate).

Don’t treat “publishing” as the finish line; data retrospectives are the true beginning of content upgrades.