Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installation Setup -> Configuration outsourcing from Extension Settings #638

Open
heyse-dc opened this issue Aug 22, 2024 · 3 comments
Open

Comments

@heyse-dc
Copy link

Is there a documentation how to outsource the path of the

  • mask.json,
  • Templates Frontend and
  • Backend
    e.g. inside the Typoscript of the sitepackage.
    Or may be all parameters inside Settings > Extension configuration > mask > General, Frontend, Backend?

That would make working with your own distribution much easier.

@nhovratov
Copy link
Collaborator

Unfortunately this is not possible right now. If you want to work on this feature you are welcome to approach me and we can talk about what needs to be done.

@heyse-dc
Copy link
Author

Thanks for your quick reply. What would be your first approach to realize this? Because from a development point of view it would be much bettter to have this configuration inside version control & co.
Better to implement mask as a core extension for Typo3 ;-)))

@nhovratov
Copy link
Collaborator

nhovratov commented Aug 22, 2024

Better to implement mask as a core extension for Typo3 ;-)))

@heyse-dc Have you heard of Content Blocks? :D https://github.com/nhovratov/content-blocks

I would make it like I did in Content Blocks and load it automatically, if it is within a certain Folder Structure. Then it could even be configuration-less. The remaining config could be loaded from a PHP file in the site-package by using a ServiceProvider factory.

For my part, I do no work on new features for Mask anymore and concentrate on Content Blocks. Mask will only be maintained for new versions of TYPO3 and as long people are using it. But if you still want to contribute, I would never say no.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants