How lojinhadosautistas/web works
1. This repository is a mostly static, multi-page web platform rather than a single app. The architecture is organized as many HTML entry points grouped by domain, with local CSS/JS assets providing behavior and styling.
2. The top-level “rede” area is the main product surface for the Autistas.net ecosystem. It contains the central hub, login pages, documents, calendar, conceptual structure pages, maps/mind-maps, and the core “oraculo”, “atlas”, “prisma”, “ram”, and “memo” experiences.
3. Shared cross-cutting code lives in reusable front-end files such as rede/js/*, rede/components/*, and top-level assets/js / assets/css. These appear to provide common layout, header/sidebar composition, global styles, auth handling, role logic, and page-level behavior reused across many pages.
4. Authentication and access control are an important boundary. The presence of rede/js/firebase.js, auth-login.js, auth-hub.js, and roles.js indicates that some pages gate content based on login state and user roles, with Firebase as the external identity/data service.
5. Content is heavily document- and media-driven. PDFs, HTML fragments, audio files, images, and manifests are stored alongside the pages, especially under rede/acervo, rede/atlas, rede/atipicos, rede/fabularium, and rede/oraculo. The app is clearly meant to curate and present knowledge artifacts, not just interactive UI.
6. The rede/acervo subtree acts like a content repository/knowledge archive. It includes a manifest, fragment HTML partials, includes scripts, packaged HTML bundles, and many PDF “dossiê” / “relatório” files, suggesting a modular publication layer that can be assembled into different views.
7. The oraculo subsystem is a specialized analytical/simulation area. It has many versioned dashboard, simulator, and atlas pages plus a suite of numbered biblioteca*.js files, indicating a reusable library layer powering multiple visualizations or workflows.
8. The atlas and livraria areas are separate content products with their own CSS/JS and media. atlas includes multiple versioned variants and companion audio/docs, while livraria provides book-oriented pages and supporting styles, implying distinct user journeys within the same platform.
9. There is a small server-side boundary in rede/backend with a Node-style package.json and server.js. This is likely the only backend service in the repo and probably supports serving or API needs for the otherwise static front-end platform.
10. Several subtrees are clearly adjacent product lines or branded microsites, not just feature folders: rede-dev/terrabrasil, rede-dev/icaro, rede/atipicos, rede/fabularium, rede/oraculo, and jogos / eventos. Each has its own HTML entry points and, in some cases, dedicated CSS/JS/media, so the diagram should show them as semi-independent modules sharing a common design/identity layer.
11. Versioning is mostly file-level rather than package-level. The many v1/v2/v3 HTML pages, “old” CSS files, and alternate copies of the same screens show iterative evolution and parallel variants rather than a strict component framework.
12. Deployment appears to be static hosting oriented, reinforced by CNAME at the root. That means most runtime behavior is client-side, with content and navigation assembled from local files and a few external services or backend endpoints where needed.
Main entry points: documentos.html Core pages · css Global CSS · hub.html Rede hub · js Auth layer
Components 21
Shared shell
Common front-end assets and reusable UI/auth code shared across many pages.
- Global JS · Top-level JavaScript reused across hub/login/page behaviors.
assets/js - Global CSS · Top-level styles and legacy variants for the platform shell.
assets/css - Components · Reusable header, sidebar, and assembly helpers.
rede/components - Auth layer · Login, hub auth, Firebase wiring, and role checks.
rede/js
REDE core
Main product surface for navigation, documents, maps, calendar, and account-gated pages.
- Rede hub · Primary landing and navigation surface for the REDE ecosystem.
rede/hub.html - Login pages · Entry points for authenticated access and special login flows.
rede/login.html - Core pages · Main REDE pages for documents, structure, maps, calendar, memo, and related hubs.
rede/documentos.html - Maps layer · Map and mind-map entry points that organize the platform conceptually.
rede/mapa.html - Prisma · Focused REDE area for situational prism workflows and related variants.
rede/prisma.html - RAM views · RAM-specific pages and variants tied to the REDE core experience.
rede/ram-global.html - Oraculo · Versioned dashboards, simulations, chat, and reports for the Oraculo subsystem.
rede/oraculo/oraculo-dashboard.html
Content archives
Document- and media-heavy collections used by REDE experiences.
- Acervo · Manifest-driven archive with fragments, packaged views, and PDFs.
rede/acervo - Atlas · Atlas cognitive pages with multiple versions, media, and supporting docs.
rede/atlas - Atipicos · Music-and-image driven content area with audio tracks and lyric support.
rede/atipicos - Fabularium · Story and audio-oriented content collection.
rede/fabularium
Adjacent products
Semi-independent microsites and specialized experiences that share the visual language.
- Livraria · Book-centric pages and supporting styles for reading journeys.
livraria/livraria.html - Jogos · Collection of game-like pages and exercises.
jogos/jogos.html - Eventos · Standalone event pages and microsite content.
eventos/entrepassos.html - Terrabrasil · Separate branded site with its own front-end stack and assets.
rede-dev/terrabrasil/index.html - Icaro · Adjacent product line with many versioned landing and dashboard pages.
rede-dev/icaro/icaro.html
Backend
Small server-side boundary supporting the otherwise static platform.
- Backend API · Small Node-based server boundary for serving or supporting the platform.
rede/backend/server.js
Connections 22
- Global JS → Rede hub: page behavior · Global JavaScript powers hub interactions and shared client behavior.
- Global CSS → Rede hub: theme · Shared styles define the common platform look and feel.
- Components → Core pages: layout · Reusable header/sidebar composition appears across core pages.
- Auth layer → Login pages: gate access · Authentication scripts handle login and special access flows.
- Auth layer → Rede hub: role-aware · Hub logic depends on login state and user roles.
- Auth layer → Core pages: permissions · Core pages use auth and role checks where content is gated.
- Rede hub → Core pages: navigate · The hub routes users into the main REDE pages.
- Core pages → Maps layer: concept map · Core pages connect to map and mind-map views for orientation.
- Core pages → Prisma: specialized view · Prisma is part of the core REDE product surface.
- Core pages → RAM views: workflow · RAM pages are another core workflow branch within REDE.
- Core pages → Oraculo: analysis · Oraculo provides the analytical and simulation side of REDE.
- Acervo → Core pages: feeds content · Archive artifacts are consumed by document and core pages.
- Acervo → Global CSS: shared style · Archive fragments use shared presentation styles.
- Atlas → Core pages: publishes · Atlas is a distinct content area linked from the REDE core.
- Atipicos → Core pages: cross-links · Atipicos acts as a neighboring branded content line.
- Fabularium → Core pages: cross-links · Fabularium is another content-heavy branch adjacent to the core.
- Livraria → Core pages: content journey · Livraria provides a separate book-oriented journey within the platform.
- Jogos → Core pages: interactive content · Games are a companion experience to the main REDE surface.
- Eventos → Core pages: events · Event pages extend the platform with standalone event microsites.
- Terrabrasil → Global CSS: site assets · Terrabrasil has its own front-end stack but shares the static-hosting pattern.
- Icaro → Global CSS: site assets · Icaro is a separate branded product line with versioned pages.
- Backend API → Core pages: serves/supports · Backend service likely supports serving and integration needs for the static front end.