How kel-hendros/v20-character-sheets works
Project type and purpose
• This is a single-page, front-end–only web application: a static Vampire V20 RPG character sheet.
• There is no backend or database—everything runs in the browser.
File structure
• index.html: the root HTML document that lays out the sheet.
• style light.css and style dark.css: two theme files for light/dark mode styling.
• script.js: application logic (e.g., handling user input, toggling themes, calculating derived stats).
• fonts/ and images/: static asset directories supporting UI presentation.
• README.md: describes purpose and provenance (CodePen pen).
Extract insights from the README
• Confirms this is a CodePen export for a character sheet UI.
• No server, no external APIs—just client-side rendering and interactivity.
a. Main components
• Browser UI Container
– HTML Renderer (index.html)
– CSS Engine (style light.css + style dark.css)
– JavaScript Engine (script.js)
• Static Asset Store
– fonts/
– images/
b. Relationships & interactions
• Browser loads index.html → pulls in CSS and JS.
• JS attaches event handlers to HTML elements (e.g., input fields, buttons).
• User actions (e.g., changing a stat) → JS updates the DOM → CSS reflows styling.
• Theme toggle → JS switches between light.css and dark.css.
• Fonts/images referenced by HTML/CSS are fetched from their directories.
c. Architectural patterns & design principles
• Separation of concerns: HTML for structure, CSS for appearance, JS for behavior.
• Asset modularity: fonts/ and images/ are isolated.
• Theme‐switching strategy: dynamic stylesheet swapping.
d. Relevant technologies
• HTML5
• CSS3 (two theme files)
• Vanilla JavaScript (ES6+)
• Browser environment (no frameworks)
Additional guidance
• Don’t add imaginary backend or database elements—keep it faithful to the static, in-browser architecture.