Meta tags:
description=Learn what release notes are, their structure, and how to write effective entries that inform users about product updates, features, and changes.;

Headings (most frequently used words):

release, note, example, entry, notes, writing, change, documentation, index, what, is, structure, of, page, individual, entries, template, guidelines, for, tone, self, audit, checklist, title, date, sections, by, type, new, feature, bug, fix, breaking, document360, top, features, support, contact, us,

Text of the page (most frequently used words):
the (55), release (33), and (25), for (20), what (16), support (15), this (15), article (14), one (14), with (14), notes (13), that (13), guide (12), not (12), note (11), sentence (11), #documentation (10), use (10), features (9), entry (9), breaking (9), link (9), than (8), tense (8), change (8), feature (8), 2026 (8), document360 (7), articles (7), was (7), internal (7), changes (7), entries (7), date (7), format (7), api (6), specific (6), warning (6), more (6), new (6), page (6), feedback (5), knowledge (5), content (5), are (5), fixed (5), from (5), impact (5), docs (5), your (5), base (4), resources (4), help (4), guidelines (4), audience (4), rather (4), tone (4), does (4), improved (4), callout (4), icon (4), changed (4), why (4), headings (4), month (4), version (4), before (4), section (4), improvements (4), how (4), name (4), bug (4), example (4), about (3), drive (3), analytics (3), integrations (3), site (3), private (3), customers (3), style (3), related (3), past (3), present (3), describing (3), every (3), vague (3), performance (3), text (3), alone (3), state (3), matters (3), sections (3), correctly (3), year (3), these (3), writing (3), different (3), now (3), you (3), export (3), product (3), standard (3), readers (3), search (3), customer (3), resolved (3), deprecated (3), type (3), tokens (3), update (3), images (3), were (3), eddy (3), may (3), dates (3), see (3), single (3), structure (3), ask (3), open (3), custom (3), policy (2), trust (2), our (2), com (2), contact (2), workflow (2), extensions (2), hosting (2), migration (2), request (2), types (2), templates (2), reference (2), formatting (2), next (2), troubleshooting (2), success (2), gtm (2), has (2), been (2), covers (2), factual (2), concise (2), promotional (2), language (2), used (2), itself (2), only (2), resulting (2), capability (2), terminology (2), exact (2), names (2), number (2), all (2), label (2), relevant (2), empty (2), unambiguous (2), prose (2), localized (2), title (2), follow (2), self (2), have (2), announcements (2), emails (2), serve (2), but (2), written (2), acceptable (2), when (2), editor (2), which (2), general (2), list (2), their (2), never (2), under (2), prominently (2), should (2), consistent (2), focus (2), benefit (2), reduced (2), time (2), 000 (2), released (2), fixes (2), action (2), deprecations (2), being (2), timeline (2), always (2), any (2), regenerate (2), missing (2), zip (2), conceptual (2), covering (2), each (2), numbers (2), facing (2), teams (2), complete (2), publish (2), claude (2), chatgpt (2), view (2), markdown (2), copy (2), llms (2), ctrl (2), glossary (2), october (2), review (2), file (2), index (2), soc2, cookie, privacy, center, terms, careers, culture, team, 3000, rating, status, seo, ticket, deflector, platform, assistant, portal, top, enterprise, readiness, security, demo, pricing, strategy, foundations, creating, previous, yes, helpful, involves, separate, considered, assuming, both, free, consistently, match, concrete, scope, claim, like, flagged, proper, where, actual, included, applicable, publishing, check, against, questions, audit, checklist, clear, informative, slightly, direct, other, they, much, marketing, paragraph, save, blog, posts, tighter, neutral, register, intentionally, warmer, permitted, effective, notification, transactional, announcement, purposes, shouldn, same, voice, describe, occurred, saving, added, csv, imports, also, specifically, framed, can, directly, pdf, current, narrating, event, variation, inconsistency, rule, verbs, mood, own, bury, flag, significant, improvement, make, just, announced, refer, implementation, details, write, perspective, avoid, load, bases, yyyy, symptom, description, changing, required, instead, template, callouts, alongside, symbol, meet, accessibility, requirement, conveyed, color, generated, june, will, stop, working, september, must, token, contained, uploaded, via, those, exported, files, fix, automatically, categorizes, topic, making, easier, identify, patterns, across, large, volumes, learn, categorization, explaining, reader, stating, clearly, pattern, individual, omit, include, require, highlight, phased, out, defects, symptoms, enhancements, existing, functionality, did, previously, exist, group, deployed, using, specified, guidance, units, localization, exactly, kind, translatable, needs, reformat, per, locale, carry, english, through, typically, following, ahead, distinct, artifact, often, rollout, timing, talking, points, simply, shorter, technical, public, knowing, principle, behind, distinction, good, honest, various, erode, latency, projects, build, documents, tells, removed, broad, who, need, understand, preparing, partners, integrating, doesn, fit, neatly, five, core, flags, recognized, exception, borrows, structured, scannable, explains, links, detail, without, fully, matching, fuller, treatment, prev, summary, plain, print, listen, minute, read, published, jul, powered, press, community, service, november, manage, integrate, manager, domain, customization, import, project, reminder, collaboration, tasks, interactive, decision, trees, fields, management, variables, snippets, advanced, sign, role, based, access, control, multiple, workspaces, languages, key, creators, track, set, roles, permissions, invite, users, customize, create, quick, start, discover, available, pages, exploring, further, fetch, https, txt,

