How samaniegolouie/playgroundcode works
Project type and purpose
• This is essentially a static “playground” website (playgroundcode.github.io) for front-end experiments (HTML/JS demos) with a small number of server-side PHP prototypes (e.g. apiprototype.php) and test data (dummyapi.json, test.sql). There is no formal framework, it’s a collection of standalone demo pages and a “build” folder that packages PDFMake (JS PDF generator) and its fonts for use in the browser.
File structure
• Top level: dozens of .html demo pages (drag-and-drop examples, tables, QR code page, etc.), two .php API prototypes, a SQL dump, and dummy JSON.
• “build/”: JavaScript library pdfmake.js, its source map, vfs_fonts.js, and font definitions under build/fonts.
• “img/”: static images/logos.
• “.vscode/”: IDE configuration.
• No package.json or server framework directory—this is static content plus ad-hoc PHP scripts.
README insights
• The README only contains a Git cheat-sheet, no architectural notes. We must infer that content is served statically (likely via GitHub Pages) and the PHP files must run on a separate PHP-capable host for the API prototypes.