Options for @scullyio/init:markdown and @scullyio/init:blog

🧩 Feature request

When generating a new blog it would be great to have some more Options:

ng g @scullyio/init:blog <options>

Description

I think it would be good to have at least three more configuration options when creating a blog, to define the basic module name, the source directory for the blog content files and the route for availability of the static pages.

Describe the solution you’d like

• baseName - The basic Name and prefix that’s used for the BlogModule and BlogComponent, etc. This should be set to blog by default (with this it wouldn’t break the current behavior)
• sourceDir - This parameter should define the source directory for the blog files (*.md). It should be set to blog by default (with this it wouldn’t break the current behavior)
• route - This parameter should define the route under which the blog sites are available. It should be set to blog/:slug by default (with this it wouldn’t break the current behavior)

A further benefit is that it would allow one to create multiple different blog areas:

ng g @scullyio/init:blog
ng g @scullyio/init:blog --baseName=“project” --sourceDir=“projects” --route=“project/:slug”

This functionality would also affect the generation of new entries:

ng g @scullyio/init:post --name="This is a new blog post"  # use `blog` by default, no breaking change
ng g @scullyio/init:post --name="This is a new project description" --target="project" # matches with `sourceDir`

What do you think?

[SanderElias]

I like the idea of having a ‘default’, However, it should be just a string (can be a multiline string) In there the app-owner can set his favorite defaults, and what he needs. as @d-koppenhagen stated, the blog user needs to touch the file anyway, they want to put in their content, otherwise, there is no point to the whole exercise, to begin with. By keeping the setting a string, it will not be that complex to handle.

Hmm, come to think about it. I think it would make sense to create a file with defaults. something like: defaultBlogHeader.yaml:

title: my-blog-post
thumbnail: assets/images/default.jpg
author: John Doe
mail: [e-mail]
keywords:
  - angular
  - scully
language: en

Then the schematic can just read this as a string and inject it in the result.

ng g @scullyio/init:post --metaDataFile='defaultBlogHeader.yaml" title="whatEver"

[d-koppenhagen]

I still don’t know about those flags. The validation of such an option with complex configuration seems to be tricky to me and not really handy. As I wrote before: don’t you have to adjust the post anyway after setting it up? So is it really worth it to remember the syntax passing a KVP into the option and writing it on the command line easier/better compared to setting it up using the default meta config and just adjusting it as you will adjust the post file anyway and fill it with content?