Running high-quality retrospectives is a team effort. Every member of the team collaborates to analyze incident data and converge on the best plan of action to prevent similar incidents from reoccurring.
Offering the best retrospective tool in the industry has been one of the pillars of our success at Blameless. Now, all the automated data collection and templated process standardization that Blameless Retrospectives provides can be seamlessly ported into Google Docs. Engineering organizations relying on Google Workspace, can now more efficiently produce, collaborate, and share high-impact Blameless retrospectives by automatically and securely exporting incident and retrospective data into Google Docs.
Automatic Data Export
Once incidents are resolved and the Google Drive integration is configured, Blameless automatically generates and exports incident and retrospective data into a newly created Google Doc. If, by policy, the incident type does not require a retrospective, no Google docs are created.
Effortless & Secure Access
A link to this Google Doc is automatically added to the retrospective details page within Blameless. Giving users quick and easy access and ensuring retrospective documentation doesn’t become a lost artifact in Google. Once in Google, users can add content and securely share access with a larger audience as needed, leveraging Google Docs' permission system (View, Comment, or Edit access modes).
Comprehensive Data Coverage & Easy to Navigate
The exported data comes pre-styled and properly converted to a Google Docs format. It includes incident and retrospective details like title, description, severity, incident type, timeline (including images captured from Slack or Microsoft Teams), incident tags, war room information (links to the Blameless incident, and corresponding Jira or ServiceNow tickets), the custom questionnaire, and the analysis template, which is customizable per incident type.
Refresh Data On-Demand
While the Google Doc is automatically created when the incident is resolved and fed with incident data collected up to that moment, users capturing more data post incident using the Blameless Retrospective questionnaire, tag management, and custom tab can update the linked Google Doc on-demand with the latest captured updates.
Secure Integration
Blameless only needs to know the specific Google Drive where you want Blameless to automatically create and store Google Docs. In this way, Blameless can operate within the folder system you assign without accessing other locations within drive that contain sensitive material.
Call to action
To get started creating and exporting retrospective data to Google Docs, ask your Blameless administrator to integrate your Blameless instance with a shared and secure Google Drive today!
Starting incidents shouldn’t be stressful, especially not for the incident’s creator and leaders (aka commanders). Recruiting more incident responders, assigning roles to delegate tasks, paging on-call engineers, and affirming the set of tasks that the incident team needs to complete are all key actions that need to get underway as quickly as possible.
We want these types of tasks to be obvious and intuitive. So, we’ve streamlined the Blameless welcome sequence in incident channels in Slack, to include default and dynamic buttons to trigger the following most commonly used Blameless actions at the start of an incident:
- Assign roles
- Invite Team Members
- View Tasks
- Trigger Alerts - only displayed when you have integrate Blameless with Pagerduty or Opsgenie
- View incident summary - only displayed when the incident summary is excluded from the welcome sequence
- More actions
Rather than relying solely on inputting /Blameless slash commands, you and your incident responders can rapidly initiate the incident investigation and get engaged as a cohesive and productive team, with just a simple mouse-click.
Moreover, instead of displaying the task checklist at the start of the incident, it is now accessible on-demand using the new View Tasks button.
These buttons can be triggered throughout the life of the incident and the output of these Blameless commands will be displayed at the bottom of your channel like any other new direct messages.
Optionally exclude the incident summary
Additionally, if your team would rather not display the incident summary right at the top of the incident channel, you can now ask your Blameless administrator to exclude it from any future incident channels, which is customizable as a new setting under the Invite and Notify Users section on a per incident type basis:


Get started now!
Previously created incidents will not be affected by this change. Only new incidents created starting as of today will benefit from this improved and streamlined welcome sequence.
New Feature Release
New Dynamic Bookmarks in Slack
At Blameless, one of our on-going missions is to maximize the productivity of your incident responders collaborating on incidents via Slack.
As additional areas of expertise become necessary, and new team members join the investigation, these new players need to quickly assess the urgency and importance of the issue at stake.
Now with NEW Dynamic Bookmarks, automatically added to each new incident channel, incident responders are provided fast access to vital incident information at any time during the investigation. Dynamic Bookmarks are a welcome complement to the incident summary, displayed at the top of the incident channel and on-demand using the `/blameless show incident` command.

