Shopify is my preferred platform for ecommerce. I've worked with Magento, BigCommerce, WooCommerce, OS Commerce, Zen Cart, Big Cartel and a few others and Shopify comes out on top in the market of small to mid sized retailers.
I continue to use and love Shopify because it's good at one thing - beautiful, easy to build, ecommerce sites. Store owners bootstrapping a start up can create a site in just a few days by using a reasonably priced theme. And because the code base is pretty much wide open, it's a great tool for designers and developers too.
Unfortunately, with Shopify's eyes on ecommerce, some common web functions are missing - like an editable photo gallery, which get's me thinking...outside the box. Shopify has a great blog function that allows for an infinite number of blogs. Which in turn allows for an infinite number of uses. All four of the pages below were made with Shopify blogs.
Using Shopify blogs for functions other than a blog open up a lot of possibilities. As you can see above, the blogs function was used to build a beautiful blog, listing of events, press announcements and a friends page. The best part of using the blog function was allowing the customer to take control of the content, essentially making each page a flexible CMS.
This article is more for inspiration than a how to guide. Generally speaking, when I use the Shopify blog function for pages other than a blog, I usually hide dates, authors and other non-relevant information. Sometimes I hide tags all together, other times I use tags to create a menu system within the page (like the events page above). And I rarely need the article page, so I simply don't link to it.
- Blog posts appear in search results by default, which may not be the intended behavior when using for a press or friends page. You can edit the search algorithm to exclude specific blog posts.
- Pay attention to the order of the posts. I found this to be surprisingly difficult. Of course you have published date, but this didn't work for me and the events page as most posts were in the future and would have confused the client. I trained the client to use date text (20160325) in the title of the post and hide the first 8 characters of each title.