Download the PHP package wireframe-framework/site-wireframe-boilerplate without Composer

On this page you can find all versions of the php package wireframe-framework/site-wireframe-boilerplate. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package site-wireframe-boilerplate

site-wireframe-boilerplate

A ProcessWire starter site profile based on the wireframe output framework.

This project is intended as an opinionated starting point for sites powered by the wireframe module, and contains a number of site features that make more sense as a part of a site profile, rather than the wireframe module itself.

Git ignore (.gitignore) file

Please note that wireframe boilerplate includes an opinionated .gitignore file based on Bare Minimum Git (https://gist.github.com/salcode/10017553). Please make sure that this file suits your workflow, and modify it as necessary.

Purpose

Default .gitignore file serves two primary purposes: it keeps clutter out of your version control system, and – more importantly – it helps avoid slipping secrets into the VCS. Storing sensitive data (passwords, keys, etc.) in a VCS is considered a bad practice, and should be avoided.

Important considerations

Important considerations regarding the .gitignore file:

Installing modules without Composer

Since the /site/modules/ directory is by default included in the .gitignore file ignore rules, files added beneath it won't show up if you add them and type git status in the site directory. This is by design, since the wireframe boilerplate expects modules to be installed with Composer. That being said, installing modules without Composer and adding them to your version control system is easy:

Another way, obviously, would be to comment out or remove the line in the .gitignore file affecting the modules directory. If you really want to add all your module files and directories to Git, this is a perfectly fine thing to do. And finally, you can also manually add individual module folders into the "whitelisted files" section of your .gitignore file.

Whitelisted files

At the end of the .gitignore file you'll find a section for whitelisted files. If your site requires some one-off deviations from the base rules, the easy (and safe) way out would be including more rules here instead of removing earlier ignore rules.

Requirements

Other requirements, such as ProcessWire modules, are installed with Composer.

Notes about composer.json

In case you're wondering why we're specifying ProcessWire itself as one of our requirements via the composer.json file even though we don't really need it (as a Composer requirement), this is a trick used to force Composer to install ProcessWire before the boilerplate in case they are both required in the same project.

Note: feel free to remove the ProcessWire requirement if you want to – that won't break anything.

How to install

  1. Obtain a fresh copy of ProcessWire 3.0.112 or newer and upload/unzip it on your server.

  2. Download or clone the contents of this repository into /site-wireframe-boilerplate/ within the directory you uploaded/unzipped ProcessWire to. You will see other site directories (including /site-default/) already there, but these can be safely ignored for the time being.

  3. Go to the /site-wireframe-boilerplate/ directory and run composer install.

  4. Install ProcessWire by accessing the URL it lives in with your web browser. When the installer asks you to choose a site profile, choose "Wireframe Boilerplate Site Profile".

License

This project is licensed under the Mozilla Public License Version 2.0.


All versions of site-wireframe-boilerplate with dependencies

PHP Build Version
Package Version
Requires php Version >=7.1
wireframe-framework/processwire-composer-installer Version ^1.0.1
processwire/processwire Version ^3.0
teppokoivula/markup-menu Version ^0.6.2
wireframe-framework/wireframe Version ^0.4.0
teppokoivula/search-engine Version ^0.8.1
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package wireframe-framework/site-wireframe-boilerplate contains the following files

Loading the files please wait ....