Website Workflow

Introduction

Wave Framework itself is simple to get a hold on, but when it comes to building a website on it, there are a number of things that you should know when it comes to URL requests sent to Wave. This document is a general overview about how Wave Framework handles the whole website architecture and design.

Wave Framework comes by default with a URL and View controllers that are used to build a functioning website. URL Controller interprets the URL that user entered and finds a matching View and the View Controller then loads that View. There are also other things that have to be kept in mind. Sitemap file can carry a lot of configuration settings that can affect how your website works. You can define both static and dynamic URL's in Sitemap, do redirects and more. It is also possible to load classes, libraries and additional functionality based on Sitemap configuration even before Views and other MVC objects are loaded.

URL Request Workflow

Here is an overview of what happens, if user enters a URL to their browser and is sent to the server that uses Wave Framework. For example, if you are currently running the base unmodified version of Wave and enter the URL 'http://www.example.com/example', then a number of things will happen:

Anything in this workflow can be changed by you as a developer, if you edit URL Controller, View Controller or Data Handler files.

Building websites is a multi-layered process. Wave Framework has a lot of features that are tied to this workflow. Topics such as cache, testing, API calls and more can enhance the way you build your websites or web-based software. I suggest you go through other feature guides in order to learn more about both the topics covered in this document and those that were not. It is also recommended that you learn more about the API itself as well as API wrappers, that help you use full range of functionality of Wave Framework.