How antony-beep/holding-reynaga works
1. This is a Next.js App Router site, built as a mostly static marketing/real-estate presentation project. There are no API routes, server actions, or database layers in the tree, so the architecture is centered on routed pages, reusable React sections, and file-based content/assets.
2. The top-level route structure lives under src/app. The root src/app/layout.tsx defines the global document shell, while src/app/(main)/layout.tsx wraps the public-facing site chrome for the main pages. The route group keeps the marketing pages under a shared layout without affecting the URL.
3. The home page is assembled from composable section components in src/components/home. These include Hero, ProjectOverview, About, Catalog, VirtualTour, Gallery, Location, LocationMap, FAQ, and DossierForm. The page itself is therefore a composition layer; the business content is split into presentational blocks rather than embedded in one monolith.
4. Property/apartment content is data-driven from src/data/apartments.ts. That data appears to feed the dynamic apartment detail route at src/app/(main)/departamentos/[tipo]/page.tsx and likely also the catalog and 360-tour links. The architecture implies a single source of truth for apartment types, with pages derived from the dataset by route parameter.
5. The 360 experience is isolated into its own route family under src/app/vision360/[type]/page.tsx and a dedicated viewer component at src/components/vision360/PannellumViewer.tsx. The presence of src/types/pannellum.d.ts shows an external panorama library integration, and the viewer is likely browser-only because it depends on DOM/WebGL-style behavior.
6. Several global UI/utility components are shared across pages in src/components/global: Header, Footer, CookieConsent, WhatsAppFAB, Preloader, StructuredData, and ClientOnlyComponents. This creates a clear boundary between site shell concerns, compliance/consent, marketing contact affordances, and browser-specific rendering.
7. ClientOnlyComponents is an important architectural seam. It suggests some components must not render on the server, probably because they depend on browser APIs, third-party widgets, or dynamic media behavior. That boundary keeps the SSR/App Router structure stable while still supporting interactive features.
8. The content and media layer is asset-heavy and file-based. public/images, public/videos, and public/docs/dosier_informativo.pdf hold the visual collateral, while the apartment-type folders under images and videos indicate each unit type has its own media set. This repo is therefore designed around large static media delivery rather than dynamic content generation.
9. src/app/terminos-y-condiciones/page.tsx is a separate static compliance page. Combined with cookie consent and structured data, this indicates the site has deliberate legal/SEO/marketing support rather than only brochure content.
10. Global styling is handled through src/app/globals.css plus Next.js configuration files (postcss.config.mjs, eslint.config.mjs, next.config.ts). The README also shows the app uses next/font to load Geist, so typography and global presentation are configured centrally rather than per-page.
11. The likely data flow is: route parameter or page load → page component under src/app → content pulled from src/data/apartments.ts and/or static assets in public → section components render the page → global shell components add navigation, legal prompts, WhatsApp contact, and structured metadata. The 360 pages add one extra client-side viewer layer on top of that flow.
12. Deployment/runtime-wise, this is a standard Next.js site intended for Vercel-like hosting, with static assets and server-rendered pages optimized by the framework. The architecture is best understood as a content-rich, route-driven frontend with isolated interactive modules and no visible backend service boundary.
Main entry points: app/layout.tsx Root layout · page.tsx Home page · (main)/layout.tsx Main layout · ClientOnlyComponents.tsx Client-only
Components 33
App routes
Next.js App Router entrypoints and route layouts.
- Root layout · Global document shell for the App Router.
src/app/layout.tsx - Main layout · Shared chrome for public marketing pages.
src/app/(main)/layout.tsx - Home page · Main landing page assembled from section components.
src/app/(main)/page.tsx - Apartment page · Apartment detail page driven by the tipo route param.
src/app/(main)/departamentos/[tipo]/page.tsx - Terms page · Legal/compliance page for site terms.
src/app/(main)/terminos-y-condiciones/page.tsx - 360 page · Dedicated route family for panorama experiences.
src/app/vision360/[type]/page.tsx
React components
Reusable presentation, shell, and interactive UI pieces.
- Header · Primary navigation and top-level branding.
src/components/global/Header.tsx - Footer · Bottom-of-page navigation and contact area.
src/components/global/Footer.tsx - Cookie consent · Consent prompt and tracking preference boundary.
src/components/global/CookieConsent.tsx - WhatsApp FAB · Floating contact affordance for messaging.
src/components/global/WhatsAppFAB.tsx - Client-only · Wrapper for browser-only components and widgets.
src/components/global/ClientOnlyComponents.tsx - Structured data · Injects metadata/schema for search visibility.
src/components/global/StructuredData.tsx - Preloader · Initial loading/transition state for the site.
src/components/global/Preloader.tsx - Hero · Top-fold marketing section for the home page.
src/components/home/Hero.tsx - Overview · Project summary and positioning content.
src/components/home/ProjectOverview.tsx - About · Background and descriptive project content.
src/components/home/About.tsx - Catalog · Apartment listing and entry point to unit details.
src/components/home/Catalog.tsx - Virtual tour · Entry point to immersive 360 viewing.
src/components/home/VirtualTour.tsx - Gallery · Image showcase for project and unit visuals.
src/components/home/Gallery.tsx - Location · Neighborhood and access information.
src/components/home/Location.tsx - Location map · Embedded map or map-style location view.
src/components/home/LocationMap.tsx - FAQ · Frequently asked questions and answers.
src/components/home/FAQ.tsx - Dossier form · Brochure or document request capture.
src/components/home/DossierForm.tsx - 360 viewer · Browser-side panorama renderer for the 360 route.
src/components/vision360/PannellumViewer.tsx
Content and media
Apartment data and static assets used by the site.
- Apartments data · Single source of truth for apartment types and details.
src/data/apartments.ts - Images · Project imagery, gallery media, and unit visuals.
public/images - Videos · Rendered video assets for apartments and promotion.
public/videos - Dossier PDF · Informational brochure downloaded by users.
public/docs/dosier_informativo.pdf
Project config
Build, styling, and type configuration.
- Global styles · Application-wide CSS foundation.
src/app/globals.css - Next config · Next.js build/runtime settings.
next.config.ts - PostCSS config · CSS processing configuration.
postcss.config.mjs - ESLint config · Code quality and linting rules.
eslint.config.mjs - Pannellum types · Type definitions for the panorama library integration.
src/types/pannellum.d.ts
Connections 37
- Root layout → Main layout: wraps · The root shell delegates public site chrome to the main route group.
- Main layout → Home page: renders · Shared layout frames the landing page.
- Main layout → Apartment page: frames · Shared layout also wraps apartment detail pages.
- Main layout → Terms page: frames · Shared layout also wraps the compliance page.
- Root layout → 360 page: enables · Root App Router layout supports the separate 360 route family.
- Home page → Hero: composes · Home page is assembled from reusable sections.
- Home page → Overview: composes · Home page is assembled from reusable sections.
- Home page → About: composes · Home page is assembled from reusable sections.
- Home page → Catalog: composes · Home page is assembled from reusable sections.
- Home page → Virtual tour: composes · Home page is assembled from reusable sections.
- Home page → Gallery: composes · Home page is assembled from reusable sections.
- Home page → Location: composes · Home page is assembled from reusable sections.
- Home page → Location map: composes · Home page is assembled from reusable sections.
- Home page → FAQ: composes · Home page is assembled from reusable sections.
- Home page → Dossier form: composes · Home page is assembled from reusable sections.
- Apartment page → Apartments data: reads · Apartment details are derived from the shared data model.
- Catalog → Apartments data: lists · Catalog is driven by the same apartment content source.
- Virtual tour → 360 page: links · Virtual tour section points into the 360 route family.
- 360 page → 360 viewer: uses · 360 route renders the dedicated panorama viewer.
- 360 viewer → Pannellum types: types · Viewer relies on the external panorama library typings.
- Root layout → Header: includes · Global shell includes shared header chrome.
- Root layout → Footer: includes · Global shell includes shared footer chrome.
- Root layout → Cookie consent: includes · Global shell includes consent handling.
- Root layout → WhatsApp FAB: includes · Global shell includes contact CTA affordance.
- Root layout → Structured data: includes · Global shell injects SEO structured metadata.
- Root layout → Preloader: includes · Global shell manages initial loading behavior.
- Root layout → Client-only: gates · Browser-only pieces are isolated behind a client boundary.
- Client-only → 360 viewer: hosts · Panorama viewer is a browser-only component.
- Client-only → Cookie consent: hosts · Some interactive consent behavior may be client-only.
- Client-only → WhatsApp FAB: hosts · Floating contact UI may depend on browser APIs.
- Root layout → Global styles: loads · Global document shell loads site-wide styles.
- Root layout → Next config: depends on · Framework behavior is shaped by Next.js config.
- Root layout → PostCSS config: depends on · Styling pipeline is configured centrally.
- Root layout → ESLint config: depends on · Development workflow uses shared lint rules.
- Home page → Images: uses · Sections render static marketing and gallery imagery.
- Home page → Videos: uses · Sections can display promotional apartment videos.
- Dossier form → Dossier PDF: downloads · Lead form connects to the brochure PDF asset.