The site builder moves on by two steps of its plan: the panel screen "Конструктор сайта" edits a draft of the layout and of the blocks - structure, frame of the page, inspector, library, settings and palette - and the button "Опубликовать" carries that draft to the site in one transaction of the layout, the addresses of its pages and the rows of _blocks. A second editor or a site changed meanwhile is refused instead of overwritten, an unsure commit is finished by a witness row, and the last ten publications can be brought back into the draft.

Core changes:

1. The panel screen of the builder (admin/modules/layout.php, config/modules.php, partials/layout-*.html, fragments/layout-field.html, assets/css/layout.css, assets/js/layout.js, layouts/admin.html):

2. the module layout of the super administrator, every write a POST through checkAdminPost('layout'); the screen covers the window (is_full drops the shell of the panel) with the tree, the frame of the draft and the inspector

3. the draft lives in storage/layout/draft.json: the layout, the changed, new and deleted blocks with the rows they began from, the name and the logo of the site, and fifty steps of Undo and Redo

4. the frame shows the page by the signed link of the draft and reloads where it stood after every write; a pick fetches the inspector, a write swaps the tree, the inspector and the state out of band

5. the fields take their types from Field, the kinds of the builder (markdown, file, focus, icon, tone, choice) their own checks; the library of sections, the settings with the screens that keep the rest, one Ctrl+K

6. The entries and the canon the screen takes (fragments/dock.html of both themes, menu-grid-item.html, menu-list-item.html, assets/css/theme.css and base.css, plugins/system/slaed.js, core/system.php):

7. "Конструктор сайта" is an app of the floating menu after the app of the page
8. a card of the grid may carry the schema of a section, a row of the list a level and attributes of its own

9. the capsule of the editors gets a state shown at once, a window held at its top; a select of pictures keeps its preview after a swap of htmx

10. The publication (core/classes/layout.php, core/system.php, core/classes/update.php, admin/modules/layout.php, partials/layout-state.html):

11. layout joins the shared areas of setConfigFile(), so config/layout.php is written in the Closure form with its native types; Update::SHARED takes it outside the check that a shared pack brings node.php

12. Layout::setPublish() checks the published file against the checksum the screen opened with, writes the blocks through the module (each row against the row the draft began from), marks the addresses of deleted pages gone, moves a renamed page with its former address kept for 301, and saves the layout with the path each page got

    • the proof of the operation is the first written row whose fingerprint changed (Layout::getWitnessHash(), a row

of _blocks or the rows of _routes of a page); setConfigRestore() reads it FOR UPDATE as it reads the type row
of Node, and a row matching neither side keeps the marker

• the name and the logo of the site follow by the string form into config/global.php; a failed write keeps them

in the draft and says so

• refusals with nothing written: a block changed in "Блоки и баннеры", a site changed after the screen opened, an address the registry does not take

• the restore screen of the configuration names the proof of a publication

• Two editors and the history (admin/modules/layout.php, partials/layout-screen.html, partials/layout-story.html, assets/js/layout.js):

• the draft carries its revision, its time, its writer and the screen that wrote it; every write posts the screen and the revision it saw, and a write over the change of another screen is refused by name and time

• the last ten publications are files pub-<n>.json with the author, the layout, the blocks and the name and logo of the site; the window "История публикаций" brings one back into the draft as a step with Undo

• Languages, help, docs and tests (admin/lang, lang, admin/info/layout, docs, tests, tools):
• the words of the screen and of the publication in six locales
• the help of the builder in its current state; docs/NODE.md and docs/UPDATE.md for the five shared areas

• LayoutDraftTest over the lifted functions of the module; LayoutPublishTest over real requests of route_probe.php publish: the refusals, the publication, the addresses, the history and an unsure commit both ways; ConfigFileTest over the five areas and the witness row; the audit baseline and the contrast registry

Benefits:

• A site is changed in one step that either lands whole or not at all, never half a layout with old blocks
• A second administrator or a screen left open cannot write over another one's work unnoticed
• Every publication can be taken back from the history

Technical notes:

