How enriqueiborra/asgbd works
1. This repository is not an application backend or library; it is a course content repository for the ASGBD module, centered on database administration teaching materials and a published static documentation site.
2. The main content layer is the set of PDF units at the repository root (UD1–UD6 and PLALOE_EXTR). These files are the canonical learning materials: installation, configuration, users and permissions, automation, optimization, and availability. Each unit also has a CriterisRA*.txt file describing assessment criteria for that learning outcome.
3. The docs/ directory is the delivery layer. It contains prebuilt HTML pages, CSS, images, fonts, sitemap, and JSON question banks. This is the part that is meant to be served directly, most likely through GitHub Pages, as indicated by the README link to the public site.
4. The site structure in docs/ maps the curriculum into navigable web pages: installation, configuration, SQL review, users/privileges, security, automation, optimization, availability, and ER review. There are both normal and _p variants of several pages, which suggests parallel versions of the same content, likely for alternate views or printer-friendly/pedagogical variants.
5. The quiz/assessment subsystem lives under docs/preguntes/. The JSON files (preguntes11.json, preguntes21.json, preguntes31.json, etc.) appear to hold structured question sets aligned to units and outcomes. These files are a data source for interactive exercises or self-assessment in the static site.
6. The visual presentation subsystem is fully static: docs/estilsindex.css, docs/estilsunitats.css, image assets, and font assets control the site layout and branding. There is no evidence of server-side rendering or a runtime framework; browser-side HTML/CSS is the primary delivery mechanism.
7. The repository also includes supporting “source of truth” documents in PDF form, such as installation guides, Oracle setup, Docker deployment notes, and summaries. These are instructional artifacts rather than executable code, but they define the content that the static site exposes.
8. The external dependencies that matter architecturally are minimal: a browser to read the static site, GitHub Pages as the likely hosting mechanism, and an optional Google Translate entry point referenced in the README for multilingual viewing. No database, API server, or build service is visible in the tree.
9. The data flow is essentially one-way: authored course materials and question banks are published into docs/, then consumed by students through the static website. The PDFs in the unit folders are separate downloadable reference materials that support the same curriculum.
10. Overall, this repository is best diagrammed as a content publishing system with three boundaries: source materials in PDF/TXT form, a static web presentation layer in docs/, and browser-based consumption via a hosted public site. The architecture is documentation-centric, not service-centric.
Main entry points: preguntes Quizzes · index.html Home · UD3 Unit 3 · instalacio-sgbd.html Installation
Components 23
Source materials
Canonical PDFs and assessment criteria at the repository root.
- README · Entry point describing the course site and usage.
README.md - Unit 1 · Installation and environment preparation.
UD1 - Unit 2 · Configuration, SQL review, tablespaces, and tools.
UD2 - Unit 3 · Users, privileges, and security.
UD3 - Unit 4 · Automation and procedural control.
UD4 - Unit 5 · Database optimization and tuning.
UD5 - Unit 6 · Database availability and resilience.
UD6 - Extra pack · Supplementary practice and deployment materials.
PLALOE_EXTR
Static site
Prebuilt documentation site served from docs/.
- Home · Main landing page for the published documentation site.
docs/index.html
Curriculum pages
Primary topic pages exposed in the site.
- Installation · Installation and setup content.
docs/instalacio-sgbd.html - Configuration · Server and database configuration content.
docs/configuracio-sgbd.html - Users · Users and privilege management.
docs/usuaris-privilegis.html - Security · Security mechanisms and controls.
docs/seguretat-mecanismes.html - Automation · Task automation and procedural logic.
docs/automatitzacio-tasques.html - Optimization · Performance and tuning material.
docs/optimitzacio-sgbd.html - Availability · High availability content.
docs/disponibilitat-sgbd.html - Review · SQL and ER review pages.
docs/repas-sql.html
Presentation assets
Styles, images, fonts, and site metadata.
- Stylesheets · Site-wide visual styling for index and unit pages.
docs/estilsindex.css - Media assets · Image and font resources used by the static site.
docs/imgs - Sitemap · Search and navigation metadata for the published site.
docs/sitemap.xml
Question bank
JSON datasets for self-assessment and exercises.
- Quizzes · Structured question sets for unit self-assessment.
docs/preguntes
Consumption
External hosting and browser access boundary.
- Browser · Students read the published site in a web browser.
- GitHub Pages · Static hosting boundary for the documentation site.
Connections 21
- README → Home: points to · README directs readers to the published site.
- Unit 1 → Installation: publishes · Unit 1 content is exposed as installation pages.
- Unit 2 → Configuration: publishes · Unit 2 content is exposed as configuration pages.
- Unit 3 → Users: publishes · Unit 3 content is exposed as user and privilege pages.
- Unit 3 → Security: publishes · Security material is surfaced in the site.
- Unit 4 → Automation: publishes · Unit 4 content is exposed as automation pages.
- Unit 5 → Optimization: publishes · Unit 5 content is exposed as optimization pages.
- Unit 6 → Availability: publishes · Unit 6 content is exposed as availability pages.
- Extra pack → Review: supplements · Extra materials support reviews and applied practice.
- Quizzes → Installation: feeds · Question sets align with the installation curriculum.
- Quizzes → Configuration: feeds · Question sets align with configuration content.
- Quizzes → Users: feeds · Question sets align with users and privileges.
- Quizzes → Automation: feeds · Question sets align with automation content.
- Quizzes → Optimization: feeds · Question sets align with optimization content.
- Quizzes → Availability: feeds · Question sets align with availability content.
- Home → Stylesheets: uses · Landing page uses shared styling.
- Home → Media assets: uses · Landing page pulls media assets.
- Home → Sitemap: indexed by · Site navigation is supported by sitemap metadata.
- Home → Browser: consumed by · Students access the site via browser.
- GitHub Pages → Home: serves · Hosting serves the static site entry point.
- Browser → GitHub Pages: requests · Browsers retrieve the published documentation site.