PHPackages                             upassist/prototypegenerator - 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. [Utility &amp; Helpers](/categories/utility)
4. /
5. upassist/prototypegenerator

ActiveNeos-package[Utility &amp; Helpers](/categories/utility)

upassist/prototypegenerator
===========================

A prototype generator to quickly generate prototypes based on nodetype definitions.

1.0.0(8mo ago)71.6k[2 issues](https://github.com/UpAssist/PrototypeGenerator/issues)MITPHP

Since Oct 25Pushed 8mo ago2 watchersCompare

[ Source](https://github.com/UpAssist/PrototypeGenerator)[ Packagist](https://packagist.org/packages/upassist/prototypegenerator)[ RSS](/packages/upassist-prototypegenerator/feed)WikiDiscussions main Synced 1mo ago

READMEChangelog (5)Dependencies (2)Versions (13)Used By (0)

UpAssist.PrototypeGenerator
===========================

[](#upassistprototypegenerator)

What does this package do?
--------------------------

[](#what-does-this-package-do)

This package lets you create scaffolding for prototypes for Neos using the commandline.

[![](https://camo.githubusercontent.com/c46aea483d6582b2f5e5daf24c271c9c1f0e168b93b8934725f85ae8b1a39d88/68747470733a2f2f7034362e66342e6e302e63646e2e676574636c6f75646170702e636f6d2f6974656d732f474775346b34704e2f64343932653263342d323865382d346361352d383861652d6438333861373936326336632e6769663f736f757263653d76696577657226763d3839336565626665383437366235626361336235343834326361376536656265)](https://camo.githubusercontent.com/c46aea483d6582b2f5e5daf24c271c9c1f0e168b93b8934725f85ae8b1a39d88/68747470733a2f2f7034362e66342e6e302e63646e2e676574636c6f75646170702e636f6d2f6974656d732f474775346b34704e2f64343932653263342d323865382d346361352d383861652d6438333861373936326336632e6769663f736f757263653d76696577657226763d3839336565626665383437366235626361336235343834326361376536656265)

Why did you make this?
----------------------

[](#why-did-you-make-this)

Working with an Atomic setup in Neos often requires creating quite some files for a single NodeType.

Fusion files, CSS files and sometimes specific JS files as well.

While working with templates like textExpander or livetemplates in PhpStorm, still creating the files takes up some time.

Not anymore! 😃

⚙️ How to install
-----------------

[](#️-how-to-install)

Simply run the composer command to install the package.

`composer require upassist/prototypegenerator --dev`

How to setup
------------

[](#how-to-setup)

### 🚀 Quick Setup

[](#-quick-setup)

Copy the following Settings and set your defaults:

```
UpAssist:
  PrototypeGenerator:
    # Set a default packageKey and you don't have to write the full `Vendor.Package` prefix every time  (but you still can) (optional)
    packageKey: ''
    # Folder structure (in array format) leading to your package
    packageParentFolder: ['DistributionPackages']
    # The rendering prototypes
    # For document, content and collection you can list the additional prototypes to render
    rendering:
      document:
        - template
      content:
        - organism
        - molecule
        - atom
      collection:
        - organism
        - molecule
        - atom
    # List of types you also want to create a CSS file
    renderCSS: [ 'template', 'organism', 'molecule', 'atom' ]
    # List of types you also want to create a JS file
    renderJS: [ 'organism' ]
    # The file extension used for rendering the CSS file (i.e. `css`, `scss`, `sass`, `less`)
    cssExtension: 'css'
    # The file extension used for rendering the JS file (i.e. `js`, `jsx`)
    jsExtension: 'js'
    # The name for your extendedRenderer (optional, but required in the default setup since the default templates use this)
    extendedRenderer: ''
```

### 👉🏻 Advanced Setup

[](#-advanced-setup)

Take a look at all the Settings where you can set defaults for how you would like to render your prototypes, change the inheritance and more.

📘 How to use
------------

[](#-how-to-use)

There are a couple of commands at your disposal:

CommandParamsExample`generator:prototype`--nodeType`./flow generator:prototype Content.TextWithImage``generator:atom`--prototypeName`./flow generator:atom Text``generator:molecule`--prototypeName`./flow generator:molecule TextWithImage``generator:organism`--prototypeName`./flow generator:organism TextWithImage``generator:template`--prototypeName`./flow generator:template Article``generator:extendedrenderer`--prototypeName`./flow generator:extendedrenderer Vendor.Package:ExtendedRenderer``generator:xlf`--nodeType`./flow generator:xlf Content.Text`💡 All commands support the `--force` parameter to overwrite files that are already created.

💡 You can use the full name of your prototype, and if you set a packageKey in the settings, you can omit it here. (I.e. Neos.NodeTypes:Content.Text becomes Content.Text)

💡 Nice to know
--------------

[](#-nice-to-know)

- The default templates add a `@Todo` in the generated files (you can modify this in the Settings) allowing you to use your IDE to see what you still must implement, probably best to remove it after you are done.
- You can modify the default templates to your liking using sprintf syntax to substitute strings; the settings show you what you can use.
- You can modify one or multiple templates. Or none if you like the defaults.
- This is build with atomic fusion use in mind, but should be possible to be used without that.
- Did I mention the generator created the content prototype and all atomic parts as well if you want it to? 😎

⚠️ Warning [\#1](https://github.com/UpAssist/PrototypeGenerator/issues/1#issue-1035464011)
------------------------------------------------------------------------------------------

[](#️-warning-1)

At this point determination of either Document, ContentCollection or Content types is done by the nodename, which will be changed in an upcoming version to look at the superType instead. Using this package now means you have to name your nodeType like this:

- `Vendor.Package:Document.Page`
- `Vendor.Package:Content.Text`
- `Vendor.Package:Collection.Section` | `Vendor.Package:ContentCollection.Section`

🧠 Thought about but not yet implemented...
------------------------------------------

[](#-thought-about-but-not-yet-implemented)

- Generate XLIFF files for all nodeTypes and defined language dimensions [\#3](https://github.com/UpAssist/PrototypeGenerator/issues/3#issue-1035466387)
- Implement more defaults for properties [\#2](https://github.com/UpAssist/PrototypeGenerator/issues/2#issue-1035465542)
- ...

🤔 Afterthought...
-----------------

[](#-afterthought)

This really was not meant to be ready and could probably be better thought through. However, it works pretty decent for the setup I work with and am very happy with the amount of time saved using this tool. I really hope it makes your Neos development life easier and welcome pull requests of course 😊

Thanks for reading this far and if you like it, let me know 🙂.

— *Henjo*

###  Health Score

38

—

LowBetter than 85% of packages

Maintenance53

Moderate activity, may be stable

Popularity22

Limited adoption so far

Community8

Small or concentrated contributor base

Maturity57

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 100% 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 ~127 days

Recently: every ~222 days

Total

12

Last Release

262d ago

Major Versions

0.3.1 → 1.0.02025-08-27

### Community

Maintainers

![](https://www.gravatar.com/avatar/0644de5e880c5b511c6b1cb1b08c80be5a64afd16d37dd9e633aa32c2d49f4cd?d=identicon)[hphoeksma](/maintainers/hphoeksma)

---

Top Contributors

[![hphoeksma](https://avatars.githubusercontent.com/u/250683?v=4)](https://github.com/hphoeksma "hphoeksma (55 commits)")

---

Tags

atomicneosneos-cms

### Embed Badge

![Health badge](/badges/upassist-prototypegenerator/health.svg)

```
[![Health](https://phpackages.com/badges/upassist-prototypegenerator/health.svg)](https://phpackages.com/packages/upassist-prototypegenerator)
```

###  Alternatives

[neos/eel

The Embedded Expression Language (Eel) is a building block for creating Domain Specific Languages

122.0M27](/packages/neos-eel)[kaufmanndigital/gdpr-cookieconsent

A ready-to-run package, that integrates an advanced cookie consent banner into your Neos CMS site.

2540.7k](/packages/kaufmanndigital-gdpr-cookieconsent)[shel/neos-colorpicker

A plugin for Neos CMS which provides a colorpicker editor

1494.4k6](/packages/shel-neos-colorpicker)[shel/neos-commandbar

A commandbar (CMD+K) for Neos CMS

1614.6k1](/packages/shel-neos-commandbar)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)
