Essentials Update. 10 New Templates. 20% OFF šŸŽ‰

We’ve just shipped an update to the Essentials templates, adding 10 new templates to help you build out blogs and team pages even faster. This update means we are now just short of 100 professionally designed templates in the pack :smiley:

If you’ve already purchased the Essentials pack, this update is included for free, just update the pack in Elements and the new templates will appear in your template library!

And if you haven’t picked up the Essentials pack yet, there’s never been a better time as it’s 20% off for a limited time to celebrate this update :tada:

:backhand_index_pointing_right: Get 20% off Essentials Templates.

If you haven’t picked up the Essentials Pack yet, here’s a quick video showing just how fast you can build a website from scratch :exploding_head:

New post list layouts:

  • Post List Sharp Image
  • Post List Image and Text
  • Post List Image Overlap
  • Post List Tall Cards
  • Related Posts List

New post headers:

  • Post Header
  • Post Header Centered
  • Post Header with Image
  • Post Header Image Overlay

Plus:

  • Team Grid with Square Images

You can preview all the new templates, as well as the existing ones, on the Elements Essentials preview site.

The new post list and header templates give you a lot more flexibility when designing blog index and article pages, whether you want clean and minimal or something more image-led.

To get the new templates, just update the Essentials pack directly in Elements and they’ll appear alongside the existing ones.

As always, we’d love to see what you build with them, and if there’s a template or layout you’d like to see in a future update, drop a reply below. :backhand_index_pointing_down:

Very good update - thank you very much!

Fantastic. I’m now a little confused as there are two names - both cms and blog headings. I think you used to call them blogs, then changed to cms, and now are blogs again. Forgive me if I’ve misunderstood. Are they the same thing? And how do I switch between the old style of blgo I’ve been creating and the new look? They look great. Thank

The ā€œCMSā€ templates are using the CMS components, whereas the ā€œBlogā€ templates are using just the core components, meaning you’d have to convert over those templates if you wanted to use them with the CMS.

Hope that makes sense :blush:

Hi Ben

So if you want just a standard way to create blog posts on the site just use a blog template, but if you want all the bells and whistles of the CMS (online editing etc) go for the CMS components?

Is that the only real difference?

The difference is that the CMS templates are using the CMS components, so they are hooked up to use the CMS.

Whereas the Blog templates are using just the core components, and are therefore not hooked up to use the CMS.

If you wanted to use the new Blog templates specifically with our CMS, you would have to do a little bit of work (place the blog template you want to use inside either a CMS Item or CMS Collection and then change the text content to use the CMS syntax e.g. {{item.title}}).

If you use the new Blog Components, do they automatically generate ā€˜pretty-urls’ for each blog post, or is this something that has to be set up somewhere else? I’m a RW-Classic user, thinking of updating to Elements. I have a large 12-year+ blog, and its fairly important I keep the same tidy URLs if and when I cross over.

Pretty URLs generally need to be enabled manually. However, there is clear and simple documentation for that.

Keeping the existing URLs from your old blog should not be a problem. You may need to add the appropriate .htaccess rules, but that would probably be the smaller part of the work.

I’m not sure which blog system you’re currently using, but in general, the idea of moving to Elements and ECMS 2.0 is the right one and definitely worth pursuing.

I have a few years worth of blog posts that i need to port to Elements (was using the Poster Stack) without going to in depth what would be the most efficient way to do that?

If you’re using the Poster Stack, then Poster should already be storing the blog posts in Markdown files.

In that case, you should also be able to use those files in Elements, and importing them should be possible — perhaps with a bit of manual work.

Great - thanks for clarifying :+1: