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
CMS Agnostic Support / Starter Kit #134
Comments
Hi, I added a cms boilerplate https://github.com/christianwiedemann/cms-boilerplate to become a more detailed vision of how a generic CMS build could work. Maybe we should rename this issue to CMS Starter Kit. Would be great if you can check it out and run
The goal should be a generic app that handles generation assets in a CMS independent Inside the wingsuit.config.js you can configure paths etc. I used your example as test folder structure. |
Sorry for the delay getting back to you on this and THANK YOU for the hard work on this feature - it will help tremendously and I think be of real interest to the Craft CMS Community and any other CMS based on Twig templating. I have just tested it out and it works well. I think it might be worth getting some more eyes on the feature though. @khalwat might be able to advise further on how this could best work with his Craft CMS Scaffolding. Andrew: this is a Design/Pattern Library called Wingsuit that uses TailwindCSS - this new feature is influenced by your Craft CMS Scaffolding file structure. Components can get generated and transferred into the craft templates folder and a 'dist' folder can be defined to. |
Question |
'extract' or 'hot'. Hot is used inside storybook. All CMS I know needs extracted CSS files. |
Thanks @christianwiedemann that makes sense. |
Hi @danleecpi. You can now use |
Is your feature request related to a problem? Please describe.
Just following on the conversation regarding the "app" starterkit for CraftCMS. @iuscare feel free to add your thoughts below as you seem to have the most experience working with Wingsuit and Craft.
Describe the solution you'd like
Craft CMS allows you to build templates using twig. Craft templates live in the "templates" folder at the root of the install.
craft/templates
If there was an automated process that ported over components on save into a subfolder of a Craft templates folder from Wingsuit that would be amazing. It would then allow utilization of the components to build modular templates more quickly and with instant previewing and debugging in the CMS.
@iuscare might have some insight into how he is doing this currently - but an out-the-box config would be great and allow Craft groupies to get started quickly.
A few thoughts on how this could work
My Example Local Dev Setup
For context, this is how I have placed Wingsuit and Craft CMS side by side for local development.
The text was updated successfully, but these errors were encountered: