Integrating maizzle in an existing project

[bernardarhia]

I'm working on an existing project. I came across maizzle two days ago. I want to integrate it into my app but when I run npx create-maizzle, I get this error
destination directory is not empty, aborting. Use options.force to override
at Degit._checkDirIsEmpty (/Users/Name/.npm/_npx/dfe834339ec2696c/node_modules/degit/dist/index-688c5d50.js:14171:12)
at Degit.clone (/Users/Name/.npm/_npx/dfe834339ec2696c/node_modules/degit/dist/index-688c5d50.js:14089:8)
at main (file:///Users/Name/.npm/_npx/dfe834339ec2696c/node_modules/create-maizzle/src/index.js:109:17)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
code: 'DEST_NOT_EMPTY'
}. I want to put maizzle in my root directory and not it'a own directory. How do I do that?

[cossssmin]

For now if you want to use create-maizzle just scaffold it in its own directory and then move it manually. The problem with allowing force copying is that it'll overwrite your NPM stuff (package.json/package lock/node_modules).

Are you using a specific framework or project structure? We should try to have guides around popular ones.

[bernardarhia]

I do have a specific folder struture. I tried doing the installing but it couldn't because of the overwriting stuff. I might have to do a microservice or something

[cossssmin]

Have a look at using the API: https://maizzle.com/docs/api

[bernardarhia]

I've found a work around it. I use maizzle to write the code and compile it using the dev or build command then I use the mustache library to compile the html

[asimpletune]

Hi everyone, I just wanted to follow up, because I came here with the same question and wanted to confirm a few things. Regarding the integration of Maizzle alongside an existing project, it seems like there are two diverging paths:

1. dynamically generating Maizzle templates
2. statically generating Maizzle templates

So for use case 1, the suggestion is to use the api.

Then for use case 2, the recommendation is to use the Maizzle tooling to generate the project scaffolding, and then to manually copy everything over to your existing project's directory structure, correct?

Here's an example directory structure:

/my-static-site-example
|-- /content        
|-- /templates      
|-- /static         
|
|-- /emails # Maizzle project for email templates
|   |-- /src            
|   |-- /config         
|   |-- /build_production   
|   |-- maizzle.config.js  
|
|-- package.json # Maizzle and the parent project should share a package.json and tailwind config
|-- tailwind.config.js  
|-- README.md          

And then from there to integrate the Maizzle dev/build pipelines into your project's existing npm scripts, makefiles, or whatever else one's situation calls for.

Did I understand that right? Thanks for reading.

[cossssmin]

For now yes, those are the options.

Note that you can define relative output paths (i.e. ../static/emails) so you don't need to manually copy the files that Maizzle generates.