# How is Elements different to Classic?

**URL:** <https://forums.realmacsoftware.com/t/how-is-elements-different-to-classic/47463>\
**Category:** Elements\
**Created:** [May 8, 2025, 10:53am UTC](https://forums.realmacsoftware.com/t/how-is-elements-different-to-classic/47463 "2025-05-08T10:53:56Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nigell1](https://avatars.discourse-cdn.com/v4/letter/n/48db29/32.png) [@Nigell1](https://forums.realmacsoftware.com/u/Nigell1)\
**Post date:** [May 8, 2025, 10:53am UTC](https://forums.realmacsoftware.com/t/how-is-elements-different-to-classic/47463/1 "2025-05-08T10:53:56Z")

</div>

Hi, I’ve read everything and watched the videos but I still don’t understand why [Elements](https://elementsapp.io/) is better than Classic.

What does it give me that Classic doesn’t? Do the sites look better, are they easier to make and so on. Can I see some.  
Sorry, but I can’t buy if it just seems, to me, the same but different.

---

<div class="post-metadata">

**Author:** ![Godber](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/godber/32/26521_2.png) [@Godber](https://forums.realmacsoftware.com/u/Godber)\
**Post date:** [May 8, 2025, 11:12am UTC](https://forums.realmacsoftware.com/t/how-is-elements-different-to-classic/47463/2 "2025-05-08T11:12:35Z")

</div>

I thought the same…but after using [elements](https://elementsapp.io/) now classic seems so complicated and I doubt I would go back

---

<div class="post-metadata">

**Author:** ![Heroic\_Nonsense](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/heroic_nonsense/32/20666_2.png) [@Heroic\_Nonsense](https://forums.realmacsoftware.com/u/Heroic_Nonsense)\
**Post date:** [May 8, 2025, 11:36am UTC](https://forums.realmacsoftware.com/t/how-is-elements-different-to-classic/47463/3 "2025-05-08T11:36:14Z")

</div>

Hi @Nigell1,

Depending on if you’re used to Classic combined with the Stacks plugin, or just plain vanilla Classic, [Elements](https://elementsapp.io/) can differ in various ways.

**If you use Classic _with_ the Stacks plugin**  
[Elements](https://elementsapp.io/)’ concept is similar to that of Classic+Stacks, in that you drag and drop functionality on an initially empty page. So paragraphs, images, columns, videos, form field items… those are all ready-made drag-and-drop items that you can position anywhere on the page.

What’s different to Classic+Stacks is that [Elements](https://elementsapp.io/) produces much leaner sites compared to Classic+Stacks, and that [Elements](https://elementsapp.io/) is truly what-you-see-is-what-you-get - the page looks like how it will end up while you edit it, compared to the schematic overview that Classic+Stacks offers (and the need to preview your work in a preview windows or browser every so often). Stacks (the bits and bobs, not the plugin) are actually tiny programs that generate code as you publish, and that code is often repeated every time you use that specific stack (some good devs have solved this, by the way).

One aspect of Classic+Stacks for the more serious web builder, are frameworks. These offer a centralised collection of settings that all stacks that are compatible with that framework draw their settings from. So for example, if you need to change the colour of all the text on your entire website, a framework allows you to do that with a click of the mouse. Frameworks are additional add-ons in Classic+Stacks, and are some of the more expensive addons at that.

[Elements](https://elementsapp.io/) offers its own way of doing this, so frameworks are no longer needed in [Elements](https://elementsapp.io/).

**If you use Classic _without_ the Stacks plugin**  
[Elements](https://elementsapp.io/) no longer uses the method of choosing a theme, add different page types and then putting your content on that page. Instead it offers you a blank canvas, and you create your own layout from scratch. This gives you much greater freedom compared to the old ways.

Cheers,  
Erwin

---

<div class="post-metadata">

**Author:** ![Nigell1](https://avatars.discourse-cdn.com/v4/letter/n/48db29/32.png) [@Nigell1](https://forums.realmacsoftware.com/u/Nigell1)\
**Post date:** [May 8, 2025, 2:54pm UTC](https://forums.realmacsoftware.com/t/how-is-elements-different-to-classic/47463/4 "2025-05-08T14:54:18Z")

</div>

Thanks. One thing that was mentioned in a YouTube video but I wasn’t clear about. It said, I think, edit in a browser. Does that mean a browser like Safari, so you can edit from anywhere, or is it an app like Classic, so I have to have it on my machine to update?

---

<div class="post-metadata">

**Author:** ![thominator](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/thominator/32/35233_2.png) [@thominator](https://forums.realmacsoftware.com/u/thominator)\
**Post date:** [May 8, 2025, 3:27pm UTC](https://forums.realmacsoftware.com/t/how-is-elements-different-to-classic/47463/5 "2025-05-08T15:27:49Z")

</div>

[Elements](https://elementsapp.io/) is a macOS application. You generally create/edit in the application. But as today’s video described (but didn’t fully show), [Elements](https://elementsapp.io/) also has a CMS capability built in, and RealMac is committed to having an online editor for CMS data.

What that means is that you can design the site with the [Elements](https://elementsapp.io/) application, then add material to the site via the online component. I plan to do this for blog, articles, FAQ, and a couple of other things, e.g. do the design in [Elements](https://elementsapp.io/), and then populate with the online component.

---

<div class="post-metadata">

**Author:** ![ben](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/ben/32/28488_2.png) [@ben](https://forums.realmacsoftware.com/u/ben)\
**Post date:** [May 8, 2025, 5:49pm UTC](https://forums.realmacsoftware.com/t/how-is-elements-different-to-classic/47463/6 "2025-05-08T17:49:55Z")

</div>

> [@Nigell1](#):
>
> One thing that was mentioned in a YouTube video but I wasn’t clear about. It said, I think, edit in a browser

Are you talking about [today’s video](https://youtu.be/D3fdoQRlblc)?

If so, the CMS we’re building for [Elements](https://elementsapp.io/) will eventually allow you to edit content online, from any browser. However, we can’t say exactly how or when that will be available.

> [@Nigell1](#):
>
> so you can edit from anywhere, or is it an app like Classic, so I have to have it on my machine to update?

You will need to have [Elements](https://elementsapp.io/) installed to create your site — you can then use the CMS (when the online editing is available) to make parts of the site, such as blog posts, blocks of text, and images editable via any browser.

Hope that helps, but let me know if you have any more questions 🙂

---

<div class="post-metadata">

**Author:** ![Nigell1](https://avatars.discourse-cdn.com/v4/letter/n/48db29/32.png) [@Nigell1](https://forums.realmacsoftware.com/u/Nigell1)\
**Post date:** [May 9, 2025, 8:51am UTC](https://forums.realmacsoftware.com/t/how-is-elements-different-to-classic/47463/7 "2025-05-09T08:51:43Z")

</div>

Thanks so much. Perfect. Then I’m in. Making some of these points clear on the website of [Elements](https://elementsapp.io/) would make it easier to make a buying decision. Currently there is little there to say why I should change, other than describing what seems like technical differences, not practical ones. I self make my website, with very little technical knowledge, and the kind of information I need to make a buying decision isn’t there.

---

<div class="post-metadata">

**Author:** ![Quinnovator](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/quinnovator/32/10225_2.png) [@Quinnovator](https://forums.realmacsoftware.com/u/Quinnovator)\
**Post date:** [August 24, 2025, 8:43pm UTC](https://forums.realmacsoftware.com/t/how-is-elements-different-to-classic/47463/8 "2025-08-24T20:43:49Z")

</div>

I’ve used Classic for years. I made a number of sites, but pretty much ramped down to 1 (for most purposes). Key is that I’m not a bit twiddler, nor a designer. I’m a content person, that is ideas, services, etc. Still, I was enticed by the continuing messages to upgrade to Elements, so I gave it a spin. And, after several trials, I am staying with Classic for now. Why? If I were a designer, I’d be all over Elements. The ability to fine tune fonts, colors, components, whoo! But I’m not. I want to choose a look/feel, and dump my content in. That’s what I realized, and that’s why I’m sticking with Classic. I could be missing something, so I welcome any pushback, but it seems to be that Elements is the cats pajamas for designers, but for those of use who want to put a site up (and are too financially strapped to pay for a designer), I think Classic (sans Stacks, not even sure that that does!) is the tool for me. Change my mind!

---

<div class="post-metadata">

**Author:** ![thominator](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/thominator/32/35233_2.png) [@thominator](https://forums.realmacsoftware.com/u/thominator)\
**Post date:** [August 25, 2025, 11:09am UTC](https://forums.realmacsoftware.com/t/how-is-elements-different-to-classic/47463/9 "2025-08-25T11:09:52Z")

</div>

This is something I’ve been saying something similar about for a long time: with the Typography component not complete and the CMS components still in beta, using Elements for production sites is like working in an office where scaffolding, tarps, saw horses, and other bits are scattered about.

However, I’d tend to disagree with your contention some, too. It’s simple enough now to “design” the site you want in Elements, even if you’re not a designer. Given your comments, my guess is that you’re adding content to your Classic site by generating a new Styled Text page and typing away. That does change some in Elements, but it’s really only the things missing in Typography that are in the way at the moment, thus my harping on that.

---

<div class="post-metadata">

**Author:** ![Quinnovator](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/quinnovator/32/10225_2.png) [@Quinnovator](https://forums.realmacsoftware.com/u/Quinnovator)\
**Post date:** [August 26, 2025, 2:44pm UTC](https://forums.realmacsoftware.com/t/how-is-elements-different-to-classic/47463/10 "2025-08-26T14:44:17Z")

</div>

Thom, thanks for the reply. Yes, I take the styled page and dump content in (to be coarse ;). Not sure about your comment, tho’. A set of different types of common pages, all styled consistently to a design I think is suitable, is more useful to me than the freedom to tweak font size. I’ve been promised that in several month, there likely will be some sample sites, and to check again then. Will do so.

---

<div class="post-metadata">

**Author:** ![MichaelDroste](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/michaeldroste/32/37212_2.png) [@MichaelDroste](https://forums.realmacsoftware.com/u/MichaelDroste)\
**Post date:** [August 26, 2025, 3:48pm UTC](https://forums.realmacsoftware.com/t/how-is-elements-different-to-classic/47463/11 "2025-08-26T15:48:31Z")

</div>

Reasons to change:

The sites are finally ‘normal’ sized as you see exactly how they will look

Don’t know if you know but often times windows users see things a little different…

Now things are cleaner and easier to position exactly how you want…

The sites take up way less space on the server

The sites in elements are fast 💨 very fast

I does take a little time to learn something new - I decided not too - then Dan showed me how to redo my site in elements episode 92? And I saw how easy it was… - I switched 🙂
