Skip to content

About

my index page for github pages

Resources

Stars

1 star

Watchers

0 watching

Forks

Latest commit

 

History

262 Commits

Folders and files

Repository files navigation

GitHub Pages Root

The landing site served at https://rubidus-api.github.io/. It introduces every public project and links each one to its repository, its release page, and a direct download of the newest published build.

The site is generated: src/site.json holds the curated copy, and the build script fills in version numbers, file sizes, and download URLs from the public GitHub release API. Generated HTML is committed because GitHub Pages serves files straight from the repository.

Layout

index.html          generated landing page — the whole site, styles inlined
src/site.json       hand-written manifest: the group tree, project copy, links
scripts/            build, fetch, and link-check scripts
tests/              offline tests for the renderer

Build

scripts/build-site.sh            # fetch fresh release data, then render
scripts/build-site.sh --offline  # re-render from the cached build/releases.json
tests/run-tests.sh               # offline renderer tests
scripts/check-links.sh           # verify every link resolves (needs network)

Re-run the build after any project publishes a release. Asset names that carry a version number are baked into the page; only version-free asset names use the stable releases/latest/download/ form, which always points at the newest release. An APK is the exception: it must carry the release version and is always linked as that exact file, so the renderer refuses an unversioned .apk that is not excluded.

The last step of every listed project's release is one command, which rebuilds, tests, commits index.html, and publishes:

scripts/refresh-after-release.sh "retekey_apk v0.1.200"   # --dry-run to stop before pushing

Requirements: POSIX shell, Python 3, and curl. Setting GITHUB_TOKEN is optional and only raises the anonymous API rate limit.

Publishing

scripts/publish.sh -m "Site snapshot — 2026-08-16"   # force-push one snapshot commit
scripts/publish.sh --dry-run                          # show what would be published

Local history is kept in full; the public repository holds a single parentless commit with the current state of the site. Commit locally first — the script publishes the tree at HEAD.

Adding a project

Append an entry to src/site.json with id, repo, titles, taglines, tags, and body paragraphs, and name its id in one of the groups — C, Win32 API, or Android apps — then rebuild. A project in no group, or in two, fails the render rather than vanishing from the page. Optional fields: extra_links for online reading or documentation, exclude_assets for release files that should not be listed, and asset_labels for custom download labels.

License

MIT. See LICENSE.

About

my index page for github pages

Resources

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages