New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Switch to ERB as the default templating language #705
Comments
I'm all in favor of moving the default to ERB. That seems to be a better standard moving forward for such a rich tool. But I still use Liquid for blog posts. And I really don't want to convert 50+ of them to ERB. So, as you mentioned, please don't drop Liquid support even if it isn't the default! |
Definitely no plans to drop Liquid, that would be far too disruptive. We'll always keep it as an option. |
I started my website in liquid, then dabbled with serbea, and then went to ERB. All have pros and cons, but for my team and most rails/roda converts, they're likely to expect ERB as the default. |
ERB as a default sounds great to me! I totally agree about Liquid being a tool to provide protection from authors or template developers such as Shopify originally intended it for. My vote for the full power of Ruby. |
Summary
I'd like to petition changing the default templating language to ERB for v2.0.
Motivation
ERB is way more flexible and feature rich. The primary motivation for Liquid in my mind is security in user-authored templates. That's not the case with Bridgetown sites which will almost always be completely authored by the developer.
Features like Bridgetown components are also only available in ERB/Tilt-based templates.
I think using Liquid as the default is a remanent of the Jekyll era and I'd like to petition we change the default to ERB while still retaining Liquid support for people who want to use it!
The text was updated successfully, but these errors were encountered: