liquid

I have used collections in my Jekyll website for GitHub Pages. I'm trying to get Jekyll to see the Markdown files inside the collection folder, _projects . Here's a rundown of the file structure: root │ ├─ _projects │ │ │ ├─ project_1.md │ └─ project_2.md │ └─ /*Rest of the Jekyll folders and files, _posts, _includes, etc.*/ At the moment, I realized that you must put the Markdown files in the root, so Jekyll can be able to see and parse the files to display them when after you clicked a link that points to them via permalinks. But it cannot "see" the Markdown files if the files are not in the

I'm trying to build a form block for my liquid theme language. I have based my approach on this answer . How ever the answer seems to be incomplete. The problem is that protect from forgery and some other methods are unavailable. Causing an error: Liquid error: undefined method `protect_against_forgery?' for # This is my code: class LiquidFormTag < Liquid::Block include ActionView::Context include ActionView::Helpers::FormHelper def initialize(tag_name, markup, tokens) super end def render(context) form_tag("#") do super end end end Liquid::Template.register_tag('liquid_form', LiquidFormTag)

I want to be able to render Rails' CSRF stuff on a liquid template. I found two pages that give me some clues: http://robots.thoughtbot.com/post/159806314/custom-tags-in-liquid https://github.com/locomotivecms/engine/blob/v2.0.0.rc12/lib/locomotive/liquid/tags/csrf.rb My problem is that the thoughtbot link does not explain how to get register the controller in the first place. Then, looking at the locomotivecms source, I can see that the template is registered with a new context , but this is done in the helper. I don't think this approach would be appropriate for me because I want to be able

Is passing liquid variables as inline styles commonly frowned upon? Here is an example of my markup: <div class="span-8-12"> <h6> {{page.role}}</h6> <h1 style="color:{{ page.accentColor }};"> {{page.title}} </h1> </div> <article class="intro"> <p style="color:{{ page.txtColor }};"> {{ page.summary }} </p> </article> I am setting h1 and p colors using the liquid variables in my posts. I know I could pass the variable directly to a CSS file, but then'd i'd have to write even more markup and CSS. Is this method valid or is there a better method on systematically changing values of color based off

I can't find any documentation on how to add custom fields for the user registration forum so I tried something but didn't work: <div class="single-full-width customer"> <div class="login"> {% form 'create_customer' %} {% if form.errors %} {% for field in form.errors %} <p class="input-error-wrapper"><span>{{field}} {{ form.errors.messages[field] }}</span></p> {% endfor %} {% endif %} <p> <label>First Name:</label> <input type="text" value="" name="customer[first_name]" class="input-text-1" /> </p> <p> <label>Last Name:</label> <input type="text" value="" name="customer[last_name]" class=

The index page on my Jekyll site is meant to be exactly like a post with only one extra bit of code for navigating the other posts. I'm not really using it to generate a blog per se, but a bunch of press pages. Now within each post I am using kramdown to generate a table of contents like so: * This line is a placeholder to generate the table of contents {:toc} That works fine for all the posts, but when I try to use it on anything but a post, it doesn't generate. The output is simply empty. It doesn't show the raw kramdown above or anything, it just disappears and nothing (especially not a TOC

I am using cart attributes to add extra information for each product to the cart (from the product page). I am specifically using cart attributes over line item properties because the client needs to be able to edit this information in the order later on which line item properties don't allow . Adding the information works just fine, the problem comes in when a customer decides to remove an item from the cart because although the item is removed, the cart attribute remains since it is not specifically tied to the product (other than a naming convention that we give it.) So, is there a way to