Add `lektor dev new-theme` command

This command should be very similar to the existing lektor dev new-plugin command, and use the same style prompts to query for basic information that will be used in creating a very basic theme. This theme should then be placed in themes/ with a specified name, and contain a theme.ini. The theme.ini should be populated by the answers to the prompts.

I think there should also be a trivial amount of content in the new theme. Perhaps a single layout.html template file with very basic contents.

Like lektor dev new-plugin, this new command should be able to accept a --path option, and a theme_name argument.

[lsrdg]

It does make a lot sense now. 🎉

After cleaning the mass (setup.py, theme_module, etc) I’m working towards the creation of theme.ini and how to populate it. Thanks for the explanation and for double checking everything.

[nixjdm]

@lsrdg Sure, I expect the tests will come at the end. They’re just ready when you get there. 😃

We probably don’t need a themesystem.py. Taking a look at pluginsystem.py, I don’t think any of that is really relevant for themes. Themes don’t have any python, and really are much simpler because of it. We don’t need to load them in the same way as plugins, there’s no event hooks, and there’s no class Theme that needs importing in a theme module. Themes won’t have a setup.py or module.

I double checked and searched the code base for pluginsystem to look at all of the imports. I don’t think themes will have any corresponding imports. That should save quite a bit of complexity. The only python files you should need to touch are devcli.py, test_devcli.py, and quickstart.py. If you do think of a helper function, it could go in themesystem.py, but you don’t need to copy pluginsystem.py.

Make sense?