PHPackages codeq/simpletemplate - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. codeq/simpletemplate ActiveNeos-package codeq/simpletemplate ==================== This simple template automatically resolves file paths according to the Neos best practises. v1.0.1(7y ago)01131MITPHP Since Jan 13Pushed 7y ago2 watchersCompare [ Source](https://github.com/code-q-web-factory/neos-simpletemplate)[ Packagist](https://packagist.org/packages/codeq/simpletemplate)[ RSS](/packages/codeq-simpletemplate/feed)WikiDiscussions master Synced 5d ago READMEChangelog (1)Dependencies (1)Versions (3)Used By (1) Neos - Simple Template for Fluid template path mapping ====================================================== [](#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 ----- [](#usage) 1. Install with `composer require codeq/unicodenormalizer` 2. Your node types will automatically use the new template, examples of the auto mapping can be found below. 3. To use auto mapping in your Fusion components, the prototype needs to be baed on the SimplteTempalte ``` prototype(Example.Site:Component.Footer) < prototype(CodeQ.SimpleTemplate:Template) { ... } ``` Best practises for folder and file naming ----------------------------------------- [](#best-practises-for-folder-and-file-naming) ### NodeTypes [](#nodetypes) 1. Each NodeType configuration has it’s own file: `Configuration/NodeTypes...yaml` 2. Each NodeType has it’s own folder for rendering with: ``` Resources/Private/Fusion/// .fusion .html (optional) ``` 3. The Fusion prototype name is `Example.Site:.` ### Sub-NodeTypes [](#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: 1. Each Sub-NodeType configuration has it’s own file: `Configuration/NodeTypes....yaml` 2. Each Sub-NodeType has it’s own folder for rendering with: ``` Resources/Private/Fusion//// .fusion .html (optional) ``` 3. The Fusion prototype name is `Example.Site:..` ### Standalone Fusion Components [](#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. 1. Each component has its own folder inside the Components folder with: ``` Resources/Private/Fusion/Components// .fusion .html (optional) ``` 2. Each Fluid component must inherit from `prototype(Example.Site:SimpleTemplate)` 3. The Fusion prototype name is `Example.Site:Component.` The main idea behind all of it is this: --------------------------------------- [](#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. ``` Example.Site:Content.Slider -> ../Private/Fusion/Content/Slider/Slider.fusion -> ../Private/Fusion/Content/Slider/Slider.html Example.Site:Component.Footer -> ../Private/Fusion/Component/Footer/Footer.fusion -> ../Private/Fusion/Component/Footer/Footer.html ``` 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.: ``` Example.Site:Content.News -> ../Private/Fusion/Content/News/News.fusion Example.Site:Content.News.RelatedArticles -> ../Private/Fusion/Content/News/RelatedArticles/RelatedArticles.fusion ``` ### Health Score 29 — LowBetter than 59% of packages Maintenance20 Infrequent updates — may be unmaintained Popularity10 Limited adoption so far Community12 Small or concentrated contributor base Maturity64 Established project with proven stability Bus Factor1 Top contributor holds 62.5% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~158 days Total 2 Last Release 2886d ago ### Community Maintainers ![](https://www.gravatar.com/avatar/c898f86932821ebd9add02d4f01864bd4804e1a620083fbc5951af0bb3e9c850?d=identicon)[codeq](/maintainers/codeq) --- Top Contributors [![dimaip](https://avatars.githubusercontent.com/u/837032?v=4)](https://github.com/dimaip "dimaip (5 commits)")[![rolandschuetz](https://avatars.githubusercontent.com/u/735982?v=4)](https://github.com/rolandschuetz "rolandschuetz (3 commits)") --- Tags flowNeosfluid ### Embed Badge ![Health badge](/badges/codeq-simpletemplate/health.svg) ``` [![Health](https://phpackages.com/badges/codeq-simpletemplate/health.svg)](https://phpackages.com/packages/codeq-simpletemplate) ``` ### Alternatives [shel/neos-colorpicker A plugin for Neos CMS which provides a colorpicker editor 1494.4k6](/packages/shel-neos-colorpicker)[shel/neos-hyphens A plugin for Neos CMS which provides hyphens for the inline editor 20200.7k1](/packages/shel-neos-hyphens)[techdivision/ckstyles Neos package which enables you adding your custom style classes for the CkEditor with a simple Yaml configuration 21166.3k](/packages/techdivision-ckstyles)[moc/notfound Neos CMS package that loads a normal editable page for displaying a 404 error 18167.5k](/packages/moc-notfound)[carbon/includeassets Include your assets (css, js) in an easy way into Neos 14228.6k10](/packages/carbon-includeassets)[shel/nodetypes-analyzer Graphical analysis & visualizer for the Neos CMS nodetypes as backend module 2160.6k](/packages/shel-nodetypes-analyzer) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)