Search results

24 results for "wireframe":

  • Home
    Wireframe is an output framework for the ProcessWire content management system. With MVC (model–view–controller) inspired architecture it promotes separation of concerns and aims to resolve scalability issues. Wireframe is a solid foundation for building
  • Why use Wireframe?
  • 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
    The Wireframe boilerplate site profile includes an opinionated .gitignore file based on Bare Minimum Git project.
  • 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
    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.
  • Output framework vs. output strategy
  • Program flow
    This page outlines the basic program flow, i.e. what happens behind the scenes when a visitor enters a site running Wireframe.
  • View placeholders
    View placeholders are the way you inject content from view files – or dynamic content constructed in a Controller – into layout files.
  • 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.
  • Requirements
  • 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.
  • Partials
    Partials contain common markup, widgets, and any other content shared by multiple layouts and/or views.
  • 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
  • Alternatives
    Wireframe isn't the only MVC-ish output approach for ProcessWire – not by a long shot. In case you're liking the idea of an MVC style output strategy but Wireframe doesn't seem like the perfect fit, we've got you covered. On this page we've gathered a lis
  • Getting started
    With the instructions on this page you should get your Wireframe based project up and running with ease. You may also want to check out the boilerplate site profile, which is an out-of-the-box Wireframe setup with some useful front-end-related features bu
  • Components
    Components are reusable chunks of code and markup, comprised of a component class and optional component view(s). Like partials, but with the ability to process arguments and provide callable methods.
  • Static utility methods
    Wireframe provides static utility methods for cases where instantiating an object might be inconvenient, or where they can notably speed up the development workflow. On this page we list included methods, their parameters and return values, and explain ho
  • Configuration settings
    You can modify the behaviour and paths used by Wireframe through ProcessWire's site config settings placed in /site/config.php.
Back to top