Text of the page (random words):
release notes documentation index fetch the complete documentation index at https docs document360 com llms txt use this file to discover all available pages before exploring further quick start create an article review article publish article customize site invite users set up roles permissions track analytics eddy ai features for creators for readers for integrations key features multiple workspaces languages role based access control single sign on private hosting advanced editor templates variables snippets glossary drive file management custom fields interactive decision trees collaboration tasks custom workflow review reminder import export project site customization custom domain integrations extensions analytics feedback manager api documentation integrate with document360 manage your api docs release notes november 2026 12 11 1 october 2026 12 10 2 october 2026 12 10 1 help troubleshooting self service support ask for a feature community glossary search ctrl k press ctrl k to open search powered by release notes published on jul 27 2026 5 minute s read focus listen print copy page copy as markdown for llms view as markdown view the page as plain text open in chatgpt ask chatgpt about this page open in claude ask claude about this page article summary prev next what is a release note a release note documents what changed in a product update it tells readers what is new what was fixed what was improved and what was deprecated or removed release notes serve a broad audience customers who need to understand the impact of an update internal teams preparing to support new features and partners integrating with your product see the content that doesn t fit neatly section of the five core content types guide which flags release notes as a recognized exception that borrows from reference structured scannable and how to conceptual explains impact and links to detail without fully matching any single type this article is the fuller treatment of that entry good release notes are specific complete and honest vague entries various performance improvements erode trust specific entries reduced article publish latency by 40 for projects with more than 10 000 articles build it customer facing vs internal release notes this guide covers customer facing release notes an internal release note written for support success and gtm teams ahead of a release is a related but distinct artifact with a different audience and often different content e g internal rollout timing support talking points not simply a shorter or more technical version of this one see the public vs private knowledge base structure section of the knowing your audience guide for the general principle behind this distinction structure of a release note page each release note is typically a single article covering one release use the following structure title use the format month year version number example may 2026 12 5 1 release date state the date the release was deployed released 29 may 2026 using the unambiguous prose date format specified in the numbers dates and time guide if your release notes are localized see the dates guidance in the dates numbers and units for localization guide a release date is exactly the kind of specific translatable date that needs to reformat correctly per locale not carry the english format through sections by change type group release note entries under consistent section headings use these standard headings new features functionality that did not previously exist improvements enhancements to existing features bug fixes resolved defects list specific symptoms that were fixed deprecations features being phased out with a timeline breaking changes changes that may require action from customers always highlight these prominently omit sections that do not have entries for that release do not include empty headings writing individual release note entries each entry should follow this pattern what changed one sentence stating the change clearly why it matters one sentence explaining the benefit or impact to the reader link to documentation a link to the how to or conceptual article covering the feature example entry new feature eddy ai feedback categorization eddy ai now automatically categorizes feedback by topic making it easier to identify patterns across large volumes of article feedback learn more example entry bug fix fixed articles exported as zip files were missing images articles that contained images uploaded via drive were missing those images in zip export this has been resolved example entry breaking change warning breaking change api token format update api tokens generated before 1 june 2026 will stop working on 1 september 2026 you must regenerate your tokens before this date how to regenerate api tokens use the standard warning callout format from the callouts guide for breaking changes with the text label warning always present alongside any icon an icon or symbol alone does not meet the accessibility requirement that callout type never be conveyed by icon or color alone template month year version released dd month yyyy new features feature name one sentence what changed one sentence why it matters link to docs improvements feature name one sentence what improved one sentence impact link to docs bug fixes fixed symptom description one sentence what the bug was and that it is resolved breaking changes warning change name one sentence what is changing one sentence what action is required and by when link to docs deprecations feature name deprecated one sentence what is being deprecated one sentence timeline and what to use instead link to migration guide writing guidelines for release notes be specific avoid vague entries improved performance is not a release note reduced page load time for knowledge bases with more than 5 000 articles by up to 35 is write from the customer s perspective focus on impact and benefit not on internal implementation details use consistent terminology refer to features by their exact names in the ui link to the documentation every entry for a new feature or significant improvement should link to the relevant article do not make readers search for how to use what you just announced flag breaking changes prominently use the standard warning callout and list breaking changes in their own section never bury a breaking change under improvements tense use past tense to describe that a change occurred fixed x was not saving correctly added support for csv imports present tense is also acceptable specifically when describing the resulting capability itself framed with now you can now export directly to pdf from the editor this is describing the current state of the product not narrating the release event which is why it s an acceptable variation rather than an inconsistency with the general past tense rule for release notes in the verbs tense and mood guide tone clear and informative release notes have a slightly more direct factual tone than other documentation they are announcements as much as documentation be concise a release note entry is not a marketing paragraph save promotional language for announcements and blog posts this is a tighter more neutral register than the intentionally warmer tone permitted in the writing effective notification and transactional emails guide release notes and announcement emails serve related but different purposes and shouldn t be written in the same voice self audit checklist before publishing check the release note against these questions does the title follow the month year version format is the release date in the unambiguous prose format localized correctly if applicable are only the sections with actual entries included with no empty headings does every entry state what changed why it matters and link to documentation where relevant are all breaking changes flagged with a proper warning callout with a text label rather than an icon alone is every entry specific with a concrete number or scope rather than a vague claim like improved performance does terminology match the exact feature names used in the ui is tense used consistently past tense for the change itself present tense only for describing the resulting capability is the tone factual and concise free of promotional language if this release involves an internal audience support success gtm has a separate internal release note been considered rather than assuming this one covers both was this article helpful yes no previous article troubleshooting articles next article creating an article related articles documentation guidelines help support support resources document360 style guide content strategy and foundations formatting guidelines help support support resources document360 style guide formatting guidelines reference articles help support support resources document360 style guide content types and templates document360 customers pricing resources request a demo migration request security private hosting enterprise readiness top features knowledge base portal knowledge base site knowledge base assistant integrations and extensions platform api analytics workflow ticket deflector drive seo support documentation support status feedback contact us contact us support document360 com rating 4 7 3000 about us our team our culture careers terms trust center privacy policy cookie policy soc2