• Stored data: storage/layout/ holds the draft and the history, outside the document root and never in a package
• config/layout.php is now written with native types; the reader still takes the text form an older save left
• The stand keeps its own config/layout.php outside this commit

The site builder moves on by three steps of its plan: a page of the layout is a row of the address registry at the root of the site, the theme lite draws sixteen types of section on the classes of its presentation, and a module brings a type of its own with a provider and a default fragment. Beside it the demo stand gets two series of the panel, the statistic redrawn eight ways and the monitor four ways, the cockpit of the monitor carrying the pulse of the server, and the chart of the presentation gets washes under its lines.

Core changes:

1. The page of the layout at its address (core/classes/route.php, core/classes/layout.php, public/index.php, core/system.php, core/security.php):

2. the kind page of Route lives at the root: its own check of the name under the grammar of a slug, the empty prefix in addRouteRow() and isRouteReserved(), 301 from a former path and 410 for a deleted page

3. a page of the layout carries the name page-<key> in $conf['name'], its title, description, og:image, robots and canonical address through setHead(), and its entry in the sitemap

4. the page 404 of the layout answers through setError() with the code kept; a page may be for users only

5. the read-only link of the draft: a signed token with a term over storage/layout/draft.json, noindex, the mark "Черновик" and the answer 403 for a dead link; storage/layout/ is ignored by git

6. The sections of lite (public/templates/lite/sections/, fragments/section.html, assets/css/presentation.css):
7. "Основа": hero, features, media, text, steps and cta, each a description sections/<type>.json and a fragment

8. the other groups: gallery and video, stats, voices and team, faq, prices and map, embed and own HTML

   • the fragments of the feed, the record and the block wait for their data without a description
9. every section stands in the frame of a presentation section with its number, anchor, devices and dates
10. the alt of a picture, its point of focus (--sl-d-focus), Markdown through Parser::filterDoc() with the module layout

11. the own rules sl-sec-* only where the presentation has no form: the picture beside a text, the claim, the columns, the frame of an outside service, the cards of the contacts

12. The rendering of a section (core/classes/layout.php, core/classes/template.php, public/plugins/system/slaed.js):

13. the kinds code, video, page and point: raw HTML of the super administrator, the privacy mode of YouTube or a film of the uploads, a page of https alone with its host, a map of OpenStreetMap from one field "lat, lon"

14. an outside frame waits behind a placeholder, the picture of the section or its icon with a button, and asks the outside server only after the click; slaed.js puts the frame of the template in its place

15. every fragment gets the values of the theme of the layout as parts and every item is_first
16. a section whose fragment prints nothing loses its frame and its number

17. Template::getHtmlSection() renders the default fragment a module brings where the theme has none, held inside the folder of that module

18. The showcase of sites as a type of the module presentation (modules/presentation/):

19. sections/sites.json, the provider sites.php and the default fragment sites.html; lite draws it on fragments/presentation-site.html

20. getPresentationSites(), getPresentationBrand(), getPresentationDna() and getPresentationVoices() move into common.php, so the provider never runs the module

21. The chart of the presentation (public/plugins/presentation/presentation.js, partials/presentation-rhythm.html):
22. a chart marked data-sl-pres-fill="all" lays a wash and a soft shade under every line, as the monitor of the panel

23. The demo series of the statistic and the monitor (public/demo/st-.html, mon-.html, assets/st., assets/mon., assets/demo.js, README.md):

24. the statistic: eight faces of admin.php?name=statistic on one engine and one corpus of the counter

25. the monitor: four faces of admin.php?name=monitor on the engine of the statistic, the findings of the live page drawn mended

    • the lamp, the state and the checks follow thirteen signals of the server and its programs, not the checks of SLAED
    • the lamp of the cockpit shows the pulse of the server: the heart, the rate, a running cardiogram and the mood in

the tone of the state, with the scene "Ночь" of the stand

1. Languages and tests (admin/lang, lang, modules/presentation/lang, tests):
2. the labels of the sections in six locales, the words of the draft and of the outside frames on the site

3. LayoutTest holds the shape, the kinds, the outside frames and the type of the module; RoutePageTest and RouteRegistryTest hold the page at the root

