NitroNet supports only the precise project-structure of Nitro. That's a current requirement that we need to eliminate.
Actually we have these 4 prerequisites of Nitro:
- One pattern has one hbs-file
- The hbs-file needs to have exactly the same name as the pattern (with a little flexibility of hyphens and camelcase recognitions/replacements)
- A Mainpattern needs to be in the same folder with the same name as the pattern has (e.g. teaser.hsb needs to be placed into teaser/teaser.hbs)
- Variants of a pattern needs to be in the same folder as a mainpattern (e.g. teaser-blue.hbs needs to be placed into teaser/teaser-blue.hbs)
Please eliminate these conditions above (at least point 3 and 4) to reach a higher flexible framework that could also be used outside of the Nitro world. In addition the nitronet-config.json needs to be updated because the current configuration with the nodes is not very reasonable.
NitroNet has to be configured in such a way that only the file name is crucial and the file location and folder structure can be ignored.
NitroNet supports only the precise project-structure of Nitro. That's a current requirement that we need to eliminate.
Actually we have these 4 prerequisites of Nitro:
Please eliminate these conditions above (at least point 3 and 4) to reach a higher flexible framework that could also be used outside of the Nitro world. In addition the nitronet-config.json needs to be updated because the current configuration with the nodes is not very reasonable.
NitroNet has to be configured in such a way that only the file name is crucial and the file location and folder structure can be ignored.