From the very start of an incident, Blameless automatically adds the following key bookmarks to each incident channel in Slack:
- Severity: one of your custom severity labels
- Status: Investigating, Identified, Monitoring or Resolved
- Required tasks: 1/5 - dynamically updated as required tasks are completed per incident status (not across all statuses)
- Incident - Link to the incident detailed page on your Blameless account
- Retrospective - Link to the retrospective detailed page on your Blameless account
- Join Meeting - Link to the video conference
Required Tasks count is particularly powerful as it tracks the completion of steps necessary to progress the incident forward and can serve as a clear indicator of the team’s progress. This is an excellent reminder to task owners and incident leaders to complete the required tasks as soon as possible.
Immediate call to action
To benefit from this new feature enhancement in Slack, ask your Blameless administrator to re-authorize the Slack bot in Blameless at your earliest convenience.
Feature Releases
Identity management
SCIM provisioning: Blameless-Okta integration
Does your organization manage user access across multiple SaaS services? If so, then more than likely you're using a third-party authorization provider like Okta to centrally manage your users. Good news! We are happy to announce that you can now manage Blameless user groups directly from Okta via our new SCIM integration capabilities.
Key features include:
- User activation
- User deactivation
- Group pushing
- Group linking
- User to group bi-directional updating (when groups are linked)
At a high level, the process works as follows:
- Create your groups in Okta.
- Assign your application for authorization to Blameless for each group.
- Assign multiple users to a group within the groups tab in directory.
- Select and push these groups to Blameless.
- Visit your Blameless instance to see your groups and the users you selected.
- Apply permissions to the group within Blameless that reflects the needs of your group.
Please see Okta to learn how to integrate Okta and Blameless. Additionally, to get up-to-speed on creating groups and adding users in Okta, please see User Management with Okta.
Bug Fixes
Slack
Starting an incident fails from a private channel without the Blameless app
Issue:
When attempting to start a Blameless incident from a private channel without the Blameless app added to it, the /blameless start incident command allowed users to open and complete the Start incident modal, but the creation of the incident would fail after submitting the request.
Fix:
Now, the following warning message is displayed in the private channel when users attempt to run any /blameless command when the Blameless app has not been added to it:

Additionally, the following warning message is displayed in direct messages when users attempt to run any /blameless command when the Blameless bot user had not been invited to that direct message channel:

Incident types
Once the auto assigned role to a creator is set to a role, it can no longer be reset to none
Issue:
In Settings → Incident Types, after selecting a new default incident role for an incident creator, users were no longer able to change it back to None.
Fix:
Users can now reset the default incident role for the creator of an incident to None from any previously-saved value.
Jira
The links to the Blameless incident and the incident channel in Slack no longer appear in the Jira ticket Description field
Issue:
When the integration with Jira was enabled in your Blameless account, the Description field in auto-created Jira tickets (per Blameless incident) stopped including both a link to the Blameless incident and the incident channel in Slack.
Fix:
If the integration with Jira is enabled in your Blameless account, both links to the Blameless incident and the incident channel in Slack now appear in the Description field for each auto-created Jira ticket (when a Blameless incident is created).
Feature Releases
Slack
Self-serve API Keys for authenticating services with Blameless
Looking to authenticate services and machines to Blameless while building out automation in your incident management response workflow? We’ve been listening.
Previously, this feature was available by contacting one of our friendly CSMs. We are now happy to offer self-serve on demand API key generation from the convenience of the Blameless UI.
Here's how to do it:
- In the sidebar of the Blameless UI, select Identity Management, and then select the Key Management tab.

- Select + Generate New Key.

- In the Enter a Name for the Key field, enter a memorable name for the new API key and then select Create.

- A new API key will be generated. Select Copy to copy the key to your clipboard, and then save the key in a secure location. When done, select Close.
- Note: This key will not be displayed again.

