aaa3604cd4
Normalized the 18 shared/ui components (button, input, select, badge, card, section-card, table, dialog, empty-state, form-field, pagination, toggle, image-field, key-value-editor, locale-tabs, color-picker, code-editor, skeleton) — these are the reusable primitives consumed across storefront/builder/backoffice — to use the new --font-size-*/--font-weight-*/--line-height-* tokens and the --radius-xs/--radius-full tokens introduced in the previous commit, replacing one-off literal values (0.875rem, 13px, 999px, 12px, etc.). Fixes found along the way: - code-editor.component.scss: focus border/shadow used a hardcoded #497671 (the dexar tenant's primary color) instead of var(--primary-color) — would not adapt to the lavero/novo tenant themes. Now theme-aware. - section-card.component.scss used raw 16px/18px/14px radius/padding instead of the --radius-lg/--space-* tokens the sibling card component already used, so cards and section-cards had slightly different rounding/padding for no reason. Aligned to the same scale. - toggle/badge/item-tag: raw 999px pill radius replaced with the new --radius-full token. Deferred: syntax-highlighting colors in code-editor (.cm-*) are intentional and left untouched; tenant brand colors in the three theme.scss files are intentional per-tenant palettes, left untouched.
Marketplace Frontend
Angular marketplace frontend for the client demonstration. The app uses standalone components, signals, runtime branding/configuration, and a production build optimized for the current marketplace experience.
Features
- Responsive marketplace storefront
- Category browsing and product detail pages
- Search and shopping cart flows
- Telegram login integration
- Payment handoff through the existing backend contract
- Runtime branding and configuration loading
- PWA manifest and service worker configuration
Development
Install dependencies:
npm install
Start the local development server:
npm start
Build for production:
npm run build
The production build is written to dist/dexarmarket/.
Project Structure
src/
├── app/
│ ├── components/ # Shared storefront components
│ ├── core/ # Runtime, config, guards, providers, interceptors
│ ├── dynamic-renderer/ # Page, section, and widget rendering pipeline
│ ├── facades/ # Runtime, website, builder, and backoffice facades
│ ├── pages/ # Storefront, info, legal, cart, search, and item pages
│ ├── services/ # API, cart, auth, SEO, Telegram, and language services
│ └── widgets/ # Dynamic renderer widgets
├── assets/mock/ # Local mock configuration and catalog data
├── environments/ # Development and production environment settings
└── styles/ # Shared global styles and themes
Useful Checks
npm run build
npm run arch:check
Notes
- Authentication and payment integrations are intentionally left on their existing contracts.
- Renderer and runtime architecture should remain stable during demo preparation.
- Client-facing content should avoid placeholder names, mock labels, and temporary routes.