How snwatson/ketamine-nightmares works
Main Components
• Repository (Version Control):
– Represent the Git repository as the central source. This contains all the content directories (“admin”, “fex”, “pex”, “pocus”) and supporting files (like index.md, README.md, CNAME).
– Show the organized file tree with separate modules for different types of content: “fex” (core clinical information, classics, summaries, investigations, etc.), “pex” (exam preparation materials, memorisation content, SAQs, videos) and “pocus” (point-of-care ultrasound resources).
• Content Conversion & Processing Pipeline:
– Include a component for the conversion process. The README shows that HTML content produced initially in Microsoft Word is filtered and converted (using grep, GNU parallel, and tidy-html5).
– Represent the processing tools (grep, parallel, tidy) as sub-components or a service that “transforms” files.
• Static Site Hosting / Delivery:
– Show the deployment of the static website (hinted by the CNAME file) – likely hosted on a static hosting service (e.g., GitHub Pages or similar).
– Indicate that the cleaned content is ultimately deployed onto a web server or CDN that serves pages to end users via web browsers.
Relationships & Data Flow
• From the Conversion Pipeline, direct output (converted HTML/ASCII content) into a “Build/Deployment” component.
• Also, you might indicate feedback from user experience (if improvements are made) back to the Repository for updates.
Architectural Patterns & Technologies
• Static website paradigm, where all pages are generated in advance (using a “preprocessing” pipeline) rather than dynamically rendered on each request. This is crucial both in “content maintenance” and “deployment.”
Final Structure
• Next, indicate a “Static Build & Deployment” stage, potentially integrating tools like a static site generator (even if implicitly) or placing files on the hosting platform (hinted at by CNAME).
This detailed approach will help capture all essential architectural elements of the Ketamine Nightmares project while clarifying its static content management, transformation, and delivery workflow.