Skip to content
ONIWC
iwc 0.1.0

Example projects

Complete, runnable IWC projects. Each one compiles with iwc check and passes its own tests on the IWC version these docs describe.

shop

A complete e-commerce store — the most complete example, shipped with the CLI as a template.

Terminal
iwc create my-store --template store
cd my-store && iwc dev --open
  • Features: catalogue with categories, search and pagination; product pages; a client-side cart; sign-in that returns you to checkout; server-side pricing and stock; order history; an admin dashboard with stock chart and a "Mark shipped" workflow; newsletter sign-up; an order workflow, event and email job.
  • Architecture: state/cart.state.iwc → checkout form (include: ["STATE.cart.items"]) → api/checkout.api.iwc → actions/checkout.action.iwc (transactional: prices from the database, guarded stock decrement, payment call) → workflows/order.workflow.iwc → events/order-placed.event.iwc → jobs/order-email.job.iwc.
  • Size: 47 files, 13 screens, 9 APIs, 5 schemas, 42 tests.
  • Accounts: casey@lumen.test / casey-pass-123 (customer), admin@lumen.test / admin-pass-123 (admin).
  • Walkthrough: Tutorial 11. Also an admin dashboard example.

cookbook

One validated example per common page type, used throughout the framework guides: a landing page with a feature grid and FAQ, login and registration, a dashboard with notes, product listing and details, cart, checkout and an API-connected page. Its files are shown in full in the guides where each pattern is explained, starting with UI development.

tasks

A to-do application with an admin dashboard — built in Tutorials 8–10.

Project files
tasks/
├── api/
│   ├── login.api.iwc
│   ├── me.api.iwc
│   ├── register.api.iwc
│   ├── task-create.api.iwc
│   ├── task-delete.api.iwc
│   ├── task-list.api.iwc
│   └── task-update.api.iwc
├── components/
│   ├── header.component.iwc
│   └── stat.component.iwc
├── database/
│   ├── task.schema.iwc
│   └── user.schema.iwc
├── layouts/
│   ├── admin.layout.iwc
│   └── main.layout.iwc
├── styles/
│   └── main.css
├── tests/
│   ├── admin.test.iwc
│   └── tasks.test.iwc
├── ui/
│   ├── admin.ui.iwc
│   ├── home.ui.iwc
│   ├── login.ui.iwc
│   ├── not-found.ui.iwc
│   ├── register.ui.iwc
│   ├── task-edit.ui.iwc
│   └── tasks.ui.iwc
├── app.iwc
└── package.iwc
  • Features: sign-up and sign-in; per-user tasks with priority, due date and done state; edit form; live list; admin dashboard with database aggregates, a bar chart and a live table; PostgreSQL configuration.
  • Tests: 13 — on SQLite and PostgreSQL.
  • Setup: iwc dev, sign in as max@example.com / member-pass-123 or admin@example.com / admin-pass-123.

auth

An authentication application — Tutorial 7: registration, sign-in, sign-out, a protected account page, an admin-only member list, a header that changes with the visitor. 10 tests.

chat

A real-time chat room — Tutorial 14: messages appear in every open browser through live data over Server-Sent Events; the sender is taken from the session, never the request. 6 tests.

More tutorial projects

ProjectTutorialShows
hello1, 2The starter app plus a menu page
buttons3A component with props, defaults and expressions
layouts4A shared layout with navbar, footer and 404
contact-form5A validated form writing to the database
api-connect6An external service behind an action and GET API
api-onlyProject typesA JSON API with no screens
payments12Hosted checkout with server-side confirmation
push13PWA, Web Push, devices, background jobs
offline15Stored screens, queued writes, conflicts

Every file of each tutorial project is printed in full in its tutorial, so you can rebuild it step by step.

Source: apps/marketing/content/docs/examples.md