Benefits:

• a page of sections is a page of the site with its address, SEO and sitemap, without a module of its own
• a section of a site visits no outside server before the visitor asks for it
• a theme brings only markup and a schema, a module brings its own types with their data

Technical notes:

• config/layout.php stays version 1; a page of the builder is a row of _routes of the kind page with its number as oid
• tools/ui-contract.php declares --sl-d-focus and --sl-d-frame
• no change of the database schema; the stand database and uploads/ are unchanged

The builder of the demo stand showed what a site owner edits in one place; the owner now judges it as the panel screen it is to become. Its chrome is the canon of the panel, the fields are the fields of the panel forms, the publication carries checks, a note and a history, and the screen opens its own manual, as every panel screen does.

Core changes:

1. The chrome (public/demo/sb-01-builder.html, assets/sb.css):

2. The tools stand in the capsules of the editors (sl-editor-pill, sl-editor-grp, sl-modal-act) by their groups, the widths in the segmented control, the state as a chip, the help and the settings last at the edge

3. The windows of the screen: the manual, the settings with the file of the layout read in the code editor of the panel, the link of the draft, the history, the checks, the palette

4. Editing (assets/sb.js, assets/sb-data.js):

5. The fields of the panel forms: the switch and the segmented control with flipped answers, the checkbox list, the swatches, the file field with the file manager, the logos of the theme, a focus grid for a cropped picture

6. Markdown texts in the editor window of the panel, raw markup in its code editor, each shown by its beginning

7. A field that differs from the site carries the way back to its published value; the guest view, the neighbours of a pick, the address of a section by its anchor

8. The library of sections with "Мои секции", "Недавние" and the groups as a filter; a type a page holds once, the slot of a module, has no twin and answers at the module's address with its SEO

9. Publication (assets/sb.js):

10. Checks of every field and of the links and pictures inside the Markdown texts, the count of changes in words, a note of the author, the blocks published with the layout, ten versions and the way back to the site

11. The canvas and the manual (assets/sb-site.js, assets/sb-site.css, sb-site.html, assets/sb-help.md):
12. The sections drawn on the tokens of the theme lite, the slot of a module and the pages of the builder by address

13. sb-help.md is the manual the window "Руководство" renders: how to open the builder, the screen, pages, sections, menus, theme parts, blocks, the draft and the publication, in Russian like the help of the panel

Benefits:

• The owner judges the builder in the look and with the mechanics the panel screen will have

Technical notes:

• The stand is outside the release (export-ignore); the draft lives in localStorage, no request but the manual
• The demo loads ../plugins/system/editor.js and the CodeMirror stylesheet of the plugins for its editor windows

What a site owner changes today only by editing HTML - the home page, the main and the footer menu, the slogan, the badge and the social links of the header, the strip before the footer, the contacts - is gathered into one editor and one layout, which in the system would be one file config/layout.php. The stand shows it before any line of the core is written, as the decisions of the owner of 2026-10-26 describe.

Core changes:

1. The editor (public/demo/sb-01-builder.html, assets/sb.js, assets/sb.css):
2. Three tabs over one layout: the page with its header, sections and footer, the two menus, the theme parts

3. The page in a device frame in the middle: hover names a part, a click selects it everywhere, a double click edits the text in place; the selected section moves, copies, hides, deletes and adds below through the library

4. Undo by gesture, a draft and a publication, a check before publishing, ten published versions, anchors, the device switch, page presets, Ctrl+K, the export and import of layout.json, menu items from the modules

5. Blocks by the model of the system: the four zones a theme prints, "where to show" read as getBlocks() reads it and written as editsave() writes it, the order of a position, a drag on the tree and on the page

6. The chrome of the editor is the mechanics of the panel: canon windows, setToast(), the tabs, the icon window, the drag marks and the buttons of the panel

7. The canvas (public/demo/sb-site.html, assets/sb-site.js, assets/sb-site.css, assets/sb-data.js):

8. The sections of the theme lite on its tokens with the live header and footer of the site; inside the frame of the editor it is the page in edit mode, alone it is the published site with the pill "Edit page"

