admin-frontend

This module provides an administrative frontend interface for managing restaurant or business configurations, including themes, modes, colors, and settings. It offers a user-friendly way to customize and control various aspects of the frontend experience through interactive components and configuration tools.

development mode set system environment variable DEV=TRUE

Docs

• Программные сниппеты из модулей — как другому модулю отдавать HTML-сниппеты в собираемый фронтенд через событие admin-frontend:collect-snippets.

2.7.29 The recipe form names the values of a list by the enumDescriptions of the schema: target reads "Сайт с отрисовкой на сервере (ssr)", "Статическая страница (www)" instead of bare values 2.7.28 Storefront rendered on the server: a recipe with "target": "ssr" (factory project layout2) is built as the ssr target; its client/ becomes the static folder, server/ goes next to it into frontend-server/<build hash> (never served), and handle() of its bundle renders the pages. The module answers the container's storefront:get-renderer (restoapp config/http.js, asked once) with one object { mode, handle } it keeps current: at start from the last successful build of the history, after a build from the target of the built recipe; www brings back the static site without a restart. The website channel is ready for an ssr build when its server is loaded. The recipe setting schema takes target 2.7.26 Website sales channel key defaults to web, the same value the storefront sends as the order source (orderedOnPlatform), so a new install gets the order source equal to the channel key. Existing website channels are kept as is: core adopts them by type + provider, and orders still resolve to them through platforms 2.7.25 Fixed the published build: the website sales channel was never registered (Class constructor SalesChannelAdapter cannot be invoked without 'new'). The publish script compiled with TypeScript 3.9, which does not know the es2022 target and silently emitted ES5 classes that cannot extend the core's native SalesChannelAdapter. TypeScript is now ^5.9.3, useDefineForClassFields: false keeps the field semantics of earlier releases, and publishing fails if npm i fails or tsc emits ES5 classes 2.7.24 Website sales channel is registered through the core SalesChannelAdapter (SalesChannel.alive): core creates or adopts the channel record, readiness comes from getStatus() (storefront built, its files on disk and served) and is refreshed after every build; the module no longer writes the website record and its RESTOCORE_URL url. On older cores only the web-storefront type is registered. web-storefront declares supportsMultipleInstances: false; marketplace tags sales-channel, sales-channel:web-storefront. Removed the install wizard steps (about/colors) and the baked frontend (lib/processBakedFrontend, .ci/bake_admin_frontend.js): the storefront is configured and built on the frontend setup page 2.7.23 Fixed the storefront always showing prices in "$": the Admin Frontend install wizard hardcoded currencySymbol "$" into the recipe; it now takes the symbol of the project currency (DEFAULT_CURRENCY_ISO, e.g. RUB -> ₽) and falls back to "$" only when no currency is configured 2.7.22 Fixed FDS channel ignoring FDS_URL: the default channel, history labels and the Layout setup selector now follow the FDS host that actually builds (FDS_URL wins over BRANCH), so a manual build no longer silently goes to the BRANCH channel 2.7.11 Fixed module-provided snippets (e.g. blocking-popup) never appearing in the Snippets list: SnippetProvider now reads the bare emitter global instead of calling @webresto/core's getEmitter() itself, avoiding a dual module-instance mismatch under this app's tsx runtime 2.6.0 Schema-driven recipe form editor (Form ↔ JSON tab) with reactive key suggestions per inventory unit 2.3.7 Add baked frontend generation