Search

Search results

27 results for "wireframe":

  • 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.
  • 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?
    /about/why-use-wireframe/
  • 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.
  • 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.
  • 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.
  • Requirements
    /about/requirements/
  • Partials
    /docs/view/partials/
    Partials contain common markup, widgets, and any other content shared by multiple layouts and/or views.
  • 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/
  • 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.
  • Components
    /docs/view/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.
  • Caching
    /docs/caching/
    In order to make your site run fast, Wireframe provides a number of features related to caching: some are fully automatic, while others need to be specifically enabled. On this page we're going to introduce all the major caching features in Wireframe.
  • Alternatives
    /about/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
    /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
  • Renderers
    /docs/view/renderers/
    Renderers are optional addon modules for Wireframe, used whenever you want to render view files authored in something other than PHP — typically in some sort of a templating language.
Back to top