# AWEEXP — Publishing Rules

AWEEXP accepts AWE and community projects that are openly licensed and meet the publication standard. Acceptance is **not guaranteed**: submitting the form only starts the review process.

## 1. Static websites
A project is a **static website** when its published experience is delivered entirely from static files (HTML/CSS/JS/assets) and does not require a server-side application, database, or runtime backend to operate.

Limits for a static web project:
- minimum **2 files**;
- maximum **10 files**;
- maximum **2 folders**;
- the site must work as a static publication.

## 2. Other project types
CLI, GUI, Android/mobile, games, AI tools, libraries, and other non-static project types are not restricted by the 10-file/2-folder web limit. The same quality and safety rules still apply. AWEEXP presents the appropriate built artifact/download when a project is not a web project.

## 3. Required for every submission
- The project must be **open source**.
- Source code must be available to reviewers.
- The project must contain at least **2 files**.
- The project must be functional enough to review.
- The project must have a clear name and description.
- The project must not contain advertisements or promotional ad systems.
- The project must not contain illegal, malicious, harmful, deceptive, or abusive content.
- The project must not contain unauthorized, deceptive, malicious, or unrelated links.
- Third-party assets/code must be used lawfully and with compatible licensing.
- No credential theft, malware, spyware, phishing, or other abusive functionality.

## 4. Design and quality
Projects should have a clean, coherent, usable presentation. Static websites are expected to have a reasonably polished design and usable navigation. A project can be rejected for being incomplete, broken, misleading, or clearly below the publication standard.

## 5. Submission
Use the official AWEEXP submission form:

https://forms.gle/F4oMQiyt3bNibJTP9

Submitting a project does **not** guarantee publication, integration with AWE, promotion, or conversion into an AWE product.

## 6. Publication structure
Each project belongs to a type directory and has a corresponding JavaScript catalog file, for example:

- `web/web.js`
- `apps/apps.js`
- `cli/cli.js`
- `gui/gui.js`
- `android/android.js`
- `games/games.js`
- `ai/ai.js`
- `tools/tools.js`

The public catalog is generated from these project records. Web projects may be previewed; other project types expose their build/download artifact.