will update automatically if the framework is updated
you are dependend on a third party, which might go down without notice
the third party might track your users
File in static/css/
Download the stylesheet and put it into the sites static folder as static/css/stylesheet.css.
If this file exists then the option stylesheetUrl from the config will be ignored.
full controll over what is part of your site
you can overwrite the file if you want
you can use your own stylesheets, even if they are not publicly available
you can get creative with using git submodules or makefiles to automate the process
changing frameworks is more work
foreign css-code is now in your repo
There is only one standard parameter for posts: If you want a cover image, add it like this:
Most of the time the path will just be coverimage.jpg or so.
This assumes that your posts are organized as page-bundles (which is the most sensible way anyways).
Have a look at the exampleSite to see how this would look.
Ideas for improvement
Add ci tests
Automatically create Screenshots in the CI
Have versions of the demo site online for different css-frameworks
Make sure the project can be internationalized well