Blog Writing Guide

How to write, structure, and publish a post with the Pixel Logic blog editor.

Everything you need to write a polished post — from the first draft to the live page. The editor lives at Admin → Blog → New Post.

Creating a post

  1. Go to Admin → Blog and click + New Post.
  2. Give it a title — this also generates the URL slug (see below).
  3. Write your content in the editor. It's a what-you-see-is-what-you-get editor that stores clean Markdown under the hood.
  4. Click Save draft (or press Ctrl+S / Cmd+S) early and often.

A draft is private: only admins can see it. Use Preview (top right) to read it exactly as the public page will render it.

The URL slug

The slug is the post's permanent address: pixellogicteam.com/blog/<slug>.

  • Auto-generate from title (the checkbox above the slug field) is on by default for new posts — the slug follows the title as you type.
  • Want a custom slug? Untick the box and write your own (lowercase letters, numbers, and hyphens).
  • Changing the slug of an already-published post is safe: the old URL automatically becomes a permanent (308) redirect to the new one, so links and SEO are preserved. Still — pick a good slug early and keep it.

Chapters & structure

Headings are your chapters. Use H2 for chapters and H3 for sub-sections — readers get them as the sticky "On this page" navigation next to the post, and search engines use them to understand the structure.

  • The Chapters panel in the editor sidebar shows your outline live; click an entry to jump there, or use + Chapter / + Subchapter to insert a new H2 or H3 at the cursor.
  • The post title is the page's only H1 — that's why the editor offers H2–H4.
  • You need at least 2 chapters before the "On this page" sidebar appears on the public page.

Images

  • Cover image: 1200×630 (16:9) recommended — it's also the social-share card. The picker crops to 16:9 automatically. Always fill in the alt text (accessibility + SEO).
  • Inline images: click the image button in the toolbar, drag & drop a file into the editor, or just paste — a screenshot or an image copied from a web page is uploaded to our storage automatically and the hosted link is inserted.
  • Limits: JPG, PNG, WebP, GIF or AVIF, up to 1 MB per image. Compress before uploading (e.g. squoosh.app).
  • Deleting an image from your post also removes the file from storage on the next save — no manual cleanup needed.

Code blocks

Use the toolbar's code-block button (or type ``` on a new line) and pick the language — published posts get syntax highlighting and a copy button. Use inline code for short identifiers.

Excerpt, category & tags

  • Excerpt — 1–2 sentences shown on listing cards and used as the search result description. Write it like a hook, not a summary of everything.
  • Category — one per post: Case Study, Engineering, News, or Guide. Powers the /blog/category/… listings.
  • Tags — comma-separated keywords (e.g. ga4, server-side, gtm). Powers the /blog/tag/… listings and "Related posts".

SEO overrides (optional)

The defaults are good: the title becomes the meta title, the excerpt the meta description, and a branded social card is generated per post. Open SEO overrides in the sidebar only when you want a different search snippet, or to hide a post from search engines (noindex).

Your work is never lost

  • While you type, the editor backs the whole form up in your browser every second. If you close the tab without saving — crash, accidental close, forgotten save — reopening the post offers to restore the unsaved work.
  • Closing the tab with unsaved changes also pops a browser warning first.
  • The "backed up HH:MM" note next to the status chip tells you the safety net is active. It's per-browser, though — Save draft is still what stores your work on the server.

Publishing

  1. Complete your author profile first (Admin → Authors): name, title, bio, photo. Posts can't be published without one — your byline links to your public bio page.
  2. Click Publish. The post goes live at /blog/<slug> immediately, lands in the RSS feed and sitemap, and gets a social card.
  3. Editing later: open the post, make your changes, click Save changes — the live page updates right away, no unpublish needed. View live ↗ takes you to the public page.
  4. Unpublish moves it back to a private draft; Archive retires it.

Publish on a schedule

Set a date and time in the sidebar's Schedule publish card and save — the post publishes itself within ~5 minutes of that time (your author profile still needs to be complete). Clear the field and save to cancel. Scheduled drafts show a "scheduled" chip in the post list.

Share a draft for review

Need feedback before publishing? Use Share preview in the sidebar to create a private link anyone can open — no login needed. Disable it any time; once the post is published the link redirects to the live page.

Good-practice checklist

  • Title under ~60 characters (it's the search headline)
  • Excerpt written as a hook (under ~160 characters)
  • Cover image 1200×630 with alt text
  • At least two H2 chapters
  • Code blocks have a language selected
  • Tags + category set
  • Previewed before publishing