How eathorne2/quickcode-html-designer works
Project type and purpose
• This is a full-stack monolithic web application written in PHP, JavaScript, HTML and CSS.
File structure
• Top-level
• LICENSE, README.md
• quickcodeui_db.sql – database schema for optional MySQL backing store
• app/components
• Custom PHP “component” library, likely used by the back-end to render segment templates
• public/
• index.php – main entry point for the UI
• api.php – AJAX endpoint for dynamic operations (saving, segment listing, palette operations)
• .htaccess – Apache URL rewriting and security rules
• assets/ – CSS, JS and images served statically to the browser
• includes/ – back-end modules that implement page logic: loader, segment injection, login/signup, palette manager, save/load, export
• segments/ – organized library of PHP template files for UI “chunks” (buttons, cards, grids, forms, etc.)
• saved/ – per-user storage of generated HTML & CSS snippets (file system persisted)
• export_templates/ – HTML/JS templates used to bundle or package the finished designs
• public/color_palettes, public/images – static asset stores for palettes & segment artwork
Key technical insights from README
• Single-application designer providing drag-and-drop of HTML “segments.”
• No mention of external microservices or heavy third-party integrations beyond standard LAMP stack.
Capturing essential elements
• Don’t clutter with every single segment file—group under “Segments Library.”
• Separation of static assets vs. dynamic code.
• Make the API boundary explicit: index.php (UI shell) vs. api.php (data & operations).
• File-based storage of user projects as a key persistence mechanism.