Yup, we’re releasing a generic “Client CMS” app that pro users can use for free. We just want to make sure we debug the existing app before releasing to clients. It’s hard to keep track of second hand “client” bug reports. :)
Hey there. This can be done by targeting the body class from inside PageLime. Using CSS you can create a tooltip or a small text area to instruct your users.
We’re starting work on “Widgetizing” Pagelime in August.
Guys, the problem here is that we'd have to compromise the simplicty of Pagelime as a add a "cms-editable" and everything works for some of these to work elegantly. However some of this is going to start rolling out, but it will require the "web services" integration method and some coding. Our goal was to NOT have the Wordpress learning curve, and once we start doing that, we're going to run into issues supporting it, as we're not an open-source product and receive 100s of support emails daily, and we handle all of them (even the free account ones). With a complicated, coding-required plug-in, we simply can't support it at the price point we're offering.
That said, we've been polishing our API and SDK behind the scenes, and our first piece rolling out will be our Heroku add-on soon. A blog-like plugin will be following, but it will be dead simple.
We've also been working with Wufoo for a form editor, but their approach doesn't work very well with our visual editor, so we're a bit blocked on that until we figure out a way around that.
Dave I love the idea. And we'll probably add something in the future, if not a standalone app that integrates with Pagelime. As of right now, we're focused on Content Management. Check out notableapp.com if you need something right now, it seems like it will fit the bill.
I thought about this, but there's actually a few simpler solutions. Let me explore what this would take though before I apply a flag to this.
There's two challenges here:
1. Without live preview, it's tough to know what the page will look like before publishing.
2. If there are more than five or six fields, it starts looking like a very long form, and it's hard for people to figure out which field maps to what.
Overall this is not a user-experience path we're satisfied with. We would prefer to find a way to make the in-page / inline editing more user friendly instead.
Chris - we are planning a feature called "shared regions", where you can tag areas with a class "cms-shared", in which case, PageLime scans the entire site for areas with the same ID and that class, and publishes all of them. Though, ideally for a scenario where a region is shared, you should use our include handling system:
48 votesAdminKJ (Support, PageLime) responded
Running this by Tom.
Sounds like a good point. We'll take a look at renaming the button.
I like the concept! I don't know if it should be a code level thing. Perhaps it could be done as a per page permissions screen. It would take some manual configuration per page to get the permissions set up. Tom and I will walk through this and white board some ideas, and probably share them on the blog.