How casparwylie/cascii-core works
File structure
• Top-level files:
• cascii.html – the entire application (HTML, CSS, and JS)
• README.md – description, feature list, usage
• .prettierrc, .gitattributes – formatting/git config
• TODO – rough notes
• No separate frontend/backend folders: everything runs in the browser.
• No build or deployment scripts: open cascii.html directly.
README for additional insights
• Managers: EventManager, LayerManager, CharManager, GroupManager, ModeMaster
• CanvasCom: the rendering engine (“Pixels!”)
• Layer classes: SquareLayer, CircleLayer, DiamondLayer, BaseLineLayer, SwitchLineLayer, StepLineLayer, FreeLineLayer, FreeLayer, TableLayer
• Features: selection, grouping, history, import/export, themes, auto-save localStorage
• External integration: optional server for short links and user accounts.
Essential details
• Make each manager and layer type explicit—this illustrates the core extensibility of the tool.
• Data flow from user input through rendering and persistence.
• Clean separation: no build tools, all logic embedded in cascii.html.
• A note on optional server integration, even though it’s not in this repo.