Download the PHP package codeq/simpletemplate without Composer
On this page you can find all versions of the php package codeq/simpletemplate. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
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 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.
Informations about the package simpletemplate
Neos - Simple Template for Fluid template path mapping
You never need to manually define a template path to your Fluid file anymore. The simple template automatically sets up folder paths based on the Neos best practises.
Usage
-
Install with
composer require codeq/unicodenormalizer -
Your node types will automatically use the new template, examples of the auto mapping can be found below.
- To use auto mapping in your Fusion components, the prototype needs to be baed on the SimplteTempalte
Best practises for folder and file naming
NodeTypes
-
Each NodeType configuration has it’s own file:
Configuration/NodeTypes.<Document/Content>.<NodeType Name>.yaml -
Each NodeType has it’s own folder for rendering with:
- The Fusion prototype name is
Example.Site:<Document/Content>.<NodeType Name>
Sub-NodeTypes
Some NodeTypes are only allowed inside other NodeTypes, e.g. a SliderItem is always a subnode of a Slider. To better group them you can use the following folder structure:
-
Each Sub-NodeType configuration has it’s own file:
Configuration/NodeTypes.<Document/Content>.<NodeType Name>.<Sub-NodeType Name>.yaml -
Each Sub-NodeType has it’s own folder for rendering with:
- The Fusion prototype name is
Example.Site:<Document/Content>.<NodeType Name>.<Sub-NodeType Name>
Standalone Fusion Components
Components are reusable Fusion (and Fluid) modules which can be reused when rendering different NodeTypes. A component consists of one Fusion and an optional Fluid file.
-
Each component has its own folder inside the Components folder with:
-
Each Fluid component must inherit from
prototype(Example.Site:SimpleTemplate) - The Fusion prototype name is
Example.Site:Component.<Component Name>
The main idea behind all of it is this:
The location of all files related to a Fusion object (Fusion protype, Fluid template) should always be deducible from object's name name. E.g.
Certain prototypes should provide reusable functionality and therefore only named Components. Those should not bound to a particular NodeType.
If you need to break apart one big Fusion prototype into a few smaller ones, you can always group them with another layer of namespacing, e.g.:
