Confluence Blog Posts
Pages hold lasting knowledge, and blog posts carry news. A blog post records an update at a specific moment: a product launch, a team win, a policy change, or a weekly summary. Confluence stores each post in a timeline inside its space, and readers scroll from the newest item to the oldest.
Pages vs Blog Posts
| Feature | Page | Blog Post |
|---|---|---|
| Purpose | Lasting reference | Timely announcement |
| Organisation | Tree of parents and children | Timeline sorted by date |
| Child pages | Allowed | Not allowed |
| Best content | Guides, policies, plans | News, updates, recaps |
A simple test helps: if the content will matter in a year, write a page. If the content describes an event, write a blog post.
The Timeline Diagram
SPACE: Engineering
|
+-- Pages (tree) +-- Blog (timeline)
Home 12 June Release 4.2 shipped
+-- Runbooks 05 June New on-call schedule
+-- Architecture 29 May Team offsite recap
Creating a Blog Post
- Open the space where the news belongs.
- Click create and choose blog post.
- Write a clear title that names the news.
- Add the body text, images, and links.
- Publish the post to share it with the space audience.
The post date comes from the publish time. Space members who follow the space or watch the blog receive notifications according to their settings.
Writing a Strong Post
Lead with the News
Place the main point in the first two sentences. Busy readers decide within seconds whether to keep reading.
Keep Titles Specific
"Release 4.2 shipped with faster search" informs better than "Release update". A clear title earns clicks in the timeline.
Add One Visual
A screenshot, chart, or team photo breaks up text and adds context. Add alt text for accessibility.
Close with a Next Step
Tell readers what to do: read a linked page, join a call, or reply with feedback.
Engaging Readers
Readers react with emojis, leave comments, and mention colleagues. Comments turn a one-way announcement into a short discussion. Mention a decision-maker in a comment when a post needs an answer by a certain date.
Listing Posts on a Page
The blog posts macro displays recent posts on any page. A team home page can show the five newest posts, which gives visitors a live news feed without manual updates. Filter the macro by label to show only posts that carry a chosen tag, such as release-notes.
TEAM HOME PAGE +-----------------------------------+ | Welcome to the Engineering Space | | | | [Blog Posts macro] | | Label: release-notes | | Shows: 5 newest posts | +-----------------------------------+
Using Templates for Consistency
Weekly updates look better when they share one structure. Save a template with fixed headings, such as Highlights, Risks, and Next Week. Writers fill in the blanks, and readers know where to find each piece of information.
Common Mistakes
- Posting lasting instructions as a blog post, where the content sinks into the timeline.
- Publishing very long posts with no headings.
- Skipping labels, which makes old posts hard to find.
- Posting too often, so readers ignore notifications.
A Sample Weekly Update
Consider a team lead who posts every Friday. The post opens with one sentence: "We shipped the search upgrade and cut load times." Three short headings follow: Highlights, Risks, and Next Week. Each heading holds two or three bullets. Readers finish the post in under a minute and know exactly where the team stands. Over a quarter, the timeline becomes an honest diary of progress that managers and new joiners both enjoy reading.
Following and Notifications
Readers choose how much news they receive. Following a space or watching its blog sends alerts for new posts. Authors who post often should remind the team that they can tune notification settings, so frequent news never feels like noise.
Key Takeaways
- Blog posts carry dated news, and pages carry lasting knowledge.
- Posts form a timeline inside each space.
- Labels and the blog posts macro surface relevant updates.
- Short, specific, well-structured posts earn the most attention.