an ssg written in shell

Summary

The author details the creation of a static site generator using POSIX shell. The article outlines the script's functionality, including markdown rendering, metadata extraction, and template processing. The author favors simplicity over established frameworks.

Key Takeaways

1. A static site generator was built using POSIX shell to avoid large JavaScript frameworks.
2. The script handles markdown rendering, metadata extraction, and template processing.
3. The author uses `sed` and `envsubst` for HTML manipulation and templating.

Statement Breakdown

• Claimed Facts: 60% of statements the article presents as facts
• Opinions: 30% of statements classified as editorial or subjective
• Claims: 10% of statements surfaced for additional reader evaluation

Credibility & Bias Reasoning

Credibility assessment: The article is a personal blog post detailing the author's experience creating a static site generator. The technical details are specific and plausible, but lack external verification. The author's expertise is self-reported, which lowers the overall credibility.

Bias assessment: Technological Purism. The author expresses a clear preference for simple, self-made tools over established JavaScript frameworks. This bias is evident in the decision to use POSIX shell and string concatenation instead of more conventional methods. The article frames this choice as a rejection of complexity and bloat.

Note: This article is a personal account. Verify claims independently before relying on them.

Credibility flag: Self-Reported

Claimed Facts (7)

• This is a direct statement of the script's purpose.
• This claims the website is generated by the script.
• This describes the input and output formats of the script.
• This outlines the directory structure required by the script.
• This states the markdown rendering engine and its features.
• This describes the post rendering process.
• This explains the templating method used.

Opinions (6)

• The description of the project as "mildly cursed" and "fun" is subjective.
• This expresses a personal preference for HTML and against JS frameworks.
• The tone is subjective and welcoming.
• This is a statement of personal preference.
• This is a subjective reaction to the amount of custom markdown functionality.
• This is a subjective and humorous description.

Claims (3)

• The description is hyperbolic and lacks specific details to verify the claim.
• The claim of being "decently fast" is subjective and lacks a clear benchmark.
• The claim that it's "safe to do" is potentially dubious without further security analysis.

Key Sources

• Author — Blogger
• comrak — Markdown rendering engine