68d679759d
- Add --font-size-xs..4xl, --font-weight-*, --line-height-* tokens to src/styles.scss (no typography scale previously existed) - Add --radius-xs (4px) and --radius-full (999px) to all three theme files (dexar/lavero/novo) to cover chip/badge and pill shapes already in wide use (41x 999px, 9x 4px across the app) but previously hand-written per component - Apply the new tokens to global base elements (body/h1-h6/p/small), the .btn/.mt-*/.mb-*/.p-* utility classes, and the shared .item-badge/.item-tag/.item-simple-desc classes - Extend --space-* scale with --space-2xl (48px) and --space-3xl (64px) for section-level gaps
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.