Erb include other template

I-C maybe you should ask Liquid about those shortages and ask them what they think about fixing it. It seems like Jekyll is in a pretty committed relationship with Liquid at present. Are there specific limitations imposed by Liquid that could be solved merely by using a different template system? ERB is significantly more complex than liquid, and choices in templating languages make things exponentially more complicated for new users which to choose, the need for double the documentation, etc.

Is the goal of Pages to be a static site Rails? To be an all-purpose static site generator like middleman? Zen-like simplicity? For me, it's closer to "simple publishing", than "publish any type of content, in any potential representation". Restricting Ruby to Safe Mode or even ERB would only make it slightly more useful than Liquid which in-total would make it really not worth it at all. ERB is significantly more complex than liquid, and choices in templating languages make things exponentially more complicated for new users.

I would think ERB would be less complex since it doesn't need parse anything more than extraction, the rest is done by Ruby itself, this makes it 1. Faster and 2.

Less Complex. I like this a lot, a pluggable engine gives users the best amount of flexibility while casting it out of your hand to make the decision for them. It lets us say "we like Liquid, there is ERB plugin. Less complex for us, more complex for the user all of Ruby, versus a purpose-built templating language. It's not really about raw functionality - you can do all this stuff with Liquid - but it's about a the constant minor annoyance of it all, and b all the slowdowns you get from having to do complicated stuff in multiple operations or loops that other templating engines can natively do in one pass.

Any template engine we add would have to not be able to execute abritrary code, include all the Jekyll functionality and be vetted a lot before enabling it in safe mode. Adding another template engine requires us to abstract all our docs to say "if you're using Liquid You just enable ERB and don't provide them with any support :.

I think Liquid is perfect for default Jekyll, I like Liquid, but I think if users want ERB or Handlebars, why can't we give that to them through pluggable template engines? Plugin is the way to go. Thanks for the conversation. Bear with me as I try to digest and synthesize all the comments Following up on that, do we know who Jekyll users are? More specifically, do we access to data survey or otherwise which describes Jekyll users' languages and templates of choice, or their experiences and opinions about using Liquid?

Creates a new compiler for ERB. See ERB::Compiler. Executes the generated ERB code to produce a completed template, returning the results of that code. Generate results and print them. Can be used to set eoutvar as described in ERB::new. It's probably easier to just use the constructor though, since calling this method requires the setup of an ERB compiler object.

Home Core 2. Home Classes Methods. In Files erb. Parent Object. EOF puts template. Responds to Ruby commands Rubies, of course! Check out the documentation and code examples here. Bridgetown includes access to some helpful Liquid filters as helpers within your ERB templates:. These helpers are actually methods of the helper object which is an instance of Bridgetown::RubyTemplateView::Helpers. You can add an.

When authoring a document using ERB, you might find yourself wanting to embed some Markdown within the document content. Alternatively, you can author a document with a. Continue reading for additional information. If you have familiarity with other Ruby site generators or frameworks, you might instinctively reach for the solution where you use a double extension, say, posts.

Of course you can also set the permalink to anything you want, regardless of the filename itself. The second option is to switch template engines using front matter or site-wide configuration. That will allow you to write posts. Find out more about choosing template engines here.