Blogging in PageMotor
PageMotor has no blog button, and that surprises people arriving from WordPress. The surprise runs the other way too: most of a blog was already there. This guide shows what core gives you, how to run a blog with nothing but pages, and when the free EP Blog plugin earns its place.
A blog is really four things wearing one name: a place to write (posts with dates and authors), a front page for them (newest first, with excerpts), a way to group them (categories and tags), and the plumbing around them (feeds, comments, scheduling, search). PageMotor core covers the first almost completely, half-covers the second, and the plumbing is standard EP Suite territory. The only piece genuinely missing was the automatic front page, and that is what EP Blog adds.
In this guide
1 What core already gives you
PageMotor stores every piece of content with a publish date, a last-modified date and an author. Every page can have a Parent, and the URL nests under it: a page with Parent set to your /journal/ page lives at /journal/my-post/. Drafts, live and trash states are built in.
In other words, the data model is already blog-shaped. What core does not do is loop over that data on the front end. There is no screen that says “list everything under Journal, newest first, with an excerpt of each”. There are also no categories or tags, and no reader-facing feed in core itself.
The missing organ is the index loop: the automatic newest-first front page. Everything else about blogging is either already in core or already in the suite.
2 Route one: a blog made of plain pages
You can run a perfectly respectable blog today with nothing but core pages. This is not a workaround; for a small, considered publication it is arguably the better tool.
How
- Create a page called Journal (or News, or Essays). It lives at
/journal/. - Write each post as its own page, and set its Parent to the Journal page. The URL nests:
/journal/my-first-post/. - The Journal page itself is your index, and you curate it by hand: a heading, a line or two about the post, a link. When you publish, you add its entry at the top.
Why this is genuinely good
The hand-built index is a feature in disguise. You choose the order, so your best work can sit on top forever instead of sliding off page three. You write the blurbs, so they read like an editor wrote them rather than the first 240 characters of each post. And there are no moving parts at all: nothing to configure, nothing to update.
When to use it
3 The pieces that were already in place
These four plugins are what most people actually mean by “blog features”, and none of them needs EP Blog. Each one works identically with plain pages and with EP Blog posts, so nothing you set up here is wasted if you change route later.
EP RSS — the feed
What: serves your site’s feed at /feed (RSS) and /feed/atom (Atom), newest first, with auto-discovery tags so readers like Feedly and NetNewsWire find it from your homepage URL alone.
Why: a feed is how regular readers actually follow a small site. It also gives search engines a fast signal that you have published something new.
When: the moment you have content people might want to follow. On the pages route your pages appear in /feed automatically; with EP Blog you additionally get a posts-only feed at /feed/rss/post.
EP Comments — the conversation
What: a full comment system with threading, moderation, spam protection and notification emails. It attaches to any content, pages included, with a per-page toggle.
Why: comments turn broadcasting into conversation, and moderated first-party comments are worth more than a social media thread you do not own.
When: when you want replies where the writing lives. Skip it if you would rather point readers at email or a forum; a blog without comments is still a blog.
EP Scheduled Content — the queue
What: set a future date and time on any draft and it goes live by itself.
Why: writing in batches and publishing on a rhythm is the single easiest way to keep a blog alive. The Tuesday post can be written on Saturday.
When: when you notice you write in bursts. It works on drafts of any type, so the pages route benefits equally.
EP Search — the archive key
What: a search form and results page over your titles and content, with highlighted excerpts.
Why: once the archive is bigger than one screen, search is how people (including you) find the piece from last spring.
When: from roughly your twentieth piece of content onward, or immediately if your posts are reference material.
Also worth knowing: EP SEO handles the social sharing cards and metadata for whichever route you choose, and every plugin above is on the free tier of the ElmsPark update channel, like EP Blog itself.
4 Route two: the EP Blog plugin
EP Blog adds the missing organ and the taxonomy around it. Concretely, over the pages route you gain:
- A Post content type with its own screens under Content, so posts stop mingling with your real pages.
- The automatic index:
[ep-blog]on a page renders every live post, newest first, with excerpts, category badges, bylines and pagination. Publishing becomes one edit, not two. - Nested categories and tags, defined once in settings, picked per post from a dropdown. Indent a category to nest it, and filtering a parent includes everything beneath it.
- Category archive URLs, optional: each category gets its own real page at
/journal/category/news/, with its own title and description for search engines. - Bylines and post navigation: date and author on each post, older/newer links between posts.
- BlogPosting structured data on every post, automatically.
- A posts-only feed at
/feed/rss/postwhen EP RSS is active.
On category archives being real pages. That is deliberate, and it is the same idea Chris describes: everything is a Page. Because each archive is an ordinary PageMotor page rather than a URL conjured by routing code, it carries its own title, meta description and social card, lands in your sitemap, works with breadcrumbs, and can take an introduction of your own above the list. The URLs stay flat however deep the nesting goes, so re-parenting a category never breaks a link you have already published.
Setting it up
- Activate EP Blog, then define your categories under Plugins → Blog, one per line.
- Create your
/journal/page with[ep-blog]in its body, and enter that URL as the Blog index URL in settings. - Create posts under Content → Post, each with the Journal page as its Parent.
- Optionally put
[ep-blog-meta]at the top of each post and[ep-blog-post-nav]at the bottom.
Posts render through your theme automatically; EP Blog clones your theme’s Page template into a Post template the first time it runs, so there is no Theme Editor work.
Migrating from the pages route later? Nothing is lost. Your hand-built index page simply gains the [ep-blog] shortcode below (or instead of) its curated list, and new writing goes in as posts. Existing pages can stay pages; the two live happily side by side.
5 How to choose
| Plain pages | EP Blog | |
|---|---|---|
| Front page of posts | Hand-curated | Automatic, newest first |
| Effort per post | Two edits | One edit |
| Categories and tags | None | Nested, filterable, rolled up |
| Category archive URLs | Build them by hand | A real page each, optional |
| Bylines, older/newer links | Hand-written if at all | Automatic |
| Editorial control of the index | Total | Chronological by design |
| Feed (EP RSS) | /feed | /feed plus /feed/rss/post |
| Comments, scheduling, search | Identical | Identical |
| Moving parts | Zero | One plugin |
The short version: if you publish a few deliberate pieces a year and want to curate how they are presented, plain pages plus EP RSS is a complete and elegant blog. The moment publishing becomes a habit rather than an event, install EP Blog and let the index keep itself.