- From your activity (Studio). Turn pull requests, commits, releases and Linear issues into a narrative post about what you shipped.
- From a prompt (GEO Write). Write an article that targets a prompt people ask AI answer engines, with your brand identity, sitemap and competitor data as context for the writer.
blog_post that you review and publish from Content.
Content types
Posts in Notra have one of these content types:
Every post has a status of
draft or published.
Blog posts can also carry a subtype: guide, comparison, listicle, how-to, faq or alternatives. Posts written through GEO Write get one of these, while posts generated from repository activity do not.
How blog posts differ from changelogs
Both count against the long-form posts quota of your plan, as described in Billing and plans.
Writing from repository activity
1
Open the create dialog
Switch the sidebar to Studio, open Content and click New post.
2
Formats
Select Blog post, which you can combine with other formats in the same run. Pick the lookback window and toggle Pull Requests, Commits and Releases.
3
Activity
Choose repositories and Linear integrations, then deselect anything you do not want in the post, because a selection focused on one feature produces a better article.
4
Identity
Choose the brand identity that should write the post, and Notra creates a collection and generates the draft.
Automating blog posts
Schedules and event triggers can also generate blog posts, and a release trigger is the most common setup:published instead of draft. See Event-based automation and Scheduled automation.
Writing from a prompt (GEO Write)
When you want an article that improves how AI answer engines describe your brand, use Write in the GEO sidebar.1
Prompt
Enter the prompt you want the article to answer, or start from a content gap.
2
Format
Choose Guide (a long article that answers the prompt directly), Listicle (a numbered list buyers can scan and cite) or Comparison (compares your brand with its alternatives).
3
Context
Optionally attach a brand identity, competitors to position against and a sitemap so the writer can link to your existing pages.
4
Brief and draft
Notra first writes a content brief and then drafts the article from it. The finished post opens in the editor with the brief available alongside it.
Editing with the content agent
Open any post and use the content agent in the right-hand panel. Select a passage to give it context, then ask for changes: Expand on technical details- “Explain the implementation in more detail”
- “Add a code example for this feature”
- “Make this section more accessible for non-technical readers”
- “Rewrite this in a more conversational tone”
- “Add a section about migration steps”
- “Add a conclusion with next steps”
Publishing
Clicking Publish sets the post status topublished, but Notra does not push the post to a site by itself. Published posts reach your site through:
- Framer. The Notra plugin imports posts into a Framer site, as described in Framer.
- Manual. Copy the Markdown from the editor.
draft.
Best practices
Focus on one main topic
Give each blog post one clear narrative by deselecting unrelated activity in the Activity step instead of asking the writer to cover everything. Good: “How We Reduced API Response Time by 60%“Poor: “March 2026 Product Updates”
Include context and motivation
Good posts explain the problem, the solution, the impact for users and what you learned. The writer can only include what your PRs, commits, issues and brand identity contain, so descriptive PR bodies matter.Keep your brand identity current
The writer reads your company description, tone, target audience, custom instructions and reference posts, so keep them up to date in Brand voice.Review before publishing
Check technical accuracy, add screenshots or diagrams on your site and get a teammate to read it, since posts stay indraft until you publish them.