While the recent “Step-By-Step” YouTube video on CMS2 Elements was excellent for building a blog and working with text, I haven’t been able to find a similar resource focused on handling images. This is a key feature for my workflow, as about 90% of my clients require image management capabilities.
My background is with Classic EasyCMS, but I recently purchased CMS2 Studio and am eager to transition fully. However, I’m struggling to grasp how image handling works in the new system.
Could someone create a step-by-step video or provide a detailed example of how to upload, manage, and display images using CMS2 Elements and Studio? A working demo, example or tutorial would be extremely helpful for making the switch from Classic/EasyCMS to the new platform.
I spent most of my weekend working with ChatGPT and now have a fully operational, simple CMS for Elements that doesn’t require licensing, per-domain costs, or any money at all, and it is self-installing. Directions are included.
While I have a CMS license for all domain/sub-domain uses through Elements, this one has few limitations. It is not blog-capable, and this package is a field-based CMS rather than a visual page editor. If anyone is interested, I will share it with them at the location where files can be left.
My CMS needs are entirely image- and text-based. I will use the Elements CMS for blogs if necessary, but this option is easier, in my opinion.
The Elements CMS has always been free and could be used across multiple domains and subdomains without any additional cost. What costs money is the use of the online editor for the CMS.
For all of my projects, I use only the app-based CMS, without using the online editor.
In my largest project, I use almost 1,500 Markdown files, which generate just as many pages. This means that the Elements CMS can definitely be used for larger projects as well.
So, you say that it’s free, UNLESS, you need multiple collections and AI features. What if AI can make that free?… I am very happy with Elements, but free is better than the previous results. Seems AI can develop the online editor as well, for free. As someone who has invested in Rapidweaver, Source, Foundation and Elements, I am tired of throwing money at every turn, and in some cases, desire a better playing field. So yes, I have asked chatGPT to make an online editor and have received the installable for this. We will see if this works. I have no desire to upset the hard work of our coders, but costs are becoming ridiculous.
Absolutely, you can use AI to create your own online editor, it’s really empowering to build you’re own solutions
However, if you do find that your vibe coded online editor is buggy or doesn’t have the features (or support you need). You can always switch to the official online editor.
I’d be keen to see what you build and how it works, keep us posted!
You make a very good point. I still use your CMS Editor, licensed for use across all my subdirectories. I make webpages for non-profits that are starting and have little to no funding. I never charge, and when possible, transfer them off my subdomain to their own host, where I will maintain their webpage. This would be incredibly expensive to buy CMS Elements Online Editors for every ‘client that’s transferred ’, which is why I have elected to use AI for them.
Last thought…. I expect to find issues within the AI path, but my needs are narrow and specific. It only needs to be sufficient for file and text handling. It doesn’t need to be professional, swank or awesome. It only needs to work. I have placed 2 directories on my iDrive: one that doesn’t use the ‘online editor’ and one that does. I have successfully used the second one. I have not yet tried the first. Links below.
Please check it out and provide constructive opinions. Please know that my choices here are not picky or about finding fault with CMS Elements. It is solely about the cost issue and providing clients with an alternative.
Yes, but as I said, I have not gone any further with this as yet. My intention is to see where its limitations are. For now, using a car dealership example, I am just sitting in the car parked at the dealership. I have not started it, driven it off the lot, and certainly not put it through its paces. And, when it is fully active, the clients may not want the CMS Elements version. This one seems simpler to use (as it is basic), and that is a benefit many would appreciate.
