7cb1c8c3c6
Mechanical, value-preserving substitution: every literal font-size declaration across src/app (89 files) that matched one of the 9 typography scale steps introduced earlier (--font-size-xs..4xl) was replaced with var(--font-size-STEP, <same-or-nearest-step-value>). Values within ~0.03rem/1px of a scale step were snapped to that step (e.g. 0.85rem and 0.8rem both -> --font-size-sm/0.8125rem; 0.9rem and 0.875rem -> --font-size-base/0.875rem) to consolidate roughly 15 near-duplicate sizes down to the 9-step scale, per the RC design-system finalization brief. This eliminates most of the font-size fragmentation found across the app (previously: 0.7/0.72/0.75/0.78/0.8/0.8125/0.85/ 0.875/0.9/0.9375/0.95/1/1.05/1.1/1.125/1.15/1.2/1.25/1.3/1.35/1.4/1.5/ 1.75/2rem all in live use simultaneously). Not touched (deliberately, see docs/UI-DESIGN-REVIEW.md): 3rem+ display sizes (too large a jump to any existing step, would need a --font-size-5xl addition), font-size values expressed via clamp()/calc(), and any component listed as intentionally distinct (code-editor syntax tokens, theme brand colors).
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.