How juserdev/personal-landing-page works
Project type and purpose
• This is a static, front-end “landing page” website hosted on GitHub Pages. Its purpose is to showcase completed Frontend Mentor challenges in organized sections (HTML/CSS challenges, JavaScript/TypeScript challenges, intermediate challenges). There is no server-side component or database; all content is delivered as static assets.
File structure
• Top-level assets
• index.html, style.css (global styles), code.ts/js, tsconfig.json, package.json → root landing page and TS build config
• node_modules/ and package.json → local TS/JS tooling (TypeScript compiler, possible bundler)
• Sections
• /retos-html/ → HTML & CSS challenge gallery (app.ts/js + data.json drive dynamic menu)
• /retos-intermedios/ → intermediate challenge gallery (app.ts/js + intermediate.json)
• /retos-js-ts/ → JavaScript & TypeScript challenge gallery (app.ts/js + data.json)
• Inside each section: HTML pages, CSS (Style.css), code.js / code.ts, JSON data, design and images subfolders.
README for additional insights
• Confirms static nature, responsive design, modular folder structure, and use of JSON to drive page content dynamically via client-side scripts.
Detail and thoroughness
• JSON data flow into the client-side scripts
• One-way pipeline from source files to end user
• Don’t over-optimize: more components (workstation, build, repo, host, browser, data) make it clearer how the static site is produced and consumed.