Assuming one were looking to create a simple static file from scratch (e.g. a personal blog), why would one select Frozen-Flask over a traditional static site engine?

If you are familiar with building sites with Flask, I can obviously see the appeal, but for someone unfamiliar with Flask, is there any advantage to going the Frozen-Flask route over simply using a static site generator and content stored as flat markdown? One of the selling points of static sites for me was not having to include a database layer for something as simple as a personal blog with a few dozen entries that I wish to serve.

It's probably worthwhile to point out the distinction between general frameworks for static page generation and those that are designed for blogs. Overall the supported features are similar with the only difference being the amount of code that needs to be written and how opinionated the framework is regarding the project structure. This latter point pretty much defines whether a particular framework will work for your project.

I have a static site, which is published in two languages, currently with over 5000 pages and about 50 page updates and new pages added per day. None of the static blog frameworks were flexible enough even though my requirements are pretty minimal. I ended up using https://github.com/mtigas/django-medusa/ with a custom app, https://github.com/StuartMacKay/django-sitepaths to manage all the pages and allow pages to be easily regenerated. This works well, with little tinkering to keep it working however I'd certainly take a closer look at Frozen-Flask for my next project.