How aniljasel/portfolio works
Project type and purpose
• This is a static front-end portfolio website. There is no custom backend or database—everything runs client-side in the browser.
• Its purpose is to showcase content (images, text, links) with pre-built CSS and JavaScript libraries for animation, sliders, popups, etc.
File structure
• Top‐level “index.html”: the single entry point.
• “css/”: all style definitions and 3rd-party CSS (animate.css, owl.carousel.css, slicknav.css, etc.).
• “js/”: JavaScript libraries (jQuery plugins, smooth scroll, mixitup) plus custom code (app.js, scripts.js).
• “fonts/” and “images/”: static assets consumed by the markup and CSS.
• No server code, no build scripts, no config files—pure static hosting scenario.
README
• README.md simply declares “# portfolio,” confirming a static portfolio site without extra runtime services.
a. Main components to show:
• Client Browser
• Static Asset Host (e.g., GitHub Pages, Netlify, S3/CloudFront)
• Static Assets split into:
• HTML (index.html)
• CSS libraries & custom styles
• JS libraries & custom scripts
• Images
• Fonts
• External services (optional), such as:
• Analytics (e.g., Google Analytics)
• Contact‐form API (if any)
• CDN endpoints for libraries
b. Relationships and interactions:
• Browser → HTTP GET index.html
• index.html → Browser loads CSS, JS, fonts, images from the same host or CDN
• JS executes in the browser, manipulating the DOM, invoking 3rd-party plugins
• (Optional) JS may send events to analytics or call an external contact‐form endpoint
c. Architectural patterns and design principles:
• Client-side rendering: no server logic beyond asset delivery
• Modular asset organization: grouping CSS, JS, fonts, images into separate folders
• Progressive enhancement: use of libraries to add UI effects without breaking core content
d. Key technologies/frameworks:
• HTML5, CSS3, JavaScript (ES5/ES6)
• jQuery + plugins (mixItUp, slicknav, magnific-popup, etc.)
• CSS animation libs (animate.css, magic-mouse.css)
• Carousel & slider libs (Owl Carousel)
Capturing essential elements
• Don’t overcomplicate—focus on the static delivery model and the asset types.
• dependencies: index.html depends on both CSS and JS, which in turn may depend on fonts and images.