Skip to content
Greg Bowler edited this page Mar 6, 2018 · 82 revisions

Docs are being rewritten for WebEngine version 3.0, please sit tight!

PHP.Gt logo

Welcome to the PHP.Gt WebEngine — a lightweight PHP 7 application development toolkit aimed at streamlining development and respecting web technologies.

Web frameworks offer many features, but often come with steep learning curves or imposing rules. The motivation behind this project is the belief that what a framework can offer can be achieved by eliminating code rather than adding more.

Introduction

The core concept behind the WebEngine is that applications start static first, the simplest application consisting of a single index.html. HTML can be split into templates and included using Custom Elements <like-this>. When the page needs to become dynamic, PHP is added to the index.php, having context of the page's DOM.

Main features

Separation of concerns

Each component within a WebEngine application can be developed within its own ??context??, usually within its own file on disk, so that WebEngine can hook everything up and make the magic happen. There is a strong separation of concerns promoted throughout the WebEngine and within applications built upon it.

Separate areas of concern:

  • Page View - the representation of a page or template, in HTML.
  • Page Logic - the business logic that makes Views dynamic, in PHP.
  • Database - the database queries, in SQL.
  • Service View and Logic - the same concept as Page View/Logic, but for building webservice requests rather than pages, in JSON and PHP.
  • Class - the separate areas of functionality that build up your application's logic, in PHP.
  • Client side assets - the source code for pages' JavaScript and CSS (or preprocessors).

Getting started

If you're new to WebEngine, read the quick start guide first, and work through the beginner tutorials (Hello, World! and Hello, You!) to get the best introduction to the toolkit.

The core concepts to know are detailed in "The Book", starting with the request-response lifecycle.

Help & Support

Use Stack Overflow to get help with technical issues. Tag your question with webengine and a developer will be alerted to answer your question as soon as possible.

Report bugs and suggest features on the Github issue tracker.

Clone this wiki locally