It took a little while to get everything set up correctly, but I can say that the CMS is already working very well.
On my website, I’m using two different CMS instances on different pages, each with its own set of articles. I even implemented one as an accordion, and it works perfectly—you can even search through it. I still have a few questions about it, but I’ll ask those separately.
I also found a solution for the crawler issue, thanks to Ben’s support; he pointed me in the right direction. Anyone who’s interested can contact me.
I would be very happy to see new features added to the CMS soon (very soon!), and I’m sure there will be some that I can use.
Thank you very much for all the work so far, @ben, @dan, and everyone else who’s been working on it.
I’ll add to this: as I work on “v2” of my company’s website, I use the CMS for just about everything right now. That feels risky given the Beta status and comments that “things may change”. v1 of my site is built on “the old CMS” which is valuable because of the end-user’s ability to modify the site. The “new CMS” is not quite there yet, but the last two days I’ve started to really (for me) flex and use the CMS in scripts. I’m not going to pretend to know how I’d do that on my v1 site, but the architecture in place today with this CMS is allowing me to do cooler things that theoretically are easy to maintain. All this to say, it has been a few weeks of learning, and I’m still a rookie climbing the mountain, but I really appreciate Elements and its current CMS architecture. It is powerful.