- Your new key appears in the key list table. You can have up to 10 active keys at a time.

After you have generated a Blameless API Key (long-lived), you can then exchange it for an API Token (short-lived) via a POST request to an API endpoint.
Background on Authentication
Blameless provides OAuth flows to authorize access to the Blameless API. The client credential’s OAuth flow is used for machine-to-machine application and allows authentication of the application without involving an end user. Authentication tokens are passed using an auth header and are used when interacting with the API. All requests to the Blameless APIs require authentication.
Bug Fix
PagerDuty
The PagerDuty webhook fails to start an incident in Blameless when the PagerDuty user does not match a Blameless user
Issue:
In PagerDuty, configurable webhooks can be triggered upon the creation of an alert for a specific service, and then automatically create an incident in Blameless. If Blameless is unable to match the email address of either a) the creator of the PagerDuty alert or b) any on-call users defined in PagerDuty for the specific service, incidents are not started.
Fix:
Now, an incident will start when a PagerDuty webhook request is received, even if Blameless is unable to match the email address of a PagerDuty user (creator or on-call users) to a Blameless user. In this case, Blameless does not automatically set a Blameless user as the creator of the incident, but incidents are still started, as specifying the name of the creator of a Blameless incident is optional.
Feature Releases
Slack
Customizable start incident modal
Incident responders can now be optionally prompted to enter incident tags at the start of the incident creation process in Slack, effectively helping users capture and share context about the incident as soon as possible.
The list of tag categories (aka custom fields) displayed dynamically changes based on the incident type selected by users in the incident modal.
In the graphic below, the tag selection feature is available after starting a new incident by typing /blameless start incident in Slack.

After the incident is started, incident responders can still update and add more tags to the incident directly from within the incident channel. This is done by entering /blameless add tags in Slack.
To leverage this new capability, ask your Blameless administrator to do the following:
In Settings → Tag Management, configure selected tag categories to be visible as custom fields at the start of an incident in Slack. If no incident type has been selected, the tag category field is automatically visible to any selected incident type.
Incident Types
Enhanced incident type setting layout
The layout of the incident type setting page has been updated to provide a faster and more reliable user experience when creating new incident types. In addition, settings are now grouped together into expandable / collapsible sections and the order is aligned with an incident's workflow to facilitate ease of management.
The setting categories are as follows:
- Manage Incident Details
- Invite & Notify Team Members
- Trigger Alerts
- Set Affected Services
- Create Ticketing
- Assign Roles & Tasks
- Create Retrospective Reports
A few additional enhancements have been made available to improve your experience with incident types:
- To gain faster access to the configuration page for a selected incident type, you can directly click on the incident type from the list.
- In case you have a long list of incident types, we make it easier to find your incident type by searching and sorting your incident types by name.
- If you forgot to proactively click Save, you will be automatically asked if you want to save your changes before leaving any tab of the incident type configuration page.
Identity Management
Self-serve activate & deactivate users
As your team evolves, it is often necessary to activate and/or deactivate users ⏤ Blameless's new user status toggle feature now enables you to do this on demand.
Deactivating a user relinquishes their access to Blameless but does not delete the user profile, giving you the option to activate them again later.
To toggle user status:
- In the sidebar of the Blameless UI, select Identity Management, and then select the Users tab.
- Under the Status column heading, select the toggle switch to activate or deactivate a user as needed.
- In the confirmation dialog box, select Deactivate or Reactivate.