9. sb-data.js holds what both share: the section catalogue with its field schema, the theme parts, the menus and the layout of a fresh site

10. The ways in (public/demo/admin/, public/demo/site/, assets/demo.js):
11. The panel reference: "Site builder" in the menu "Administrator" and a card on the home (mark D13)
12. The site reference: "Edit page" in the floating menu (mark C15)
13. The manifest gets the series "Site builder"
14. The stand description (public/demo/README.md):

15. The series, the files, the owner's decisions with the mechanics of the system each part of the chrome reuses, the twelve accepted features and the open point of the new "which" value page:<key>

Benefits:

• The owner judges the builder on a working page before the core class, the fragments and the panel screen exist

Technical notes:

• The stand is outside the release; the draft lives in localStorage (sb.draft, sb.live, sb.history), no request reaches the server but the header and footer of index.php?name=presentation

The stored texts become Markdown, so the code that still produced BB moves with them: the reply quotes, the inserts of the editors and the file window, and the shipped contact text. The meta image of a text is read from a Markdown image. Bare addresses are linked by the GFM autolinks of the parser at render, which leaves the write-time rewrite into [url] and [mail] and the settings that steered it nothing to do.

Core changes:

1. Reply quotes (core/user.php, modules/forum/index.php):

2. The reply to a private message and the quote of a forum post are the text as "> " lines and a blank line after them; the branch for an HTML editor goes, as those editors serve the panel alone and both forms are site forms

3. Inserts of the editors (public/plugins/system/, public/plugins/editors/toastui/):
4. getEditorInsertText() of slaed.js writes name, with its Markdown characters escaped, and

5. editor.js writes a Markdown image in every field; filemanager.js writes one through addSource(), the side-taking [img=...] of addImage() goes, and the side choice of the insert window hides for a picture

   • data-sl-opts="align" moves to the wrapper of the choice in window-body-insert.html of both themes, as size has it

6. The quote button of Toast UI goes, Toast keeps its own; _EQUOTE leaves the six lang/*.php, its icon leaves skin.css of both themes

7. The meta image (core/system.php):
8. getImgText() takes [attach] first, then the Markdown image with an <address> or a bare one; the two [img] forms go
9. The link rewrite (core/security.php, core/classes/, admin/modules/, config/):
10. filterClickable(), getEd2kLink() and filterCut() go; filterHtml() loses the argument that only switched it off
11. Comment and Privat lose the switch and the link flag: getLinkFlag(), the 'click' setting

12. The setting "Convert addresses into hyperlinks?" of the configuration and "Prohibition of the automatic conversion of links" of the comments go with _CLICABLE, _CLICABLEINFO, _NOALINKP and the keys clickable and alink

13. The update and the shipped settings (public/update.php, config/contact.php):
14. setUpdateConfig() drops clickable of a 6.2 global and alink of 6.2 comments; setUpdateMerge() retires both
15. The shipped contact text is Markdown, equal to what the converter makes of the former BB one
16. Help and documents (admin/info/, docs/):
17. The help of the configuration and of the comments loses the two settings
18. docs/EDITORS.md: a picture enters as a Markdown image without a side; docs/NODE.md names the retired keys
19. Tests (tests/):

20. FileAccessTest: the reply form offers the quote as Markdown lines and a quoting reply binds the quoted name; the meta image of a topic is its attachment or its Markdown image

21. PrivatClassTest: a bare address is stored as typed and linked in the rendering
22. UpdateConfigTest and UpdateArchiveTest: both keys leave on the 6.2 and on the 6.3 path
23. EditorWindowTest follows the Markdown image writer of the shell

Benefits:

• No code of the site writes BB any more; what an author or a reply produces is Markdown the standard reads
• One way a bare address becomes a link, at render, instead of two that disagreed

Technical notes:

• Breaking: the settings clickable and alink are gone; a bare http(s)://, www. or e-mail address is always a link, for guests too, as the parser renders it since the GFM autolinks

• The stored texts are not touched here; their conversion is the text unit of update.php