jfeelgoodofficial/tbosw

1. Repository purpose

- This is a static marketing microsite for *The Book of Shadow Work* by J. Feelgood.

- The architecture is intentionally simple: one primary landing page, one supporting “learn more” page, and a few site-level metadata files for hosting and discovery.

2. Core runtime model

- There is no backend, database, API layer, or build pipeline.

- The site runs entirely in the browser as plain HTML/CSS/JavaScript, making the deployment model a flat static host or CDN.

3. Primary entry point

- index.html is the main product page and the center of the architecture.

- It contains the full promotional experience: hero, book explanation, method preview, character sections, sample pages, disclaimer, and final call to action.

- The page appears to be designed as a single-scroll narrative rather than a multi-page application.

4. Supporting content page

- TBOSW-Learn-More.html is a separate extended page for the “Dream Therapy Method.”

- This is a secondary content boundary: the main landing page drives attention and conversion, while the learn-more page gives deeper explanatory material.

- The repo tree shows it as a standalone HTML file rather than a routed view, so navigation is likely plain link-based.

5. Interactive presentation layer

- The landing page uses browser-side interactions for engagement:

- a 7-step swipeable carousel for the method section

- drag-scroll for character cards

- lightbox-style previews for sample pages

- These are UI-only behaviors; they do not depend on server state or persistent storage.

6. Content and conversion flow

- The main user journey is:

- land on the hero

- absorb summary/content sections

- optionally open the learn-more page

- click out to the Amazon purchase link

- The external commerce boundary is important: the repo itself does not sell the book; it routes users to Amazon for the actual transaction.

7. Visual assets and presentation strategy

- The README indicates the design relies heavily on CSS-generated styling, including a mock book cover.

- There are also placeholders for optional image assets if the author later swaps in real cover art or character illustrations.

- This suggests the repo is optimized for zero-dependency visual presentation rather than asset-heavy delivery.

8. SEO and site hosting support

- sitemap.xml and robots.txt support search engine crawling and indexing.

- llms.txt suggests the site also exposes content in a format intended for LLM consumption or discovery.

- CNAME indicates the site is meant to be served under the custom domain tbosw.jfeelgood.com.

9. Deployment boundary

- The project is explicitly designed for static hosting such as Netlify, Vercel, or GitHub Pages.

- Because there is no server code, the deployment boundary is simply: repository files → static host → browser.

10. Technology footprint

- The only required technologies are:

- HTML for structure

- CSS for layout and branding

- JavaScript for small UI interactions

- Google Fonts are loaded externally for typography, but otherwise the site has no material third-party runtime dependencies.

11. Operational implications

- There is no persistence, authentication, analytics pipeline, CMS, or admin surface in the repository.

- Content updates are likely handled by editing static files directly and redeploying.

- The architecture is therefore low-complexity and low-risk, with most changes concentrated in index.html.

12. How to diagram it

- A good architecture diagram would show:

- Browser client

- Static host/CDN

- Primary HTML landing page

- Secondary learn-more HTML page

- External Amazon destination

- SEO/discovery files (robots.txt, sitemap.xml, llms.txt)

- The key relationship is that the site is a static content funnel: informational pages on the repo, outbound conversion to Amazon.