Bug Fixes
Slack
Type ahead search when adding tags to incidents in Slack is not working
Issue:
When adding tags via Slack, type ahead search (i.e., autosuggest) was no longer possible in Slack making it difficult to search for specific tags to be added to an incident.
Fix:
The type ahead search capability for tag categories in the Add Tags dialog box in Slack has now been restored for tag categories that have predefined tags, whether users select only one single tag or multiple tags.
Tasks would occasionally be duplicated when completed
Issue:
When completing a task in Slack, an identical message confirming the completion of the task would occasionally and randomly be displayed multiple times.
Fix:
This rare issue typically occurred when multiple tasks were rapidly being completed at nearly the same time. The processing of multiple tasks being completed nearly concurrently has been improved to prevent multiple appearances of the task confirmation message.
Jira
Jira incident ticket is not created when starting a new incident
Issue:
When the Reporter Jira system field was set as a required Jira field, the creation of incidents would fail. However, when the Reporter field is not required, Blameless correctly sets it to the default Jira user account used to integrate Blameless with Jira.
Fix:
If the Reporter Jira system field is set as a required Jira field, the creation of incidents now succeeds as Blameless does set its value automatically to the default Jira user account used to integrate Blameless with Jira, the same way it is set when the Reporter field is not required.
Feature Releases
Role-Based Access Control (RBAC)
New default groups make access assignment more intuitive
To make the assignment process more intuitive for new and existing instances, Blameless has introduced three new default incident groups:
- Observer: Users who participate in discussion and complete tasks (i.e., minimum viable permission set).
- Responder: Users who frequently participate and/or drive incident resolution.
- Lead: Users who are frequently incident commanders and have reliability management duties.
These groups reflect the most common types of incident response team roles, with each group possessing its own unique permission set.
Use Case
An enterprise wants to enable its teams to use Blameless, but has a Zero-Trust Policy. By specifying Observer as the default incident group, the organization ensures that the hundreds of users it is adding into Blameless are automatically routed and assigned the minimum viable set of permissions. If changes need to be made, the company can select users and modify their group placement at any time.
Additionally, here is a group-role matrix for each of the new groups:

Slack
Unresolved Incidents now viewable from Blameless Slack App Home Tab
Incident responders using Blameless in Slack can now leverage the new Home tab enabled on their Blameless app to gain access to the following enhancements:
- Brand new sorted view of your top unresolved active incidents.
- Shortcut buttons designed to facilitate quick access to useful tools and features, such as the web app, commands used in Slack, and a getting started tutorial.

While on the Home tab, a list of your top unresolved incidents appears with a link to each incident's corresponding dedicated Slack channel. In addition, you can sort your top unresolved incidents by severity, creation date (oldest or newest first), status, or in alphabetical order by incident title.
These features enable users to quickly identify the most pressing incidents and then collaborate with colleagues to investigate and resolve.
We made sure that the list of unresolved incidents is refreshed from your Blameless account each time you change the sorting option or access the Home tab.
To benefit from these new enhancements, make sure to add the Blameless app to your app portfolio in Slack (Go to the bottom left and select + Add app). To navigate to the Home tab after the Blameless app has been added, browse to the Apps section and select blamelessbot.

