How lediofiri/adi-gazi works
1. What this repository is
- This is a static marketing/portfolio website for the furniture business Mobileri Adi Gazi.
- There is no backend, database, or build pipeline; the site runs directly from HTML/CSS/JavaScript files and can be hosted on any static host.
2. Top-level site structure
- The root-level pages form the main public-facing site: index.html, categories.html, produktet.html, about.html, and contact.html.
- These pages provide the primary navigation path: homepage → category overview → product listings → business/about/contact information.
3. Category-based content architecture
- The site is organized around product families stored in dedicated folders: dollape/, Dyer/, kende/, krevate/, kuzhina/, and shkalle/.
- Each folder contains its own index.html plus several detail pages, making each category a self-contained mini-section linked back into the main site.
4. Content hierarchy and browsing flow
- The homepage and category pages act as entry points into the product catalog.
- Users typically move from broad categories to specific product examples through internal links, with detail pages used to show individual items or variants.
5. Shared presentation layer
- style.css is the single global stylesheet for the entire site.
- It controls layout, responsiveness, cards, buttons, spacing, and the visual consistency across both root pages and category subpages.
6. Shared interaction layer
- script.js provides the site’s lightweight client-side behavior.
- The README indicates it handles the mobile navigation menu and scroll/reveal animations, so JavaScript is used only for presentation enhancements rather than application logic.
7. External service dependencies
- Product imagery is mostly served from Cloudinary, so media is hosted externally rather than stored in the repo.
- The contact layer also relies on external platforms: WhatsApp, Instagram, Facebook, and phone links for direct user conversion.
8. Media and promotional content
- The site includes a mix of static images and embedded/linked video content, with videos hosted on YouTube.
- This means the site is a content aggregator and lead-generation front end, not a self-contained media platform.
9. User journeys and conversion points
- The main architectural goal is to move visitors from browsing to contact.
- Conversion is handled through prominent contact affordances: WhatsApp button, phone number, social links, and location details on the contact page and in the site-wide navigation flow.
10. Boundary between shared and category-local assets
- Root pages use shared styling and behavior, while each category folder contains its own localized page set and relative links.
- This separation matters for architecture diagrams: there is one shared site shell, but the catalog content is distributed across category directories.
11. Deployment model
- Because everything is static, deployment is simply file hosting: upload the HTML files, style.css, script.js, and all category folders together.
- The architecture depends on relative linking, so preserving folder/file names is part of the runtime structure.
12. Key diagram takeaway
- The cleanest architecture view is: static content layer (HTML pages) + shared presentation/behavior layer (style.css, script.js) + external media/contact services (Cloudinary, WhatsApp, social platforms, YouTube).
Main entry points: style.css Styles · categories.html Categories · index.html Home · produktet.html Products
Components 22
Public site
Root-level pages that form the main browsing and conversion flow.
- Home · Primary entry page for the furniture brand site.
index.html - Categories · Overview page that routes visitors into product families.
categories.html - Products · Broad product browsing page for the catalog.
produktet.html - About · Business background and company information.
about.html - Contact · Contact and lead-generation page with direct outreach options.
contact.html
Catalog sections
Self-contained category folders with entry pages and product detail pages.
- Dollape · Entry page for wardrobe products.
dollape/index.html - Wardrobe · Representative wardrobe detail page within the dollape section.
dollape/dollap1.html - Dyer · Entry page for door products.
Dyer/index.html - Door detail · Representative door detail page within the Dyer section.
Dyer/dera1.html - Kende · Entry page for window products.
kende/index.html - Window detail · Representative window detail page within the kende section.
kende/kendi1.html - Krevate · Entry page for bed products.
krevate/index.html - Bed detail · Representative bed detail page within the krevate section.
krevate/krevati1.html - Kuzhina · Entry page for kitchen products.
kuzhina/index.html - Kitchen detail · Representative kitchen detail page within the kuzhina section.
kuzhina/kuzhina1.html - Shkalle · Entry page for staircase products.
shkalle/index.html - Stair detail · Representative staircase detail page within the shkalle section.
shkalle/shkalla1.html
Shared layer
Global presentation and lightweight interaction used across the whole site.
External services
Off-repo services for media hosting and contact conversion.
- Cloudinary · External host for most product imagery.
- YouTube · External host for embedded or linked promotional video content.
- Social links · Outbound contact routes such as WhatsApp, Instagram, Facebook, and phone links.
Connections 39
- Home → Categories: browse · Main path from homepage into category browsing.
- Home → Products: browse · Homepage can also lead into the broader product catalog.
- Home → About: learn · Visitors can move from the home page to business information.
- Home → Contact: contact · Primary conversion path from the homepage to contact options.
- Categories → Dollape: open · Category overview routes into the wardrobe section.
- Categories → Dyer: open · Category overview routes into the door section.
- Categories → Kende: open · Category overview routes into the window section.
- Categories → Krevate: open · Category overview routes into the bed section.
- Categories → Kuzhina: open · Category overview routes into the kitchen section.
- Categories → Shkalle: open · Category overview routes into the staircase section.
- Dollape → Wardrobe: view · Category landing pages link to specific product examples.
- Dyer → Door detail: view · Category landing pages link to specific product examples.
- Kende → Window detail: view · Category landing pages link to specific product examples.
- Krevate → Bed detail: view · Category landing pages link to specific product examples.
- Kuzhina → Kitchen detail: view · Category landing pages link to specific product examples.
- Shkalle → Stair detail: view · Category landing pages link to specific product examples.
- Home → Styles: uses · All public pages share the global stylesheet.
- Categories → Styles: uses · Category overview page uses the shared stylesheet.
- Products → Styles: uses · Product hub uses the shared stylesheet.
- About → Styles: uses · About page uses the shared stylesheet.
- Contact → Styles: uses · Contact page uses the shared stylesheet.
- Dollape → Styles: uses · Category sections inherit the shared presentation layer.
- Dyer → Styles: uses · Category sections inherit the shared presentation layer.
- Kende → Styles: uses · Category sections inherit the shared presentation layer.
- Krevate → Styles: uses · Category sections inherit the shared presentation layer.
- Kuzhina → Styles: uses · Category sections inherit the shared presentation layer.
- Shkalle → Styles: uses · Category sections inherit the shared presentation layer.
- Home → Behavior: uses · Client-side enhancements are loaded on the main site pages.
- Categories → Behavior: uses · Client-side enhancements are loaded on shared navigation pages.
- Contact → Social links: routes · Contact page pushes users to direct outreach channels.
- Products → Cloudinary: loads media · Product browsing relies heavily on externally hosted images.
- Wardrobe → Cloudinary: loads media · Product detail pages load images from Cloudinary.
- Door detail → Cloudinary: loads media · Product detail pages load images from Cloudinary.
- Window detail → Cloudinary: loads media · Product detail pages load images from Cloudinary.
- Bed detail → Cloudinary: loads media · Product detail pages load images from Cloudinary.
- Kitchen detail → Cloudinary: loads media · Product detail pages load images from Cloudinary.
- Stair detail → Cloudinary: loads media · Product detail pages load images from Cloudinary.
- Home → YouTube: embeds · Promotional media may be linked or embedded from YouTube.
- Products → YouTube: embeds · Catalog pages may include video content for promotion.