How 1inmortal/githubpagetest works
Project type and purpose
• This repository is a developer portfolio / multimedia front-end showcase. It bundles dozens of static HTML/CSS/JS “mini-apps” (Blog, Certificados, Evidencias, presentaciones, plus a small React sub-application) along with audio/video assets to demonstrate futuristic HUD-style interfaces, dynamic data visuals, and immersive UX/sonic effects.
File structure
• Top-level directories (“Audio”, “Blog”, “Certificados”, “Evidencias”, “presentacion”, “react-ui-login”, “src”) each host standalone front-end demos or sub-apps.
• Root has package.json/lock, a compose.yaml, GitHub Actions workflows, Dockerfiles in evidence subfolders, plus index.html and supporting CSS/JS under “src” for the main site.
• CI/CD manifests (.github/workflows/*.yml) indicate automated builds, tests (CodeQL), container image publication, and static deployment.
README for additional insights
• The README is not a technical blueprint but a manifesto describing the developer’s specialization in HUD interfaces, advanced UI/UX, dynamic data visualization, and reactive audio-visual experiences.
• No pre-drawn architecture is provided, so we infer a static-site + CI/CD + containerization pipeline.
Detail is key
• Break the pipeline into as many logical steps (jobs) as needed: CodeQL scan, npm install, webpack build, docker build, docker push, static deploy.
• React sub-app separately if it’s deployed as its own package or route.