AWE SCHOOL · FREE LEARNING PATH

Understand the ecosystem.
Become a builder.

A guided introduction to AWE, its products and repositories, and the practical skills needed to explore and build technology. Learn in small steps; every lesson includes an action you can try.

Start the course ↓

Learning path

Mark lessons as complete to track your progress in this page. Progress is kept only for the current browser session and is not sent to a server.

0 of 6 lessons completed

What is AWE?

AWE is a family of independent projects across software, operating systems, AI, networking, knowledge and creative tools. AWEONE is the ecosystem's shared entry point.

I can explain the difference between an ecosystem and a single application.

Websites vs repositories

A website is the experience a visitor uses. A GitHub repository contains project files, history, issues and contribution workflows. A website may be built from a repository, but the two are not identical.

I opened a live site and its related source repository.

Explore a project

Read the README, inspect the directory structure, find the entry point, identify dependencies and locate tests. Distinguish what exists today from future plans.

I found a README, an entry file and a documented setup command.

Your first web page

HTML describes structure, CSS controls appearance and JavaScript adds behavior. Try a small change, run it in the browser and observe the result.

<h1>Hello, AWE!</h1> <button onclick="alert('It works!')">Try me</button>

Open the Playground ↗ I edited and ran a small HTML example.

Contribute responsibly

Use a feature branch, make a small focused change, test it, explain the change and open a pull request. Never commit credentials or personal secrets.

I understand the basic pull-request workflow.

Test and troubleshoot

Reproduce the problem, read the first useful error, check the browser console, confirm configuration and test the actual user journey—not only whether a build command passes.

I can write a clear bug report with reproducible steps.

Project map: where to learn next

AWE Library — explore knowledge and reading experiences.
AWEP2P — explore peer-to-peer concepts.
AWEOS — explore operating-system concepts.
AWEOCR — explore document and text recognition workflows.
AWE repository — study the website source and its commit history.
AWE Documentation — troubleshooting, contribution and repository guidance.

Learning principles

Be curious, test assumptions, respect privacy, document limitations, prefer small verifiable steps and treat security as a design requirement. A project is not “finished” merely because a page looks good: its core workflows, error handling, accessibility and deployment must also be tested.

Understand the ecosystem.Become a builder.