Having a variety of content for community members is a great way to engage and share information to draw your members to the community. Blogs are where you can create and publish written content for your community to consume and embed videos, gifs, etc. in addition to text and tables.
New! Gradual has just unveiled a new blog and resource editor that allows for more customization and better handling of PDFs, images, videos and more.
New icon styles and options
Better handling of alignment and resizing for images, videos, and PDFs
Captions and link generation for images, videos, and PDFs elements
Local PDF upload support
Ability to apply code formatting to code blocks
This updated blog & resource editor will be available to all communities and dashboards soon, but will be rolled out in phases.
Customization of the 'Blog' name
Some communities don't use the name 'Blog' for their written content and prefer terms like 'Article' or 'News'. Gradual now allows you to customize what written content is referred to in the main menu and throughout your community.
Sign into the dashboard and navigate to the Content menu, and to Blogs.
In the upper right hand side select the button that reads 'Name'.
You'll be led to the Blog Name Customization page where you will can select 'Edit' to enter the name you'd like to use. Click 'Save' and the name will be updated immediately across the dashboard and front end of your community.
Names can be up to 10 characters and should be entered in the singular as the system will automatically pluralize it when needed.
Blog Editor Versions
Legacy Blog Editor
The majority of the community dashboards use the legacy or default blog editor that allows for rich text content, images, video embeds and more. The steps described below to build and edit a blog are using the legacy blog editor.
This blog editor looks like this:
A new blog editor was released in Q2 of 2025 that allows for more customization and better handling of PDFs, images, videos, and more. This updated blog editor will be available to all communities and dashboards soon, but will be rolled out in phases.
Learn more about this new blog editor here.
The new blog editor includes new icons and features and looks like this:
Creating a Blog (with the Legacy Blog & Resource Editor)
Here is how to create a blog post in the legacy blog editor:
Sign into your dashboard.
Select the Content tab from the main menu, and then Blogs from within that menu.
Select the +Create New Blog button in the upper right.
Fill in the necessary information like Title, URL Slug and Sub Title. The Sub Title populates under the Title on the Resource page and should be a one-liner description.
The Sub Title and Summary can be the same text.
The Summary populates under the Title on the Content page and while not necessary, provides another opportunity for a one-liner description.
The Sub Title populated under the title on the content detail page and is necessary.
Fill the Content description with your content. You can embed links, tables, images and iframes in the content block.
Upload a Cover Image and select, or add a category. If you would like to include tags to the post, and gate or limit access by spaces, make those selections.
Preview and publish. Before a blog is published, you can preview the post using the preview link, found in the upper right hand side of the Blog detail page in the dashboard.
Note: This link is a special tokenized link that will expire after 24 hours to prevent blogs from being viewed before they’re published.
💡 Pro Tip: You can also copy and paste blog content from a markdown editor or Google docs. Just be sure to double-check as some formatting doesn’t always copy over when copying and pasting.
Here are links to more helpful articles around blogs:
The legacy blog editor does not support uploading downloadable PDFs, resizing images or videos, or utilizing the table feature for formatting. These are available in the new blog editor.
Resources
If your blog has organized content that would be better suited with a table of contents for easier navigation, build a Resource instead!