diff --git a/src/content/blog/technical/how-teams-keep-docs-up-to-date-with-promptless.mdx b/src/content/blog/technical/how-teams-keep-docs-up-to-date-with-promptless.mdx new file mode 100644 index 00000000..76f1d740 --- /dev/null +++ b/src/content/blog/technical/how-teams-keep-docs-up-to-date-with-promptless.mdx @@ -0,0 +1,67 @@ +--- +title: What It Looks Like When Your Docs Keep Up With Your Product +subtitle: Published March 2026 +description: >- + Three real workflows from teams using Promptless that show what changes when + your tooling handles detection, context gathering, and the first draft. +date: '2026-03-26T00:00:00.000Z' +section: Technical +hidden: false +--- +import BlogRequestDemo from '@components/site/BlogRequestDemo.astro'; + +What does it look like when your docs keep up with your product, without you +spending half your day hunting for what changed? + +Most docs tools solve distribution. They give you a nice site, interactive API +explorers, maybe a search bar that works. That's real value, but it assumes the +hard part is presentation. The actual hard part is knowing what needs to be +written and keeping it honest as the product moves underneath you. That is the +work that eats your week, and that is the problem we built Promptless to solve. + +We have been working with teams like Helm, Vitess, Basis, and Vellum over the +past few months, and there are three workflows that keep surprising me with how +much they change the shape of a writer's day. + +The first is just eliminating the classic "I didn't know that changed" problem. +Many of our customers love the awareness Promptless gives them of what changed, +and how it changed. Promptless watches every PR across their repos, and when an +engineer changes how auth works or deprecates a parameter, the tech writer does +not find out from a support ticket three weeks later. A writer gets a drafted +update with citations back to the PR, the relevant Slack discussion, the +engineer's own description of the change. Review it, ask Promptless for changes, +manually edit it, published. The feedback loop between code change and +doc update collapses to hours. + +The second is something Basis is doing that (completely unexpected to me)! They +dump their customer call transcripts into a Git repository, and Promptless +monitors that repo and maintains internal documentation around what all their +customers are doing, what they are asking about, what keeps coming up, how the +product is actually being used out in the field. An internal knowledge base that +builds itself from conversations, and because it lives in their own repo in a +format they control, they are building all kinds of internal agents to make use +of it. They would get way less value from throwing all that data +into a third party system and hope third party agents can do something useful +with it. + +The third is about scale. Helm had community translations of their docs across +ten languages, but most were incomplete or out of date, and would be a big ask +for their writers to bring them all current by hand. So two writers spent about +five iterations over eight hours "teaching" Promptless how to do the work (its +just skills, which if you read this blog you know is just another kind of docs). +They started with a style guide which was not good enough. But they got feedback +in about 35 minutes, so they iterated and fixed the problems. They added a +glossary, then more language-specific instructions for how to handle existing +translations, keep what was still good, update what had drifted, and fill in the +gaps. By the end of that process the writers had 10 playbooks that Promptless +could execute for 10 languages over the 110 pages of Helm V3 docs. So in one +day, 10 PRs opened. Then over the next three weeks the community reviewed and +merged them one by one. Pretty clever use case we didn't build for. + +This is what's possible when your writers have a power tool that rewards +the craft, not just a platform that makes things look nice. + +If you want to see what this looks like for your team, book a quick 15-min demo +with one of our engineers. 30-day free trials! + + \ No newline at end of file diff --git a/src/content/changelog/changelogs/march-2026.mdx b/src/content/changelog/changelogs/march-2026.mdx new file mode 100644 index 00000000..d806f644 --- /dev/null +++ b/src/content/changelog/changelogs/march-2026.mdx @@ -0,0 +1,40 @@ +--- +title: March 2026 +subtitle: Version branch targeting, AGENTS.md support, improved screenshots, and smarter clarification prompts. +date: '2026-03-01T00:00:00.000Z' +hidden: false +--- +import Frame from '@components/fern/Frame.astro'; + +**New Features:** + +* **Version Branch Targeting:** Suggestions now target the correct base branch automatically. When a trigger comes from a non-default branch, Promptless creates the suggestion against that branch—useful for teams maintaining versioned documentation. A base branch chip appears on suggestion cards so you can see at a glance which branch a suggestion targets. + +* **AGENTS.md Support:** Promptless now honors `AGENTS.md` files in your docs repository, letting you provide persistent guidance to the agent about your project's conventions, terminology, and documentation standards. + +* **Clarification Prompts:** When you send a direct request via Slack or the Web UI, Promptless now asks clarifying questions before diving in—reducing back-and-forth and improving suggestion quality. + +**Improvements:** + +* **Better Screenshot Capture:** Screenshots are now captured more reliably and at higher quality. Large screenshot canvases also fit properly within the editor dialog instead of overflowing. + +* **Improved Voice Matching:** Promptless now does a better job matching your team's writing style, tone, and conventions when generating documentation suggestions. + +* **Suggestion Branch Syncing:** Open suggestion branches now stay synced with their effective base branch, so suggestions always build on the latest documentation state. + +* **Sticky File Header in Diff Review:** The file header now sticks to the top of the viewport while scrolling through diffs, so you always know which file you're reviewing. + +* **Dynamic Browser Tab Titles:** All dashboard pages now display descriptive tab titles, making it easier to navigate with multiple tabs open. + +* **Full PR Links in Citations:** Citations now link directly to the source pull request, making it easier to trace a suggestion back to the change that triggered it. + +* **Improved Slack Notifications:** Slack messages now render with consistent formatting—links, bold text, and code blocks display properly across all notification types. + +**Bug Fixes:** + +* **Docs PR Status:** Fixed the trigger events page showing stale PR status instead of the current state. +* **Large PR Handling:** Fixed an issue where PRs with more than 300 changed files could silently drop changes during processing. +* **Onboarding Doc Detection:** Fixed onboarding to correctly detect `.rst` and `.adoc` files in your repository. +* **Stale Image Filtering:** Fixed stale images appearing in the "Added images" section of suggestion diffs. +* **Stale Suggestion Pruning:** Suggestions with open documentation PRs are no longer incorrectly archived by the stale-suggestion cleanup. +* **Default Branch Rename:** Fixed suggestion sync breaking when a repository's default branch is renamed.