How zesty-io/accounts-ui works
Project type and purpose
• This is a single-page, full-stack front-end application (PWA) that provides an “account management” UI for the Zesty.io CMS.
• It uses a micro-frontend approach: a “shell” (routing, auth, global UI) plus multiple sub-apps (“account,” “blueprints,” “dashboard,” “properties,” “support,” “teams”) each built, bundled, and mounted separately.
• State is managed centrally via Redux. The design system is shared via an external package (@zesty-io/core).
File structure
• Top-level:
• Dockerfile, app.yaml → containerization & GCP deployment
• .github/workflows → CI/CD pipelines
• ci/scripts → local test setup, screenshots, secrets
• cypress/ → end-to-end tests (fixtures, integration specs)
• src/:
• src/shell/ → main shell app (routing, auth, notifications, error handling)
• src/apps/…/ → six sub-applications, each with its own package.json, webpack.config.js, src/index.js, views, components and optionally a Redux sub-store
• src/util/, src/vendors/ → shared utilities and third-party polyfills
• Build scripts in bin/ orchestrate assembling and deploying bundles.
Extract insights from the README
• PWA focus → service worker, caching, lazy loading eventually.
• Global Redux store; design system follows atomic design.
• Error notifications via a global Notify component, error aggregation to Sentry.
Components
a. Main components
• User’s Browser (Client)
• CDN / Static Asset Hosting
• NGINX (proxy, TLS termination)
• Shell Application
• Sub-App Bundles (“account,” “blueprints,” etc.)
• Global Redux Store
• Backend API (Zesty.io CMS services)
• External Services:
– Auth (OAuth/JWT issuer)
– Sentry (error aggregation)
– CI/CD (GitHub Actions)
b. Relationships & data flows
• Browser → CDN → NGINX → serve index.html + shell bundle + all sub-app bundles (initial load)
• Shell handles routing, mounts sub-apps based on URL
• Sub-apps dispatch Redux actions → update global store → subscribe components
• Components invoke src/util/request.js → HTTP calls → backend API
• Errors bubble up → Notify component → display to user + send to Sentry
• CI pipeline builds Docker image → pushes to registry → deployed via GitHub Actions using app.yaml to GCP
c. Architectural patterns & design principles
• Micro-frontend: independent sub-app bundles hosted & welded by a shell
• Redux single-store pattern
• Atomic design for shared UI components
• PRPL pattern (future): initial push, render, pre-cache, lazy-load
d. Key technologies & frameworks
• React + Redux
• Webpack (per-app config)
• Cypress for e2e tests
• Docker, NGINX, GCP App Engine (app.yaml)
• GitHub Actions for CI (ci.yaml, cd.yaml)
• Sentry
Detail
• Build/deploy mechanisms (CI/CD, Docker, app.yaml) as separate infrastructure nodes
• Error handling flow (Notify → Sentry)
• Configuration scripts and local-testing tools (Cypress, CI scripts) off to one side as supporting processes