How jwaitze/jake-personal-website works
Project type and purpose
• Type: Monolithic PHP-based personal website
• Purpose: Presents static and dynamic content (home page, blog with full CRUD, chat, resume, privacy policy), plus integrates CAPTCHA (Securimage) and an IRC chat (unrealircd).
File structure
• Top-level entry points:
– index.php (likely homepage redirect)
– folders for each section: blog/, chat/, home/, login/, privacy-policy/, resume/
• Shared code:
– inc/ contains helper modules (database.php, blog.php, chat.php, functions.php, process_submits.php, etc.), header/footer templates
– _config.php holds DB credentials, _structure.sql defines schema
• Static assets:
– css/, js/, img/
• Third-party modules:
– securimage/ provides CAPTCHA service
– uconn-chat/ likely client or embed for IRC
• Build/deploy:
– robots.txt, sitemap.xml, pgp.txt
README for insights
• Stack: LAMP (Linux, Apache, MySQLi, PHP), HTML5, CSS3, JS
• Features: Blog CRUD, chat via IRC, contact & resume pages
• Setup: DB and user, configure _config.php, import schema, generate password
Main components & interactions
a. User’s Web Browser
– Sends HTTP(S) requests, loads HTML/CSS/JS, interacts via forms/JS
b. Web Server (Apache or equivalent)
– Serves static assets directly (css/, js/, img/)
– Routes requests for .php endpoints to the PHP interpreter
c. PHP Application
– Front controller pattern: each folder’s index.php loads inc/includes.php, renders header/footer, calls section logic (inc/blogpost.php, inc/chat.php, etc.)
– inc/process_submits.php handles form submissions (login, blog create/update/delete, chat posts)
– securimage/ module hooked into forms for CAPTCHA generation & validation
d. MySQL Database
– Stores user accounts, blog posts, comments (if any), chat logs (if stored), site defaults, etc.
e. IRC Server (unrealircd)
– External service; uconn-chat client connects to it for real-time chat
f. External Integrations (optional)
– Social links, analytics (statcounter.js), robots.txt for search engines
Architectural patterns & design principles
• Monolith with module-based organization: inc/ holds reusable code, each feature in its own folder
• Separation of concerns: templates (header/footer), business logic (inc/*.php), data access (database.php)
• Client-server: JS enhances UX (AreYouSureYouWantToLeave.js, CanvasRenderer.js) but all data operations go through PHP back end
• Security: CAPTCHA via securimage/, login checks via inc/check_login.php
Detailed call-outs
• Inc/includes.php as the common bootstrap for all pages
• Static vs. dynamic content paths
• Where configuration (_config.php) and schema (_structure.sql) fit