You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What do you think about using Middleman for the website? That way we have a well put together development environment for building out the Inqlude websites. Also it would make the current work done on the website easy to integrate as it's all Ruby.
An example of a site built with Middleman: Project Atomic
Another advantage I can think of is that it makes contributing easy because the Middleman workflow is pretty straight forward.
The text was updated successfully, but these errors were encountered:
Well, inqlude basically includes a static website generator which is tailored to its needs. The site is generated from templates. Creating the website is just calling inqlude view. I'm not sure Middleman would add a lot because we still would need to have the automation for putting in the Inqlude data.
I added some info about how to generate the site in the README.
I'm sure Middleman provides a lot of useful stuff. I'm just not sure we need a lot for our use case. It's pretty simple and we have the tooling already in place.
An alternative could also be Jekyll which is one of the other very popular static site generators.
What do you think about using Middleman for the website? That way we have a well put together development environment for building out the Inqlude websites. Also it would make the current work done on the website easy to integrate as it's all Ruby.
An example of a site built with Middleman: Project Atomic
Another advantage I can think of is that it makes contributing easy because the Middleman workflow is pretty straight forward.
The text was updated successfully, but these errors were encountered: