BaikalSMS - a content management system for a website

BaikalCMS (BaikalSMS)

1. WHAT IS BAIKALCMS?

BaikalCMS is a commercial content management system for static
and lightweight hybrid websites. The product does not replace the file architecture
of the site and does not require a separate "content database" in the classical sense: the working
material is real files on the hosting disk (HTML, PHP, CSS, JS, XML, TXT
and other text formats).

The administration panel provides content editors and marketers with a clear interface
for edits, while developers retain control over the layout and PHP logic.,
templates and deployment rules. BaikalCMS complements the engineering stack (Git, CI/CD,
SFTP), rather than competing with it:
the repository and team processes remain the source of truth for the code, and the panel closes the task of safely editing
content without issuing raw production credentials to everyone.

2. THE THREE PILLARS OF THE PRODUCT (BRIEFLY)

• Security
  Sessions with strict checks, token validation, request frequency limitation
  (rate limiting), file upload control, security headers, Content-Security-Policy,
  logging sensitive actions is the level of discipline expected from
  industrial admin panel.

• Licensing
  Integration with PluginHub: linking the license to the domain, hard blocking of commercial
  functions without a valid license, a clear chain of "activation → work → renewal".
  It is convenient for agencies where the software is billed as a separate line in the invoice.
  to the client.

• Multilingual interface
  The panel and the built-in tour are available in the following languages: Russian (ru), Belarusian (be),
  English (en), Kazakh (kk), Kyrgyz (KY), Uzbek (uz), Thai (th),
  Vietnamese (vi), Chinese (zh). This reduces the cost of onboarding mixed teams.
  and reduces the number of errors due to misunderstanding of the interface.

3. MAIN FEATURES (IN DETAIL)

3.1. Visual and code editing
     Switching between visual mode for everyday blocks and full-fledged
     a code editor with syntax highlighting, search, and file tree navigation.
     The layout and styles laid down by the developers remain the main ones: visual mode
     it helps to change the content within a given structure, rather than "breaking" the layout.

3.2. File versions and rollback
     Each file can have a save history: rollback of the test header,
     a draft paragraph or experiment without completely re-uploading the entire site from Git.
     Reduces the risk of overwriting the production during the peak of the campaign. The versions in the panel complement Git,
     and they don't replace it in engineering pipelines.

3.3. Enhanced operations and resilience
     Request frequency limitation, download control, focus on CSP, logging,
     focused on real incidents and operator errors — without "noisy" toys
     dashboards.

3.4. PluginHub License
     Commercial use takes place through a clear activation script on the domain,
     extension and transparent support boundaries. The client's "silent" unlicensed
copy model is excluded.

3.5. Media and Attachments
     Images and files end up in predictable directories with stable URLs. —
     it is convenient to put statics behind a CDN and set up long-term caching.

3.6. Project search
     Quick search for pages, fragments, and occurrences even in a deep static hierarchy
     the site.

3.7. Compatibility with Git
     Git remains for branches, reviews, and automatic uploads; the panel is for operators.
     content that does not need direct access to the deployment chain.

3.8. Onboarding teams
     Built-in tour, unified terminology and multilingual UI reduce learning time
     as the number of editors grows.

4. WHO IS THE PRODUCT INTENDED FOR

• Studios and agencies — landing pages and promo sites with a panel that is actually used
  customers, while maintaining control over the stack and licensing.

• Marketing and product teams — campaigns without extra tickets for every small
  edits in the deployment pipeline; important pages remain under versions and approvals.

• Freelancers and integrators — a commercial offer in the spirit of "editable static
  premium class": fast hosting, neat admin panel, license via PluginHub for
  legal reuse.

• Regional and multilingual projects — a single dashboard interface in multiple languages
  for employees and contractors in different offices.

5. SYSTEM REQUIREMENTS (FOR DEPLOYMENT)

• PHP version 8.1 or later.

• Included PHP extensions: json, mbstring, fileinfo, openssl, curl (and others,
  specified in the current release documentation).

• HTTPS on a public contour; correct mod_rewrite rules (or equivalent)
  to route the panel's entry point.

• Sufficient disk space for website files and version history storage (depends on
  the retention policy you have adopted).

• An up-to-date PHP version is recommended, log monitoring, if necessary —
  restriction of access to the panel by IP, WAF and other measures in the spirit of protecting any
  production control plane.

6. LICENSING AND PURCHASE

• Purchase and license renewal are performed through the official PluginHub marketplace:
  https://pluginhub.pro

• License verification and activation are performed on the PluginHub side. Without a successful
  activations for the production domain commercial functionality and API panel
  they remain blocked.

• Save accounts, keys, and PluginHub support contacts; technical steps for
  Installation and operation are described in the "Documentation" section on the website. baikalcms.ru .

7. CONTACTS AND COMMUNICATIONS

Website: https://baikalcms.ru
E-mail:      support@baikalcms.ru
             sales@baikalcms.ru
Phone: +7 (923) 746-86-99 (in international format: +79237468699)

8. LEGAL AND INFORMATIONAL DOCUMENTS ON THE WEBSITE

On baikalcms.ru published (including in multilingual versions):

• Documentation — installation, first launch, licensing, editor, security,
  a typical workflow.

• Privacy Policy.

• Consent to the processing of personal data.

When using the site, cookies are used (including to save the selected language)
and the Yandex.Metrica web analytics service; details can be found in the privacy policy
on the site.

9. LIMITATIONS AND HONEST EXPECTATIONS

• BaikalCMS does not replace Git, FTP/SFTP, CI/CD and infrastructure tools — it
complements them with a layer for content operations.

• Simultaneous editing of the same file by multiple users
  without coordination, it leads to the fact that the last save "wins" (as in
  two IDE tabs on the same path). It is recommended to divide the areas of responsibility and
use the version history.

• The final terms of the software license, the rights to staging/additional domains, and the scope
  The supports are determined by the purchased product on PluginHub and your contract;
  check the current rules with the marketplace when expanding the infrastructure.

Check the relevance of links and system requirements on the official website and in
the documentation for your distribution version.