Question for developer friends:

Question for developer friends:

Inspired by Bigi Lui's question of revamping his blog, in the comments section I came across Hugo. A static-site generator like Jekyll. This seems to be really cool, I love the overall concept, and I like the idea of rapid firing off blog updates using markdown and version control through git. I have 50 tabs open and I really, really like all of this. Perfect solution for TheBlog.

*BUT*

In addition to TheBlog, I have a need to create a user-generated content system (more ambitious than comments in a blog) to create and edit game data. Call this the GameEditor.

I really enjoy Python and so I have taken a quick look at both Django and Flask and I think I understand the pros and cons of either. I am confident that I could create the GameEditor in either framework.

Obviously I could also create TheBlog in Django or Flask.

But I am currently thinking I should go with Hugo for TheBlog portion, and then Django or Flask for the GameEditor portion.

But raises the question in my mind, am I introducing administration complexity? Essentially, I have a requirement from the GameEditor to already go with Django or Flask, so should I just go ahead and run the Blog that way as well?

Or would I be missing out on the blazing fast and cheap serving benefits of Hugo and that the overhead of running part of the site as Hugo and part Django or Flask not that big of deal.

Any comments or opinions?

Originally posted on Facebook on May 07, 2018.