Blogging for your community

AI-generated summary

Davidb announces a new blog feature being built directly into Discourse, eliminating the need for separate blogging platforms. Articles are written using the Discourse composer and published to a reader-facing interface at /blog or a custom domain. Key features under development include community-powered comments embedded under articles, an editorial workflow with distinct contributor roles, customizable blog themes, support for multiple blogs per community, and imports from Ghost and WordPress. Davidb invites feedback on how this tool compares to existing setups.

Community members share their current workflows and expectations. Blaisep notes that while they currently use Python frameworks like Sphinx and Nikola to push content to Discourse, the native solution would be more accessible for non-technical users. LotusJeff explains they use WordPress for static pages to leverage SEO capabilities for niche keywords, while Discourse handles dynamic forum content. LotusJeff suggests that for Discourse to replace this hybrid model, it would need expanded SEO tools, easier header/footer integration, and dynamic related-content blocks.

The discussion shifts toward community engagement and personal journaling. Mueu highlights a unique advantage: unlike standalone blogs that suffer from low engagement (“shouting into the void”), Discourse blogs come with a pre-built, relevant audience. Mueu posits that the “soft boundary” of a blog post, which asks nothing of the reader compared to a forum topic, might lower the barrier for lurkers to share experiences. Mcwumbly agrees, connecting the feature to broader discussions about supporting free-form journaling. This would allow members to share thoughts without worrying about consuming shared attention, a concept previously explored in the context of the Journal plugin.

Newkid, a self-described blogging novice, expresses excitement about the potential for helping a real estate community navigate property management. Finally, NateDhaliwal seeks technical clarification, asking if the blog will leverage Discourse’s existing “Published Pages” system or if it represents a new CMS architecture with custom layouts.

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.

12 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:

1 Like

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

Is this going to be something with Published Pages? Or a new system entirely? Are you looking at a full-featured CMS with custom layouts? Or Discourse-like-interface-with-topics-as-posts-but-not-really?