Bug Fixes
Slack
Latency: Ticket and Zoom links not displaying as expected
Issue:
Occasionally, after starting an incident in Slack, the links to the Jira ticket and/or the Zoom video conferencing could take up to a few hours before being provided in the pinned incident summary at the top of the incident channel. Additionally, it would incorrectly indicate that the integration with Jira or Zoom was disabled despite being actually enabled and healthy.
Fix:
Now, after starting an incident in the Blameless app in Slack, Blameless will indicate that the links to resources on external ticketing or conference systems are still being created (e.g., Creating ticket...) and will update the links to those resources as soon as it receives confirmation from them (e.g., Jira, Zoom, Slack, etc.).
Severity levels with no label could be selected and prevent an incident from being created
Issue:
If one of the default severity levels had no label provided, this blank severity started to show up as an option in the severity dropdown when starting an incident in Slack, and when selected it would prevent the incident from starting.
Fix:
Severity levels with no labels no longer show as options in the severity dropdown when starting an incident in Slack.
Multi-line text captured in Slack are not rendered properly in the incident timeline
Issue:
In Slack, when users were adding long multi-line formatted text as a message in a Blameless incident channel in Slack and then capturing the message as an highlight to be saved in the incident timeline, the entire text would be rendered as a single line in the incident timeline in the Blameless web UI, ignoring the end of lines.
Fix:
Messages formatted with multiple lines captured as highlights in Slack are now correctly rendered in the incident timeline in the Blameless web UI.
Feature Releases
Role-Based Access Control (RBAC)
Access control extended to Blameless for Slack
As a result of newly-introduced RBAC roles under IAM, Blameless has now extended access control from the platform into Slack. These enhancements empower teams to consistently align Blameless’s platform and Slack incidents with least privilege policies.
Key features include:
- Users can assign new incident roles that map to controls in both the Blameless platform and Slack.
- Three distinct roles are created automatically for each custom incident type, enabling users to effectively isolate access permissions by incident type (Incident Reader, Incident Writer, and Incident Admin).
- The new Incident Reader role allows users to do more within incidents (e.g., such as completing tasks and follow-up actions).
- Permissions are enforced via the Blameless web UI and Blameless APIs.
- Role to Slack Command mapping:
- Incident Reader:
- View Your Tasks
- View All Tasks
- Complete Your Tasks
- Show Tag(s)
- Show On-Call
- Show Escalation Policy
- Help - Commands (show)
- All Emoji usage in channel
- Incident Writer:
- All Reader items, plus:
- Create Incident
- Assign Incident Role
- Resolve Incident
- Set Incident Status
- Set Incident Severity
- Set Incident Title
- Set Incident Description
- Add Task
- Assign Task
- Create Follow Up Action
- Create Swimlane
- Add Tag(s)
- Remove Tag
- Trigger Alert to On-Call (PagerDuty)
- Includes Invite to On-Call
- Incident Admin:
- All Reader and Writer items, plus:
- Delete Incident
Slack
New customizable Slack incident channel naming option
Blameless has introduced additional flexibility to customize incident channel names in Slack via custom text (e.g., team name) and dynamic insertion of Blameless incident data into the channel name.
This option provides incident responders with more meaningful and descriptive names for incident channels in Slack. This enables responders to find urgent incidents more efficiently by aligning incidents with existing naming conventions.
Configurable as a new option for the incident channel naming scheme setting under each incident type, you can now specify the syntax of your incident channel names in Slack through a combination of custom text and variables. The variables represent common incident data and can be specified in any order.
They include the following:
- Incident creation date
- Incident title
- Incident severity
- Incident status
- Incident ID
Additionally, as the incident progresses or if its title changes, Blameless automatically updates the incident channel name to reflect the latest state of the selected variables (e.g., status changing from investigating to monitoring).
Bug Fixes
Slack
Auto invite for multiple Slack users fails if any invitation to a user fails
Issue:
When auto-inviting multiple users into an incident channel in Slack (Settings → Incident Types → Manage → Invited Slack Groups or Users), the request could fail for all users if at least one invitee was not recognized as a user in your Slack workspace.
Fix:
Blameless detects and ignores auto-invited Slack users that do not exist (or no longer exist) in your Slack workspace. All other Slack users from the list of auto-invited Slack users that do exist in your Slack workspace will be invited to join the incident channel in Slack.
Incident Types
Unable to save updated Jira settings
Issue:
After updating Jira settings for an incident type (Settings → Incident Types → Manage → JIRA Settings), users were unable to save their updates. Additionally, it would delete all the tasks from the checklist configuration under the same incident type setting.
Fix:
Updates made to Jira settings for an incident type can now be properly saved and do not delete the tasks from the checklist.
Incidents
Events are duplicated when entered manually via the incident detail page
Issue:
When manually entering events to the incident timeline via the incident detail page in the Blameless web UI, the event would be duplicated in the incident timeline. Users could still manually delete one of the two events from the incident timeline.
Fix:
Events added manually via the incident detail page are no longer duplicated, whether captured as text or via image upload.
Feature Release
ALERTING (OPSGENIE)
Enhanced Opsgenie Integration
Blameless is providing a more comprehensive integration with Opsgenie for alert management. This makes it easier to recruit any teams defined in Opsgenie into a Blameless incident:
- Integrates with all services and teams defined in Opsgenie (service catalog and team directory)
- The user can manually trigger Opsgenie alerts by selecting Opsgenie services or teams from within the Blameless incident channel in Slack (`/blameless trigger alert`) and Microsoft Teams (On-Call > Trigger Alert)
- The user can automate Opsgenie alerts when starting incidents by preselecting services per incident type
- The user can clear alert confirmation responses inside the incident channel (Slack/Teams) displaying the name of the notified on-call responders
- Track all triggered alerts as an event in the incident timeline, with link to the alert, team or service in Opsgenie, providing clear context about what happened when, for the retrospective report and downstream analysis
SLACK
Self guided Tutorial
The Blameless Slack self guided tutorial allows new users the chance to "kick the tires".
These users include incident responders, site reliability engineers, those who are evaluating Blameless for the first time through our self-sign up trial program, and also new users within an organization already using Blameless.
The tutorial allows them to learn in a few guided steps how simple it is to start and run an incident using Blameless.
The Self-guided Slack tutorial gives the user instructions in how to:
- Choose the Severity, based on a suggested level
- Enter a title--something that makes sense in their environment
- Provide a description (optional)
When you launch the `blamelessbot` app, you will see an invitation to try out the tutorial. Simply click on the "Start Tutorial" button to begin.
The tutorial creates a sample channel, then walks the user through a series of five steps to:
- Invite team members
- Assign roles to the team
- Update the Incident status
- Report the incident to the team and shareholders
And that's it in just a few minutes; you have learned how to start a Blameless incident in Slack, invite team members, set the incident status, and communicate details to the team and stakeholders. Once complete, the tutorial invites you to learn more capabilities Blameless has to offer.

