Projects

Webisters ships four ready-to-use project templates plus a shared template engine. Pick the shape that matches your build — every template sits on top of the same library set, so you can swap or grow into another as your project evolves.

App

Full-stack MVC application — controllers, models, views, the works.

API

MVC tuned for JSON responses — perfect for headless backends and SPAs.

One

A single-file project — quick APIs and prototypes, all functions in one place.

Site

Static-site template for landing pages, marketing and content-first builds.

Template

Shared view-template engine used by every Webisters project.

Installation

Install any template directly with Composer's create-project:

composer create-project webisters/app app
composer create-project webisters/api api
composer create-project webisters/one one
composer create-project webisters/site site

Or, if you've installed the Webisters CLI globally, scaffold a project with one command:

composer global require webisters/webisters
composer global exec webisters setup

webisters new-app my-app
webisters new-api my-api
webisters new-one my-one
webisters new-site my-site

If the webisters binary isn't on your PATH yet, use Composer's fallback:

composer global exec webisters new-app my-app

Then install dependencies inside the new project:

cd my-app
composer install

Picking a template

Not sure which one to start with? A short cheat-sheet:

  • App — start here for a typical web app with pages, forms, sessions and a database.
  • API — pick this for a JSON-only backend powering a SPA or mobile client.
  • One — perfect for a tiny service, a prototype, or a single endpoint you want in one file.
  • Site — content-driven sites without a database: marketing pages, documentation, landing pages.