How princepal/uiuxportfolio works
Project type and purpose
• This is a static-style portfolio website (UI/UX designer portfolio) implemented with PHP templates, HTML5, CSS3, and JavaScript.
• Purpose: showcase designer’s work (parallax scrolling, dark/light mode, project pages, about me, book landing).
File structure
• Top-level PHP pages: index.php, about-type pages (me.php, contact.php, privacy-policy.php, refund-policy.php, etc.).
• Common includes: header.php, footer.php.
• Assets folder:
• css/style.css (global styles)
• js/main.js (parallax effects, dark/light toggle)
• fonts, images, FontAwesome library.
• projects/ and services/ directories host specific project detail pages.
• .htaccess and 404.php for URL rewriting and error handling.
README for technical stack
• Frontend: HTML5, CSS3 (responsive, parallax design), JavaScript (dark/light mode, smooth scrolling).
• No database or server-side business logic beyond PHP includes.
• Fully responsive; assets served statically.
Main components & their interactions
a. Components
• Client (Browser)
• CDN or Web Server (Apache/Nginx) + PHP engine
• PHP Templates (index.php, header.php, footer.php, page-specific PHP)
• Static Assets (CSS, JS, fonts, images, FontAwesome)
• External Services (YouTube embed, LinkedIn link)
b. Relationships & Data Flow
1. User’s browser sends HTTP(S) request → Web Server
2. Server resolves URL via .htaccess → invokes PHP template
3. PHP includes header/footer + page content → compiles HTML
4. Server responds with HTML
5. Browser requests static assets (CSS/JS/fonts/images) in parallel
6. JavaScript executes client-side parallax & theme toggling
7. External embeds (YouTube) loaded via their API/iframe
c. Architectural patterns & principles
• Template include pattern (header/footer reuse)
• Static-first architecture (minimal server logic)
• Client-side enhancement (progressive enhancement for parallax & dark mode)
d. Key technologies
• PHP (templating), .htaccess (routing)
• HTML5/CSS3 (responsive design, parallax effect)
• JavaScript (interaction, theme detection)
• FontAwesome (iconography)
Elements
• Clear labels: Browser, Web Server (Apache+PHP), PHP Templates, Static Assets, External Services.
• Browser → Server (HTTP GET page)
• Server → Browser (HTML)
• Browser → Server (asset requests)
• Browser → External (YouTube iframe)
• Rectangles for server components (PHP engine, file system)
• Clouds for external services
• Parallelograms for client browser
Detailed breakdown to capture essential elements
• Files logically: “Templates” folder (header.php, footer.php, index.php, me.php, etc.).
• “Assets” bucket with sub-buckets (CSS, JS, images, fonts, FontAwesome).
• .htaccess as the routing entry point, 404.php as error handler.
• Call out dark/light theme detection in main.js.
• Responsive breakpoints in style.css.
• External embed calls (YouTube thumbnail → iframe load).