Collaborate on Retrospectives using Google Docs

Take action as soon as you join the Incident in Slack

New Dynamic Bookmarks in Slack

SCIM provisioning: Blameless-Okta integration

Self-serve API Keys for authenticating services with Blameless

Slack - Customizable start incident modal

Role-Based Access Control
What’s a Rich Text element?
What’s a Rich Text element?The rich text element allows you to create and format headings, paragraphs, blockquotes, images, and video all in one place instead of having to add and format them individually. Just double-click and easily create content.
The rich text element allows you to create and format headings, paragraphs, blockquotes, images, and video all in one place instead of having to add and format them individually. Just double-click and easily create content.Static and dynamic content editing
Static and dynamic content editingA rich text element can be used with static or dynamic content. For static content, just drop it into any page and begin editing. For dynamic content, add a rich text field to any collection and then connect a rich text element to that field in the settings panel. Voila!
A rich text element can be used with static or dynamic content. For static content, just drop it into any page and begin editing. For dynamic content, add a rich text field to any collection and then connect a rich text element to that field in the settings panel. Voila!How to customize formatting for each rich text
How to customize formatting for each rich textHeadings, paragraphs, blockquotes, figures, images, and figure captions can all be styled after a class is added to the rich text element using the "When inside of" nested selector system.
Headings, paragraphs, blockquotes, figures, images, and figure captions can all be styled after a class is added to the rich text element using the "When inside of" nested selector system.What’s a Rich Text element?
What’s a Rich Text element?The rich text element allows you to create and format headings, paragraphs, blockquotes, images, and video all in one place instead of having to add and format them individually. Just double-click and easily create content.
The rich text element allows you to create and format headings, paragraphs, blockquotes, images, and video all in one place instead of having to add and format them individually. Just double-click and easily create content.Static and dynamic content editing
Static and dynamic content editingA rich text element can be used with static or dynamic content. For static content, just drop it into any page and begin editing. For dynamic content, add a rich text field to any collection and then connect a rich text element to that field in the settings panel. Voila!
A rich text element can be used with static or dynamic content. For static content, just drop it into any page and begin editing. For dynamic content, add a rich text field to any collection and then connect a rich text element to that field in the settings panel. Voila!How to customize formatting for each rich text
How to customize formatting for each rich textHeadings, paragraphs, blockquotes, figures, images, and figure captions can all be styled after a class is added to the rich text element using the "When inside of" nested selector system.
Headings, paragraphs, blockquotes, figures, images, and figure captions can all be styled after a class is added to the rich text element using the "When inside of" nested selector system.What’s a Rich Text element?
What’s a Rich Text element?The rich text element allows you to create and format headings, paragraphs, blockquotes, images, and video all in one place instead of having to add and format them individually. Just double-click and easily create content.
The rich text element allows you to create and format headings, paragraphs, blockquotes, images, and video all in one place instead of having to add and format them individually. Just double-click and easily create content.Static and dynamic content editing
Static and dynamic content editingA rich text element can be used with static or dynamic content. For static content, just drop it into any page and begin editing. For dynamic content, add a rich text field to any collection and then connect a rich text element to that field in the settings panel. Voila!
A rich text element can be used with static or dynamic content. For static content, just drop it into any page and begin editing. For dynamic content, add a rich text field to any collection and then connect a rich text element to that field in the settings panel. Voila!How to customize formatting for each rich text
How to customize formatting for each rich textHeadings, paragraphs, blockquotes, figures, images, and figure captions can all be styled after a class is added to the rich text element using the "When inside of" nested selector system.
Headings, paragraphs, blockquotes, figures, images, and figure captions can all be styled after a class is added to the rich text element using the "When inside of" nested selector system.What’s a Rich Text element?
What’s a Rich Text element?The rich text element allows you to create and format headings, paragraphs, blockquotes, images, and video all in one place instead of having to add and format them individually. Just double-click and easily create content.
The rich text element allows you to create and format headings, paragraphs, blockquotes, images, and video all in one place instead of having to add and format them individually. Just double-click and easily create content.Static and dynamic content editing
Static and dynamic content editingA rich text element can be used with static or dynamic content. For static content, just drop it into any page and begin editing. For dynamic content, add a rich text field to any collection and then connect a rich text element to that field in the settings panel. Voila!
A rich text element can be used with static or dynamic content. For static content, just drop it into any page and begin editing. For dynamic content, add a rich text field to any collection and then connect a rich text element to that field in the settings panel. Voila!How to customize formatting for each rich text
How to customize formatting for each rich textHeadings, paragraphs, blockquotes, figures, images, and figure captions can all be styled after a class is added to the rich text element using the "When inside of" nested selector system.
Headings, paragraphs, blockquotes, figures, images, and figure captions can all be styled after a class is added to the rich text element using the "When inside of" nested selector system.What’s a Rich Text element?
What’s a Rich Text element?The rich text element allows you to create and format headings, paragraphs, blockquotes, images, and video all in one place instead of having to add and format them individually. Just double-click and easily create content.
The rich text element allows you to create and format headings, paragraphs, blockquotes, images, and video all in one place instead of having to add and format them individually. Just double-click and easily create content.Static and dynamic content editing
Static and dynamic content editingA rich text element can be used with static or dynamic content. For static content, just drop it into any page and begin editing. For dynamic content, add a rich text field to any collection and then connect a rich text element to that field in the settings panel. Voila!
A rich text element can be used with static or dynamic content. For static content, just drop it into any page and begin editing. For dynamic content, add a rich text field to any collection and then connect a rich text element to that field in the settings panel. Voila!How to customize formatting for each rich text
How to customize formatting for each rich textHeadings, paragraphs, blockquotes, figures, images, and figure captions can all be styled after a class is added to the rich text element using the "When inside of" nested selector system.
Headings, paragraphs, blockquotes, figures, images, and figure captions can all be styled after a class is added to the rich text element using the "When inside of" nested selector system.What’s a Rich Text element?
What’s a Rich Text element?The rich text element allows you to create and format headings, paragraphs, blockquotes, images, and video all in one place instead of having to add and format them individually. Just double-click and easily create content.
The rich text element allows you to create and format headings, paragraphs, blockquotes, images, and video all in one place instead of having to add and format them individually. Just double-click and easily create content.Static and dynamic content editing
Static and dynamic content editingA rich text element can be used with static or dynamic content. For static content, just drop it into any page and begin editing. For dynamic content, add a rich text field to any collection and then connect a rich text element to that field in the settings panel. Voila!
A rich text element can be used with static or dynamic content. For static content, just drop it into any page and begin editing. For dynamic content, add a rich text field to any collection and then connect a rich text element to that field in the settings panel. Voila!How to customize formatting for each rich text
How to customize formatting for each rich textHeadings, paragraphs, blockquotes, figures, images, and figure captions can all be styled after a class is added to the rich text element using the "When inside of" nested selector system.
Headings, paragraphs, blockquotes, figures, images, and figure captions can all be styled after a class is added to the rich text element using the "When inside of" nested selector system.What’s a Rich Text element?
What’s a Rich Text element?The rich text element allows you to create and format headings, paragraphs, blockquotes, images, and video all in one place instead of having to add and format them individually. Just double-click and easily create content.
The rich text element allows you to create and format headings, paragraphs, blockquotes, images, and video all in one place instead of having to add and format them individually. Just double-click and easily create content.Static and dynamic content editing
Static and dynamic content editingA rich text element can be used with static or dynamic content. For static content, just drop it into any page and begin editing. For dynamic content, add a rich text field to any collection and then connect a rich text element to that field in the settings panel. Voila!
A rich text element can be used with static or dynamic content. For static content, just drop it into any page and begin editing. For dynamic content, add a rich text field to any collection and then connect a rich text element to that field in the settings panel. Voila!How to customize formatting for each rich text
How to customize formatting for each rich textHeadings, paragraphs, blockquotes, figures, images, and figure captions can all be styled after a class is added to the rich text element using the "When inside of" nested selector system.
Headings, paragraphs, blockquotes, figures, images, and figure captions can all be styled after a class is added to the rich text element using the "When inside of" nested selector system.What’s a Rich Text element?
What’s a Rich Text element?The rich text element allows you to create and format headings, paragraphs, blockquotes, images, and video all in one place instead of having to add and format them individually. Just double-click and easily create content.
The rich text element allows you to create and format headings, paragraphs, blockquotes, images, and video all in one place instead of having to add and format them individually. Just double-click and easily create content.Static and dynamic content editing
Static and dynamic content editingA rich text element can be used with static or dynamic content. For static content, just drop it into any page and begin editing. For dynamic content, add a rich text field to any collection and then connect a rich text element to that field in the settings panel. Voila!
A rich text element can be used with static or dynamic content. For static content, just drop it into any page and begin editing. For dynamic content, add a rich text field to any collection and then connect a rich text element to that field in the settings panel. Voila!How to customize formatting for each rich text
How to customize formatting for each rich textHeadings, paragraphs, blockquotes, figures, images, and figure captions can all be styled after a class is added to the rich text element using the "When inside of" nested selector system.
Headings, paragraphs, blockquotes, figures, images, and figure captions can all be styled after a class is added to the rich text element using the "When inside of" nested selector system.What’s a Rich Text element?
What’s a Rich Text element?The rich text element allows you to create and format headings, paragraphs, blockquotes, images, and video all in one place instead of having to add and format them individually. Just double-click and easily create content.
The rich text element allows you to create and format headings, paragraphs, blockquotes, images, and video all in one place instead of having to add and format them individually. Just double-click and easily create content.Static and dynamic content editing
Static and dynamic content editingA rich text element can be used with static or dynamic content. For static content, just drop it into any page and begin editing. For dynamic content, add a rich text field to any collection and then connect a rich text element to that field in the settings panel. Voila!
A rich text element can be used with static or dynamic content. For static content, just drop it into any page and begin editing. For dynamic content, add a rich text field to any collection and then connect a rich text element to that field in the settings panel. Voila!How to customize formatting for each rich text
How to customize formatting for each rich textHeadings, paragraphs, blockquotes, figures, images, and figure captions can all be styled after a class is added to the rich text element using the "When inside of" nested selector system.
Headings, paragraphs, blockquotes, figures, images, and figure captions can all be styled after a class is added to the rich text element using the "When inside of" nested selector system.