Download the PHP package devuri/twigit without Composer

On this page you can find all versions of the php package devuri/twigit. 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?

Example code of devuri/twigit

Informations about the package twigit

A Streamlined Templating Approach

Modern development increasingly leans toward mono repo architectures that centralize application code, dependencies, and templates in a unified repository. This approach simplifies collaboration, version control, and deployment—making it ideal for large-scale and maintainable web projects.

Embrace the Hybrid CMS:

A hybrid-cms approach allows you to keep WordPress’ as your back end while bypassing the default theme system in favor of a templating engine like Twig.

1. Install Twigit via Composer

In your project root (mysite), install Twigit using Composer:

This installs Twigit and Twig in the vendor directory.

2. Configure Twigit to Use the templates Directory

Twigit can be configured via an mu-plugin or programmatically to locate templates in mysite/templates. For example:

If using Raydium, many configuration steps are already handled. Learn more here: Raydium GitHub Repository.

3. Organize Your Templates

Create a templates directory in your project root:

You can copy and adapt Twigit's base templates from its GitHub repository: Twigit Base Templates

4. Example Twig Template

Here’s a simple example of a base Twig template:

All versions of twigit with dependencies

PHP Build Version
Package Version
Requires php Version ^7.4 || ^8.0
pimple/pimple Version 3.5.*
psr/container Version ^2.0
twig/twig Version 3.11.3
symfony/deprecation-contracts Version ^2.5
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 devuri/twigit contains the following files

Loading the files please wait ....