Blogging for your community

AI-generated summary

Davidb announced that Discourse is building a native blogging feature to allow communities to publish articles directly within the platform, eliminating the need for a separate blogging service. Articles are created using the standard Discourse composer and can be published to /blog or a custom domain. Key planned features include community-powered comments where every article has an associated topic, an editorial workflow with role-based permissions (contributor, editor, publisher), customizable themes, support for multiple blogs under one community, and import tools for Ghost and WordPress Davidb.

Blaisep responded positively, noting that while they currently publish to Discourse from Python frameworks like Sphinx and Nikola, the new native integration would be far more convenient for non-technical users blaisep.

LotusJeff shared their experience running WordPress as their main site for SEO purposes, with Discourse on a subdomain. They explained that WordPress allows for rich SEO capabilities on static pages, which drive significant traffic and rank highly, while Discourse handles dynamic forum discussions. They suggested that for Discourse’s blog feature to replace their current setup, it would need improved SEO options, easier integration into site headers/footers, and dynamic content blocks to link blog posts to relevant forum discussions LotusJeff.

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.

5 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
2 Likes