Content Pipeline Is Ready — Artyom Tetyukhin

At this point, the blog has all the features I need for future posts. Code snippets, multi-language examples, math, diagrams, and publishing metadata are all in place. The setup now feels stable enough that I can focus on the content itself rather than spending time fixing formatting or tooling.

Code Formatting

Simple Example (CodeBlock)

Regular code blocks are handled by CodeBlock.svelte, which is enough for most single-language examples. That covers the common case where I just need a clean snippet with syntax highlighting and copy support.

package main

import "fmt"

func main() {
    fmt.Println("Hello, World!")
}

Advanced Example (CodeTabs)

For posts that need comparisons across languages, CodeTabs.svelte makes the examples much easier to read. It is especially useful when the same idea needs to be shown side by side in different languages without turning the page into a long sequence of repeated snippets.

func binarySearch(nums []int, target int) int {
	lo, hi := 0, len(nums)-1
	for lo <= hi {
		mid := lo + (hi-lo)/2
		if nums[mid] == target { return mid }
		if nums[mid] < target { lo = mid + 1 } else { hi = mid - 1 }
	}
	return -1
}

Math & Diagrams

KaTeX Support

Math support is handled with KaTeX, which is more than enough for the kind of notation I expect to use in future posts. If I need to draft equations in the browser, LaTeX Editor is a convenient option.

Inline: $E = m c^{2}$
Block:

\frac{n !}{k ! ( n - k )!} = (k n)

Mermaid Diagrams

Diagrams are powered by Mermaid, which makes it easy to keep visual explanations close to the text. For drafting and testing diagrams, the Mermaid Live Editor is useful.

graph LR A[Start] --> B{Check} B -- OK --> C[Process] B -- Fail --> D[End] C --> B

flowchart TD A[Christmas] -->|Get money| B(Go shopping) B --> C{Let me think} C -->|One| D[Laptop] C -->|Two| E[iPhone] C -->|Three| F[fa:fa-car Car]

Public API & Resources

The blog also exposes a few useful endpoints that are already ready to use:

Markdown Kitchen Sink

This section exists mostly as a reference point for the post renderer. If typography, spacing, or prose styles ever drift between local development and production, these are the elements that should make it obvious.

A good content pipeline should make ordinary writing feel boring in the best possible way.

The current markdown layer already covers the basic text structures I expect to use most often:

unordered lists for short collections
ordered lists for step-by-step notes
tables for small comparisons
blockquotes for emphasis or commentary

That also makes it easier to keep technical posts readable without reaching for custom components too early:

start with plain markdown
switch to CodeBlock or CodeTabs when code needs more structure
use math or Mermaid only when the idea genuinely needs it

Element	Purpose	Status
Lists	Organize short sequences	Ready
Tables	Compare small pieces of data	Ready
Quotes	Highlight commentary or emphasis	Ready
Code	Show snippets and examples	Ready

Links & Resources

These are the main tools behind the current setup:

Framework: Svelte Documentation
Markdown: Markdown Syntax Guide
Math Editors: LaTeX Editor
Diagramming: Mermaid Live Editor

Overall, this is already enough for the kind of writing I want to publish next. The core pieces are in place, the workflow feels stable, and future posts can focus more on content than on formatting.