Skip to content

Guide: section «Наборы компонентов» (component sets) - #14

Merged
zabarov merged 3 commits into
mainfrom
docs/component-sets
Nov 3, 2026
Merged

zabarov merged 3 commits into
mainfrom
docs/component-sets

Conversation

@zabarov

@zabarov zabarov commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

A new guide section, /ru/guide/sets/, with four subpages:

  • Наборы компонентов (index): what a set is, the catalogue of sets (admin, view, chat, mail, editor, chart under the Pro licence; effects free), what stays in SIMAI Framework.
  • Подключение набора: one line, data-sf-sets on the core script; a pinned version, several sets, a set's own base through SF_BOOT_CONFIG.packages, what the Loader does when something is wrong.
  • Версии и совместимость: the shared index @simai-studio/sets (address and a real entry), how the Loader picks a release, how to update.
  • Лицензия and Имена компонентов: the Pro licence, the shared sf- family registry.

The SIMAI Framework release with sets is out (pair ui-eea8c0a97cc7, npm @simai-studio/ui 5.20261103.2154, core.runtime 1.25.0), with @simai-studio/effects 1.0.0 and @simai-studio/sets 1.0.0 on npm/jsDelivr, so no page carries a «Скоро» mark. Facts were checked against the published index, the effects package on jsDelivr and the Loader source of the pair (src/core/js/sets.js, loader.js at c4df9ae6fc05). CDN addresses stay <выпуск>: the docs audit holds them to this site's pinned release (5.20261102.1446); the text names 5.20261103.2154 as the first release that reads data-sf-sets.

Local checks against pinned ui / ui-source / ui-builder / ui-pro copies: composer docs:check, the guide structure audits, the Smart lesson audit, migration idempotency (0 changed, clean diff).

🤖 Generated with Claude Code

zabarov and others added 3 commits November 4, 2026 00:02
What a set is and the catalogue of sets (admin, view, chat, mail, editor,
chart under the Pro licence; effects free), the one-line connection with
data-sf-sets (a pinned version, several sets, a set's own base, what the
Loader does when a set is missing or unknown), versions through the shared
index @simai-studio/sets, the licence and the shared sf- name registry.
Marked «скоро»: the connection needs the SIMAI Framework release with
core.runtime 1.25.0, not released yet.

Sources: ui-control control/decisions/2026-11-03-component-sets.md and
ui-source feat/component-set-standard (standard simai.component-set 1.0.0,
docs/developer/component-sets.md, src/core/js/sets.js).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The SIMAI Framework release with component sets is published (pair
ui-eea8c0a97cc7, npm @simai-studio/ui 5.20261103.2154, core.runtime 1.25.0),
and so are @simai-studio/effects 1.0.0 and the index @simai-studio/sets 1.0.0.

- index, connect: the «Скоро» notes become the release the sets start from;
  the index says effects is the first released set and Pro components still
  come as the pro package until their sets are out.
- connect: the example pins 5.20261103.2154; the generic <выпуск> form stays.
- versions: the GitHub release with a checksum is not published for
  effects-ad9823f83a56; say where the files are on jsDelivr instead, add the
  checksums the index holds, its address and a trimmed real index entry.

Checked against the published index (simai.framework.set-index v1), the
effects package on jsDelivr and src/core/js/sets.js + loader.js at
c4df9ae6fc05 (the pair's source).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The docs audit holds every @simai-studio/ui CDN address to the pinned
release (cdn_npm_version_mismatch); this site pins 5.20261102.1446, older
than the sets release. The example keeps <выпуск> and the text names
5.20261103.2154 as the first release that reads data-sf-sets.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@zabarov
zabarov merged commit f74a958 into main Nov 3, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant