Directory of standalone browser tools, games, creative studios, utilities, and business pages, with page inventory and static-site verification tooling.
๐ท๏ธ Maintained in qamotech/DevDashboard ยท ๐ Public repository
- ๐งญ Animated directory and compatibility menu entry.
- ๐ฎ Games, creative studios, calculators, and productivity pages.
- ๐ Page manifest, local brand assets, and link/metadata checks.
- ๐๏ธ Static build tooling and a separate hosted prompt-tool experience.
Serve the repository, open index.html, choose a page from the directory, then run the existing checks before altering navigation or adding another page.
git clone https://github.com/qamotech/DevDashboard.git
cd DevDashboardUse a current browser. Serve the repository root to preserve relative assets and a stable browser origin:
python -m http.server 8000Open http://localhost:8000/index.html. Keep related assets beside the entry file. No npm setup is declared in the inspected repository.
- ๐
MiyagiThrow.html - ๐
QamelotMenu.html - ๐
acai-adaptive-cyber-analysis-interface.html - ๐
blob-bash-royale.html - ๐
blood-and-gold-panther-arena.html - ๐
build-site.mjs - ๐
contractor-tool-belt-tactical-utility-engine.html - ๐
css-visuals-library-40.html - ๐
cyber-count-calcun8r-edison-hwy.html - ๐
devdash-svg-studio.html - ๐
eco-tech-motion-library.html - ๐
ecotechcomm-secure-frequency.html - ๐
workerโ source directory
The authoritative inventory is page-manifest.json, not a fixed marketing count. Individual pages have different dependencies and maturity. The static directory and hosted worker build are separate deployment surfaces.
Keep credentials, private exports, customer records, and personal information out of commits and screenshots. A local browser demo is not evidence of account security, reliable persistence, or connected external services. Preserve exports before changing storage keys or resetting an application.
- ๐ Confirm the entry file and asset paths above exist in your checkout.
โถ๏ธ Start the documented runtime and inspect browser or terminal errors.- ๐งญ Exercise the project-specific workflow described above using sample data.
- ๐ฑ Check narrow and wide layouts when the project has a browser interface.
- ๐พ Verify save/export and recovery behavior before trusting important work to it.
- ๐ Record the exact command, browser, operating system, and outcome of your checks.
This guide was prepared from repository files and manifests. It does not claim a fresh build, deployment, security audit, or full functional test of this project.
Keep changes focused and explain the user-visible result. Preserve existing assets and configuration unless a change requires updating them. Include reproduction steps, expected and actual behavior, and relevant screenshots with personal information removed. For UI work, include the viewport and browser; for runtime issues, include the command and error text.
- ๐ Keep this guide aligned with implemented behavior and current entry points.
- ๐งช Add or maintain checks for the core workflow before expanding features.
- โฟ Review labels, keyboard navigation, contrast, and responsive layout.
- ๐ฆ Document external services, asset rights, and deployment prerequisites.
This documentation update does not grant a new software or asset license. Consult existing license files, source headers, package metadata, and original asset terms; resolve inconsistencies with the owner before redistribution. Third-party names and resources retain their own terms.
The material below is retained verbatim for history and project-specific context. Template instructions and older claims may differ from the source inventory above.
Qamelot Menu is a flat collection of 48 browser-based tools, games, studios,
experiments, and small-business webpages. index.html is the complete animated
directory. Every webpage is a standalone HTML file with its local CSS,
JavaScript, fonts, and images embedded.
index.htmlโ Qamelot Menu and the public home page*.htmlโ standalone, lowercase, hyphenated webpagesQamelotMenu.htmlโ compatibility copy of the complete animated directorypage-manifest.jsonโ the authoritative page inventoryquality_check.pyโ metadata, safety, reference, and menu-completeness auditenhance-pages.mjsโ repeatable 40-point metadata, navigation, and accessibility enhancerqamelot-media-assets/โ organized Qamelot Media brand kit and source artworkbuild-site.mjsandworker/โ the hosted N8 Prompt and funPromptz build.openai/hosting.jsonโ hosted site configurationdeploy_github.batโ verifies and publishes the collection to GitHub Pages
The 48 standalone pages and their runtime assets remain at the repository root.
The Qamelot Media brand kit is kept in its own source folder so campaign files
stay together without becoming dependencies of the standalone pages. GitHub
Pages serves the repository root directly, while the Sites build publishes the
N8 Prompt and funPromptz experience. Installed development dependencies remain
in node_modules and are not published.
python -m http.server 8000
npm run check
npm run check:links
npm run buildOpen http://localhost:8000/ to use Qamelot Menu. Each menu card displays its
complete URL and links directly to its standalone page.