GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — GitHub - certforge/certprep.dev

BranchesTags
Open more actions menu

Latest commit

 

History

4 Commits
4 Commits

Folders and files

NameName
Last commit message
Last commit date
.github/workflows
.github/workflows
 
 
.husky
.husky
 
 
public
public
 
 
src
src
 
 
tests
tests
 
 
.gitignore
.gitignore
 
 
README.md
README.md
 
 
astro.config.mjs
astro.config.mjs
 
 
package-lock.json
package-lock.json
 
 
package.json
package.json
 
 
tsconfig.json
tsconfig.json
 
 

Repository files navigation

CertPrep Static Site

A lightweight Astro site that showcases every CertPrep certification domain, links to the open-source prep repositories, and highlights the hands-on demos that live inside each repo. The site is optimized for Cloudflare Pages and enforces tests locally and in CI before deployments run.

Tech Stack

  • Astro for the static site
  • TypeScript modules for study-track data
  • Vitest for data integrity tests
  • Husky git hooks to block commits when tests fail
  • GitHub Actions workflow for Cloudflare Pages deployments

Getting Started

npm install
npm run dev

The dev server runs on http://localhost:4321 by default.

Tests

All commits must pass the Vitest suite (a Husky pre-commit hook enforces this).

npm test        # one-off
npm run test:watch

The tests verify that each track’s domain weights total 100%, every repo link resolves to the CertPrep org, and that each track exposes labs/scripts for the website to promote.

Deployment

The workflow in .github/workflows/deploy.yml handles:

  1. npm ci
  2. npm test
  3. npm run build
  4. Upload to Cloudflare Pages via cloudflare/pages-action

Add the following GitHub Actions secrets before triggering the workflow:

  • CLOUDFLARE_API_TOKEN — Pages write token scoped to the target account/project
  • CLOUDFLARE_ACCOUNT_ID

Update projectName inside the workflow if you change the Pages project slug. The build output directory remains dist/, which is what the action publishes.

Project Structure

├── public/                  # Static assets (logos, favicons)
├── src/
│   ├── components/          # Reusable UI blocks (track cards, domains)
│   ├── data/                # Track/domain metadata used for rendering + tests
│   ├── layouts/             # Site shell
│   ├── pages/               # Astro pages
│   └── styles/              # Global CSS
├── tests/                   # Vitest suites
└── .husky/                  # Git hooks (pre-commit triggers npm test)

Contributing

  1. Create a branch: git checkout -b feat/add-track.
  2. Update the relevant data in src/data/.
  3. Run npm test && npm run lint.
  4. Commit (the pre-commit hook will re-run npm test).
  5. Open a PR describing the update and referencing the source repo.

About

No description, website, or topics provided.

Resources

Readme

Contributing

Contributing
Activity
Custom properties

Stars

1 star

Watchers

0 watching

Forks

0 forks
Report repository

Releases

Packages

Used by

Contributors

Languages

You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.