Changelog
The site changes are recorded version by version.
Each release names the pages, content, or publishing work that changed on chawo.ai.
Site release history
0.6.1
Published pages now keep both channel-name locales when existing content is refreshed.
- Existing pages accept newly added required block fields without being recreated.
- English and Russian channel names stay attached to the same channel row.
- Refreshing committed content replaces an editor change only when overwrite is requested.
- The content check now compares a fresh import with an update of existing content.
0.6.0
The first screen now frames Chawo as chat management and automation.
- The headline names chat management and automation in one compact statement.
- Five channel inputs meet one editable flow, with a written status beside every input.
- The flow uses ports, curved connections, and a dotted editor canvas across the first screen.
- On narrow screens, the canvas moves below the copy and keeps its labels readable.
0.5.0
The Chawo mark now names the site in its header, footer, and browser tab.
- The striped Chawo mark replaces the temporary text wordmark in the header.
- The footer places the Chawo logo apart from the ZAI project credit.
- The browser tab now uses the canonical small Chawo mark.
- Every size keeps one coral stripe in both color schemes.
0.4.2
Runs of fact sections now change surface and pair each heading with its explanation.
- Consecutive fact sections now move through page, panel, and inverse zones.
- On wide screens, each heading sits beside its explanation; on narrow screens, the pair stacks in reading order.
- Explanations use a type step between body text and a page lead.
- Product limits now place each refusal in its own definition block.
0.4.1
The canonical brand logo now identifies the project in the footer, and Ivan appears on the not-found page.
- The footer places the canonical brand logo beside the project credit.
- The not-found page chooses Ivan’s dark or light image from the active color scheme without client-side JavaScript.
- A generated asset manifest records the source plugin, its version, and the generation date.
- Verification compares every published brand asset byte for byte with the plugin source.
0.4.0
Editors can now place uploaded images in page layouts while preserving localized descriptions and existing page changes.
- An image block keeps the uploaded file’s proportions, alternative text, and optional caption.
- Each image can follow the content container or fill the width of its page zone.
- Translator access is limited to non-default locales.
- Seed updates can target globals, pages, releases, or media separately.
0.3.1
Prices, capability status, questions, exchanges, and the first-screen flow now have distinct visual structures.
- The home page now shows the three published launch prices beside the boundary that nothing is for sale today.
- Capability status leads a two-column register instead of sitting as a small label.
- Questions use two columns, and the example exchange makes the handover the visible turning point.
- The first-screen flow and its Russian decision label have more room.
0.3.0
The site now has distinct page zones, larger headings, square-cornered cards, and interaction states for its controls.
- Background changes separate each page into distinct visual zones.
- Large headings set the reading order at the start of each page.
- Cards use flat surfaces and square corners in place of the previous soft shapes.
- The site has a dedicated mobile menu, and controls show hover and pressed states.
0.2.1
Russian flow labels now stay inside their nodes on the home-page canvas.
- The call, follow-up, and qualification labels now wrap at word boundaries.
- Each label keeps its full wording while fitting the node that owns it.
0.2.0
The site now publishes Russian pages, chrome, release notes, and locale-specific status.
- Russian pages keep the English document structure while carrying their own copy.
- The language switch links the same published page without client-side JavaScript.
- Payload publishes English and Russian locale status independently.
- The copy gate checks Russian vocabulary and catches English field fallback.
0.1.8
The site now records its changes on this page, and screenshot checks compare exactly.
- This page lists each site update by date and version.
- Each entry names the changes included in that version.
- Release notes now appear alongside the site’s other published pages.
- Screenshot checks now compare exactly.
0.1.7
The product page corrected two boundary statements, and non-canvas hero leads regained their earlier measure.
- The product page now names the delivery and model-call boundaries from the capability register.
- The home page keeps its title within the 60-character limit.
- Non-canvas hero leads now use the measure from before the home redesign.
- The desktop end-to-end check guards that measure.
0.1.6
The site added comparison pages for Salebot and Jivo with sourced capability rows.
- The Salebot page traces each comparison row to its published source.
- The Jivo page distinguishes its website widget from Chawo’s roadmap widget.
- Localized block fields supply the comparison labels and source links.
- The footer now links both pages under Compare.
0.1.5
Payload became the site content source, with early-access submissions, redirects, and authenticated preview.
- The develop server reads published pages and globals from Payload.
- The seed adds absent pages, forms, and globals while preserving editor changes.
- The early-access form records submissions without client-side JavaScript.
- Payload records now drive redirects and authenticated draft previews.
0.1.4
The site gained its Payload foundation, admin route, reusable blocks, seed, and source parity.
- The Payload admin route exposes page, media, user, and global schemas.
- Pages reference nineteen reusable blocks through the shared block field.
- Published pages remain identical while editors move content into Payload.
- Publish hooks validate copy and revalidate page and index routes.
0.1.3
The home page gained a first-screen flow canvas, progressive motion without JavaScript, and a ten-block reading order.
- The home page drops four blocks and keeps a ten-block reading order.
- Wide screens place the flow canvas beside the hero copy, while phones place it below.
- CSS runs the flow motion and removes it when the reader requests reduced motion.
- The no-script page preserves the same text and canvas.
0.1.2
The repository gained the Payload content schema for pages, blocks, localization, and publishing.
- The database design maps eight collections, three globals, and nineteen reusable blocks.
- One locale dictionary and a shared block order govern every field.
- The schema specifies page validation, previews, migrations, and source parity.
- The dependency manifest pins Payload packages to version 3.88.0.
0.1.1
The home page now names chat bots, broadcasts, chat automation, AI, and Telegram in its first screen.
- The hero eyebrow carries the category terms above the handover claim.
- The first-screen heading locates the bot-to-person handover on the canvas.
- The lead ties each stated capability to its register status.
- The footer mirrors the category language from the first screen.
0.1.0
The site reframed Chawo around three named pillars and documented the work ahead.
- The mission names the three product pillars and the seams they cover.
- The roadmap keeps planned work and decisions that need an owner in one place.
- CSS treats motion as progressive enhancement and removes it for readers who request reduced motion.
- Each published update carries a version that the running site reports.