The Colour Collection - 6 New Themes for Elements

The Colour Collection is a new set of six Elements themes designed to bring colour and personality to your next project. A sample project is also included to help showcase the colours in your chosen theme.

  • Amethyst
  • Blueberry
  • Matcha
  • Seafoam
  • Tangerine
  • Strawberry

:backhand_index_pointing_right: Get The Colour Collection (Link requires Elements 2.x to be installed)

Watch the video below to learn more about the themes and included project :smiling_face:

1 Like

I like it’s possible to copy and paste to my own projects.

1 Like

Is the sample project also available outside the purchase?
Because this project is very handy to see what the defaults of a theme are and to see what the consequences of the changes are when I change something in the theme.

I also would like to obtain the project file.

Good themes to learn and copy into other projects. I may not like all the colours, but the components used are interesting to see.

Great video as always - need to use theme studio more and customize it….

No, it’s only part of the Colour Collection pack :slight_smile:

Okay, I understand :grinning_face:.

Sorry to be a pain, are we getting the projects to open when purchasing premium themes in “NEW PROJECT” section? I still don’t see the ones for Carflip and Gallery Pro. TIA

Your question actually raises an ongoing Elements problem: naming. Carflip and Gallery Pro are Components. For some reason, Essentials is a Template (which is a set of Components). Then we have Projects, Themes, and Resources.

In the All Products view in the Store, which is which is buried in the underlying text description. We do have the ability to look at Templates, Components, Projects, Themes, and Resources separately, but I’ll bet that most user behavior is the default, All Products.

So to @PMUK’s question: we also don’t have any standard as to whether a Component or Theme could, should, or must include a Project. This actually speaks to the documentation side of the store: there’s very little, and no standard for it. A simple point: in Updates I’m told I have an update for the MicroBlog project, but no way to see what that update includes. I can get to the update information via looking at in the Store section, but not in the Library section where Updates live, and where I’d be more interested in what the update actually is about.

But that brings us back to this: the Description for Colour Collection (Themes) says “a sample Project is included.” So it’s buried. But to @PMUK’s point, you’d have to read the description for a Component in order to know whether a Project was included, and you’d also have to infer that it isn’t by its absence in the Description.

That’s a long-winded way of saying: (1) there should be an Includes section in the cards for things in the Store; (2) there needs to be a standard for README.MD files to be added that include instructions for use.

1 Like