Search results
36 results for "wireframe":
- Why use Wireframe?/about/why-use-wireframe/On this page we'll answer the question of "why use Wireframe", and also give you a crash course on the concept of output strategies: what they are, why they're needed, and what are some of the most popular output strategies.
- Layouts/docs/view/layouts/Layouts provide a frame for your pages, containing all the common elements shared by most, if not all, of your templates.
- Git ignore (.gitignore) file/docs/wireframe-boilerplate/git-ignore-file/The Wireframe boilerplate site profile includes an opinionated .gitignore file based on Bare Minimum Git project.
- Directory structure/docs/directory-structure/The directory structure outlined here is loosely based on the recommended project directory structure for Zend Framework 1.x. Each component has it's place in the tree, and each directory exists for a reason.
- Utility classes/docs/patterns-and-practices/utility-classes/So-called utility classes are often considered an antipattern in object-oriented programming, but in some cases they may be just what the doctor ordered. This page contains instructions on adding a simple Utils class to a Wireframe site.
- API return values/docs/wireframe-api/api-return-values/Wireframe API responds to API requests with a JSON object containing metadata (query status, API path, array of used arguments, etc.) along with any data returned by the endpoint. Failed requests receive a similar response, along with a message about the
- Home/Wireframe is an output framework for the ProcessWire content management system. With MVC inspired architecture it promotes separation of concerns and aims to resolve scalability issues. Wireframe is a solid foundation for building all types and sizes of P
- View placeholders/docs/view/view-placeholders/View placeholders are the way you inject content from view files – or dynamic content constructed in a Controller – into layout files.
- Output framework vs. output strategy/about/output-framework-vs-output-strategy/
- Program flow/docs/program-flow/This page outlines the basic program flow, i.e. what happens behind the scenes when a visitor enters a site running Wireframe.
- Available API endpoints/docs/wireframe-api/available-api-endpoints/Out of the box Wireframe API provides endpoints for components, pages, and partials. Keep in mind, though, that none of these are enabled by default — you need to enable the endpoints that you need via module configuration settings.
- Requirements/about/requirements/
- Custom API endpoints/docs/wireframe-api/custom-api-endpoints/Wireframe API was designed to be extendable, and thus it's possible to add custom endpoints on a case-by-case basis.
- Controllers/docs/controllers/Controllers are template-specific classes. Their main responsibilities include processing user input, fetching data from the Model (ProcessWire), formatting it as needed, and passing it to the View.
- About/about/What is Wireframe, where did it come from, who is it for – and what sets it apart from all the other ProcessWire output strategies, or output frameworks, out there?
- A bit of history/about/a-bit-of-history/
- Partials/docs/view/partials/Partials contain common markup, widgets, and any other content shared by multiple layouts and/or views.
- View/docs/view/In the context of Wireframe term "View" is used as a common name for a set of interconnected concepts: the View class, layouts, views (sometimes called "view files"), and partials.
- GET variables as API arguments/docs/wireframe-api/get-variables-as-api-arguments/For security reasons the API won't automatically convert GET params into arguments, but you can of course do exactly that manually in the Wireframe element that handles the request.
- Access control/docs/wireframe-api/access-control/Wireframe API doesn't provide any built-in logic for access control, instead depending on template access settings by default. If you need something more sophisticated than that, BYOAC (bring your own access control.)