1. Getting started
- Start on the AWE homepage to understand the ecosystem.
- Open Products to choose a website or code repository.
- Use the product's own interface and follow its on-page instructions.
- For code, read the repository README, inspect the default branch and review setup instructions before installing dependencies.
- When reporting an issue, include the page or command, expected behavior, actual behavior, browser/OS, and reproducible steps. Never include passwords, API keys or private tokens.
2. Ecosystem map
AWE is a family of independent projects. The shared homepage is a directory and entry point, not a claim that every project uses one backend or shares one account system.
3. Public website directory
These are the public URLs supplied for this project. Their descriptions are high-level orientation; actual feature availability may change independently.
4. GitHub repository directory
Use the GitHub repository page for the authoritative README, source tree, issues, commits, releases and build instructions. This directory links to known AWE projects; it does not assert that all repositories are production-ready.
Search filters this starter directory. For the complete current repository inventory, use all repositories on GitHub ↗.
5. Playground guide
The AWE Playground supports HTML, CSS and JavaScript prototyping in your browser. Choose a file, edit the code, run a preview and download an HTML artifact. The preview is sandboxed and client-side.
- Run preview: applies the current editor contents.
- Choose a file: reads a selected local file in your browser.
- Download HTML: exports the current HTML/CSS/JS draft.
- Language mode: JSON and text are displayed; Python, Rust, C++ and other compiled/server languages need an external runtime.
6. Troubleshooting
A page is blank or styles are missing
Refresh, check the URL, inspect browser developer tools and verify that asset paths match the hosting base path. GitHub Pages project sites often need relative asset paths; root paths beginning with / may point to the domain root.
A button does nothing
Confirm the expected feature is implemented, check the browser console, and test without extensions. A visual control alone does not guarantee a connected backend.
A build fails
Read the first meaningful error, check the runtime version, install dependencies using the repository's documented lockfile command, and run formatting, linting, unit tests and an actual app smoke test.
Login, API or network errors
Check configuration and service availability. Never publish tokens in issues or commit secrets into source control.
7. Contribute safely
- Fork the repository or create a feature branch.
- Read existing architecture and conventions before changing files.
- Make a focused change and document user-visible behavior.
- Run formatting, static checks, tests and a manual smoke test.
- Open a pull request with a concise summary, evidence and known limitations.
Documentation rule: label implemented features, planned ideas and experimental behavior separately. Avoid promises such as “100% secure” or “always online” without measurable evidence.
Website-by-website documentation
Each live website has its own dedicated guide with its purpose, first steps and reliability notes. Open the live site from its guide.
Project-by-project handbook
Open a dedicated guide for each listed website or source repository. Each guide covers purpose, first steps, key controls, common problems, and reliability notes.