liquid

In shopify I am using liquid templating to get blog posts which are related to products by their tags, like so: <ul> {% for article in blogs.blog.articles %} {% if article.tags contains product.handle %} <li><a href="{{ article.url }}"><p>{{ article.title }}</p></a></li> {% endif %} {% endfor %} </ul> However, if there are no related posts, I would like to display a message such as "No related posts!" My question is how would I do that? I have contemplated trying to get the articles into an array and testing if it is empty, but I am having difficulty finding out how this is done. Thanks! Try

For someone that updates posts very often it's necessary to have posts sorted from new to old based on last modification date instead of Jekyll's default sort by posted date. There seems to be no easy way of accomplishing this. I've read and tested pretty much all methods out there. Here's what worked (partially as expected): Used this gem https://github.com/gjtorikian/jekyll-last-modified-at but now I have to manually enter last_modified_at in each post's front-matter in order for Jekyll to sort the posts using this loop: {% assign sorted_posts = site.posts | sort: "last_modified_at" |

I've added a theming directory to my app as described here , using prepend_view_path . It works as expected. I can now add a view structure in my app under app/themes/my_theme/views Now, I want to be able to override erb templates by dropping in a .liquid file, which will render right off the controller action. For example, I want to override app/views/pages/home.html.erb : <h1><%= t 'it_works' %></h1> ...with app/themes/my_theme/views/pages/home.liquid <h1>It works with {{ "liquid" }}</h1> I don't want to have to specify an array of view paths (upkeep would be awful), but just add .liquid as

I'm having some difficulty getting Jekyll to use a particular theme and I think there's something fundamental I'm missing about how {{ content }} works with posts. So, in a generic Jekyll site, index.html has a layout specified in its front matter. When the site is generated, the layout includes index.html as {{ content }} . It's kind of inverted, where the page specifies the layout and then the layout calls the page, but simple enough. Posts, on the other hand, are all generated via a file, post.html , which resides in the _layouts folder even though it isn't really a layout. Like index.html