Blogging for your community

AI-generated summary

davidb announces that Discourse is building an integrated blog feature, allowing users to publish articles directly from the community without a separate platform. Key planned features include comments linked to community topics, an editorial workflow with role-based permissions, customizable blog themes, support for multiple blogs per community, and import tools for Ghost and WordPress. While still in development, the team seeks feedback on use cases and current limitations.

blaisep expresses enthusiasm, noting the new tool would be more user-friendly than their current Python-based publishing workflow. LotusJeff highlights the importance of SEO for static pages, which they currently handle via WordPress alongside Discourse. They suggest that for the Discourse blog to replace their existing setup, it would need expanded SEO capabilities, easy integration of dynamic content blocks, and streamlined header/footer management.

newkid, a self-described novice, sees potential for their real estate community to use the blog as a channel for guiding members through property management.

The discussion deepens with mueu, who analyzes the potential of the blog feature to augment the Journal plugin and boost engagement among lurkers. mueu argues that blogs lower the barrier to entry compared to forum threads because they don’t explicitly demand a response, offering a “permission” to share experiences. This leverages Discourse’s unique position of providing a built-in, interested audience, thereby solving the common blogging problem of “shouting into the void.” mcwumbly responds to these insights, mentioning ongoing internal discussions about supporting free-form journaling. While not yet confirmed for the blog feature, the team recognizes the value in providing members with personal space to share thoughts without worrying about dominating shared community attention.

We’re building a blog into Discourse, so you can publish articles directly from your community, without needing to run a separate blogging platform alongside it.

Articles are written in the Discourse composer and published to a reader-facing blog, either at /blog or on its own domain.

What we’re working on:

  • Comments powered by the community: every blog article gets a community topic, and the full discussion is embedded under the public blog article. This means that readers can reply, like and sign in without leaving the blog
  • An editorial workflow with contributor, editor and publisher roles, covering drafts, review, approval and scheduled publishing
  • Blog themes, with an editor for adjusting the design and previewing changes
  • Multiple blogs powered by one community, each with its own address, theme and discussion category
  • Importing from existing blogs, starting with Ghost and Wordpress

This is still a work in progress and things will change as we go. We’d love to hear how you would use it and what your current blog setup is missing.

8 likes

Super cool, I have published to discourse from Sphinx and Nikola (two Python frameworks) and what you’re building would be way more convenient for normal people.

2 likes

I run WordPress as my base domain and Discourse on a subdomain. The main reason is that I can create static pages. WP provides rich SEO capabilities for static pages. We have a static page for every major keyword that is important to our niche. Each static page is content-rich and includes dynamic links to the forum for that specific keyword-related content. (90% of them rank 1 or 2)

We ran a blog for a long time, but over time the blog posts evolved into standard forum posts. We still have the blog, but its primary use is for guest posts (SEO revenue).

If we were to use it, the key features would need to be:

  • Expanded SEO capabilities
  • Easy integration into header/footer
  • Easy dynamic blocks for related content to move people into the forums
3 likes

I have never blogged so I am definitely a newbie. I am excited that this could be beneficial to our real estate community and another potential channel to help our members navigate and be in the know with managing their home or their next property journey.:folded_hands:

What seems to be the most interesting aspect of this experiment is how it’ll augment the Journal plugin and concepts therein. That’s the main way I would experiment with it at least.

Engagement is difficult. Most lurk, and most support questions are being routed to AI. But you can’t route sharing experiences/discoveries to AI.

Yet there’s something awkward about starting your own thread and sharing a log of the actual hobby when you’re a participant of some hobby forum. Thus giving others the permission to write whatever (within the domain of interest the forum is in) could be a way to increase engagement, and blogs could be a way of giving that permission. Some of the most successful threads I’ve seen across the forums is just asking people what are they doing. These people would never start a thread themselves!

Though some could argue that if a thread is too much to start, who would start a blog? I don’t know. That’s the experiment. It could fail. Though I think there’s a degree of separation with a blog that may encourage the lurker: a topic asks for a response, while a blog post asks nothing of the reader, really.

And Discourse has a unique position here: there’s a boundary. There’s a soft boundary in terms of the actual audience, which are users of the forum most likely, and a hard boundary on the theme of the blogs. The forum provides you the audience of people who are already interested in the same stuff. Discovery is built-in for all participants.

Because, ironically enough, blogging itself also has an issue with engagement, commonly depicted as “shouting into void.” And I think that’s because blogs don’t come packaged with a scope of topic, an audience, or even a purpose. What’s the incentive to start a blog? I think it makes sense if you are aiming to start some journey, to learn, to share what you’ve learned, to open yourself up to the opportunity of learning from others through comments: these are concrete benefits which seem to be often obscured in favor of “expressing oneself.”

1 like

@j.jaffeux were also talking about this more generally last week, not specifically in the context of the blog plugin, but more generally how we might support more of this kind of free form journaling, where each member has some space where they feel free to share what is on their mind, without worrying about whether they are taking up too much of the “shared attention” of everyone.

I’m not sure yet whether we’ll aim to address that with this blogging feature or not, but certainly I can see how it could be designed to address this use case as well.

1 like