Since the wq framework is designed to create fully custom applications, the first step for most wq-powered projects is to start up a web server and install a number of software packages. If you are planning to self-host, or would just like to experiment with the framework, you can follow the process below to get an application up and running. (Be sure to use the referral link above to get a discount on hosting fees!)
If you would rather not run a wq-powered server yourself, you may want to reach out to any of the existing subscription-based projects and "campaign builder" apps to explore potential collaboration. Our partners also provide flexible support plans ranging from a couple of hours of installation support to full-service bespoke design, software development, and application hosting.
If you are using wq.app and wq.db together, you can use the
wq start command provided by the wq Django template. For production, you will need a WGSI-capable webserver like Apache, and a database to host the application. wq.db is generally used with PostgreSQL and PostGIS, but any Django-supported database will work. You can also use Django's built-in
./manage.py runserver for development, or even use wq.app by itself and replace wq.db with your own backend solution.
# Install wq pip install wq wq start [PROJECTNAME] -d [DOMAINNAME]
Detailed installation instructions are available for each of the following operating systems:
wq does not come with a canned data model by default. This makes it extremely flexible to adapt to a variety of project workflows, but means you need to think a bit about how you want to structure your data before continuing. The data schema you define will be used to create one or more database tables as well as the HTML forms for entering data.
See the following for more information on defining a data schema:
Introduction to Django models and tips for creating them from an XLSForm definition.
A comprehensive list of the common field / question types and conventions for using them in wq.
Instructions for defining nested forms ("repeat groups" in XLSForm syntax) as well as user-definable attributes (e.g. EAV).
Once your data model is defined and your REST API is running, you can start customizing the a user interface to list, view, create, and edit records in your database. As of version 1.0, wq includes a default set of fully functional HTML/Mustache templates for "list", "detail", and "edit"/"new" views. You can use the
wq maketemplates command to get automatically generated templates for each registered model. This command is called by the default
The generated templates are stored in
templates/ so that they can be individually customized. Once you start customizing them, be sure not to overwrite them by autogenerating them again.
wq maketemplates will prompt you before overwriting any existing templates. If you would like a uniform layout for all forms and are comfortable editing template-generating templates, you can also edit the files
master_templates/ directly and run
wq maketemplates again.