How user-danio/sabores-de-japon works
Project type and purpose
• This is a purely front-end, static website project (“Sabores de Japón”) built with HTML, CSS, and JavaScript.
• It uses PostHTML (via the .posthtmlrc file and npm scripts) to process templates and assets in src/ and emits a ready-to-serve site in docs/.
File structure
• Top-level:
• package.json / package-lock.json: Node.js dependencies & build scripts
• .posthtmlrc: configuration for the PostHTML templating pipeline
• src/: source templates, styles, components, scripts, and assets
• docs/: the compiled output (HTML, CSS, JS bundles) ready for deployment
• Inside src/:
• assets/images: static image files
• components/: reusable fragments (header, footer, portada/bento) with CSS + HTML templates
• pages/: page-level CSS + HTML (index, categoria, detalle, enlaces)
• js/: page-specific JavaScript (detalle.js, recetas.js)
• styles/: global styles.css
README
• Confirms it is an assignment (“PEC1 de Herramientas HTML y CSS”) and the author
Main components and their relationships
a. Source code (src/)
b. Build pipeline (npm scripts + PostHTML)
c. Output site (docs/)
d. Client (web browser)
e. External services: none
Flow:
src/ ──(PostHTML & npm scripts)──▶ docs/ ──▶ Browser
Key architectural patterns & design principles
• Component-based HTML (header, footer, bento)
• Static site generation (SSG) using PostHTML
• Separation of concerns: “components” vs. “pages” vs. “styles” vs. “scripts”
• Directory-based routing: each page in src/pages/ compiles to docs/pages
Technologies, frameworks, libraries
• Node.js & npm (package.json scripts)
• PostHTML for HTML processing
• Standard CSS & vanilla JavaScript
• No backend or dynamic data layer
What
• Clear labels on each folder/component
• Build & configuration (green gear)
• Output (gray folder)
• Call out key files: .posthtmlrc, package.json, docs/index.html