Add --init-templates and --start-theme Flags

[SkySingh04]

This PR introduces two new flags, --init-templates and --start-theme, to the Marmite CLI, allowing users to initialize project templates and themes more easily. The new flags add the following functionality:

• --init-templates: Creates a templates/ folder in the output directory, adding a base.html file as a starter template.
• --start-theme: Extends the --init-templates command by additionally creating a static/ folder with placeholder files (style.css, script.js) referenced by the templates.

To support these new flags, two functions were added:

• initialize_templates: Sets up the templates directory and base files.
• initialize_theme_assets: Sets up the static assets directory and initial CSS/JS files.

Both functions are currently in a new module, initializer.rs, but they contain only placeholder code for now.

Questions

Before proceeding with the complete implementation, we would like some input on how the initialize_templates and initialize_theme_assets functions should be implemented. Specifically:

1. Template Content: What content should be included in the base.html file within the templates folder? Should it be a full HTML skeleton, or just a simple comment indicating where customization can begin?
2. Static Assets: Should style.css and script.js in the static/ folder include specific starter content, or can they be empty placeholders?

Related Issue : #70

[SkySingh04]

@rochacbruno Could you please review this and answer my doubts?

[rochacbruno]

output_folder should actually be the input_folder in this case,
here we are writing templates, the output_folder is where we write the rendered files.

We want to write all the embedded templates with its contents.

Here you can use

marmite/src/embedded.rs

Line 16 in 8984168

pub struct Templates;

Something like

for name in Templates::iter() {
    let template = Templates::get(name.as_ref()).unwrap();
    let template_str = std::str::from_utf8(template.data.as_ref()).unwrap();
    # here you write to `templates_path.join(&name)` the contents of template_str
}

[SkySingh04]

Instead of writing to output_folder, initialize_templates now writes to input_folder. The function creates the templates directory within input_folder and iterates through all embedded templates using Templates::iter()

[rochacbruno]

Here you can call

marmite/src/embedded.rs

Line 45 in 8984168

pub fn generate_static(static_folder: &Path) {

But passing the input_folder.join("static"), if it does not exists yet

The output will be the embedded template, then user can customize before generating the site.

[SkySingh04]

The initialize_theme_assets function creates a static folder in input_folder (if it doesn’t already exist) and then calls generate_static(&static_path). This utilizes the generate_static function to populate static with embedded assets, eliminating the need for placeholder files

[SkySingh04]

@rochacbruno Your requested changes have been made!