38253f7e83
- product-carousel-widget: implicit CSS grid track had no min-width:0, so the flex scroller's intrinsic content width (fixed 220px product cards) overflowed the grid item and pushed body width to ~2187px on a 1440px viewport, squeezing the entire homepage into a ~340px column. Added min-width:0 to the track and scroller (standard grid/flex overflow fix). - bootstrap.json mock fixture: about-us/privacy-policy/terms-of-service static pages (the real CMS pages served via bootstrap.staticPages, per docs/PROJECT_INDEX.md) used a 'content' field, but content-page.service.ts's normalizePage() only reads 'html' - ContentPageBootstrapInput has no 'content' field. Title rendered, body was always empty. Renamed the 3 fixture entries' field from content to html to match the schema; content now renders. - compare-table: colour row rendered raw hex/name values as plain text (e.g. '#fCfCfC') with no swatch, inconsistent with variant-selector's established colour-swatch pattern used on the product page. Added a small circular swatch (reusing the same border-radius:50% pattern) next to the value. Verified live via ng serve: overflow gone (body/viewport width match at 1440/1280/375), static pages render real content, compare swatch displays. tsc --noEmit and ng build both clean (pre-existing bundle- budget warning only, already tracked in KNOWN-ISSUES item 12). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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.