darenprince-author

📁 File Structure Cheatsheet

Last updated: 2025-02-14

Use this as a quick reference when navigating the repository or onboarding collaborators.

.
├── assets/                     # Compiled CSS, JS, imagery, icons, press kit
│   ├── styles.css              # Generated via Sass (`scss/styles.scss`)
│   └── image-manifest.json     # Output from `scripts/generate-image-manifest.js` (repo-wide imagery index)
├── components/                 # HTML demos + partials for marketing and dashboard UI
├── docs/                       # Project documentation (build pipeline, migration plan, style guides)
├── js/                         # Browser modules (nav, auth placeholders, dashboards, utilities)
│   ├── auth-service.js         # Placeholder interface for future authentication provider
│   ├── auth.js                 # Login/signup UI logic + migration messaging
│   ├── auth-guard.js           # Displays downtime overlays on gated pages
│   ├── dashboard.js            # Member dashboard placeholder (disables uploads, shows notices)
│   ├── admin-user-console.js   # Admin console placeholder (renders migration status)
│   ├── profile-dropdown.js     # Avatar dropdown + login redirect while auth is offline
│   ├── ui.js                   # Toast/progress helpers exposed globally
│   └── ...                     # Book demos, hero controllers, password strength helpers
├── pages/                      # Standalone HTML shells (e.g., search results)
├── scss/                       # Modular Sass (tokens, base, layout, components, utilities)
├── scripts/                    # Node utilities (icon generation, image manifest, setup scripts)
├── src/                        # Search worker + Minisearch build scripts
├── tests/                      # Vitest suites (public site smoke checks, OG image automation)
└── package.json                # npm scripts + dependencies

Key directories & files

/js/

/scripts/

/docs/

/tests/

Generated artifacts

Reality Check: With the data platform offline, no scripts should attempt to read or write runtime credentials. Keep .env limited to analytics keys and automation endpoints until the new provider is ready.