How enric1994/resume works
Project type and purpose
• This is a static, front-end-only “3D resume” website built with HTML/CSS/JavaScript and WebGL (via glTF models).
• Users browse to index.html (locally via python3 –m http.server or published on GitHub Pages) to view a sequence of interactive 3D scenes (your resume), each backed by a .glb model.
• Blender is used offline to author .blend source files, exported to glTF (.glb), optionally compressed with the Draco encoder.
File-structure analysis
• Top-level files:
• index.html – the single-page web app shell
• compress_models.sh – helper script to run the Cesium glTF-pipeline/Draco encoder
• models/ – compiled .glb assets + Draco decoder (draco_decoder.wasm/draco_wasm_wrapper.js)
• scenes/ – original Blender .blend files (source)
• No backend code, no database—purely static assets + client-side rendering.
Key README insights
• Flow: author in Blender → export GLTF → (optional) compress via compress_models.sh → host on GitHub Pages or local simple HTTP server → browser fetches index.html + assets → renders WebGL scenes.
• Dependencies: standard HTML/CSS/JS, Blender for modeling, glTF-pipeline (Draco).
Components
a. Offline/authoring stage
• Blender (produce .blend)
• glTF Export module → raw .glb files
• compress_models.sh + glTF-pipeline/Draco → optimized .glb + draco_decoder.wasm + draco_wasm_wrapper.js
b. Deployment/hosting stage
• GitHub Pages or any static HTTP server (e.g. python3 –m http.server)
• Repository holding index.html, models/, static assets
c. Client/runtime stage
• User’s Browser (WebGL context)
• index.html + JS code (initializes Three.js or native glTF loader)
• WebAssembly module (draco_decoder.wasm) + JS wrapper
• Fetches .glb assets from models/
• Renders sequential 3D scenes (resume sections)
Relationships and interactions
• Authoring pipeline: Blender → glTF export → compress_models.sh → commit to Git repo → deploy to GitHub Pages
• At runtime: Browser → HTTP GET index.html → parse and load JS modules → fetch & decode .glb via Draco → WebGL render → user interaction
Architectural patterns and design principles
• Pure static-site architecture: no runtime server logic.
• Separation of concerns: offline model creation vs. client runtime display.
• Progressive enhancement: uncompressed .glb fallback if Draco loader unavailable.
• Modular assets: each resume section is a separate .glb.
Technologies and frameworks
• Blender (model authoring)
• glTF 2.0 (.glb)
• glTF-pipeline (Draco) for compression
• WebAssembly (draco_decoder.wasm) + JS wrapper
• Three.js or native WebGL glTF loader (implicit in index.html)
• Git/GitHub Pages for hosting
• Python HTTP server (for local dev)
Elements
• Labels on each component (e.g., “compress_models.sh + glTF-pipeline”)
Final advice
• Both offline/authoring and online/runtime aspects.
• Don’t over‐engineer—split the workflow into as many discrete, meaningful steps as needed for clarity.
• User’s journey (from opening index.html to viewing each 3D scene) is obvious.
• Static nature of hosting and WebAssembly asset decoding.