Murray *ACP* wrote:
The upside is that it's incrementally easier to make most changes using the CMS (and you *can* do this in an internet cafe, for example), than it is to find the page, open it, make the change, save it and upload the changes. Note that I said "incrementally" easier. In other words, I wouldn't do this for that reason alone.
The downside is that when you open a page in an html editor which deploys a CMS a lot of it can be server language so it takes you sometime to find what html code/css relates to what bit of server language!
Sure - it is a forest in there! My comparison was intended to imply CMS vs no CMS. If you restrict the site to always CMS, then I'd assume that the bulk of your work updating would be via the CMS admin as opposed to local editing. Opening a CMS-controlled page in DW gives me the shakes....
Murray *ACP* wrote:
If you restrict the site to always CMS, then I'd assume that the bulk of your work updating would be via the CMS admin as opposed to local editing.
Youre right......but sometimes you have the requirement to introduce additonal html structure to the site at a later stage which after you have striped out the guts of the page and replaced it with CMS code can be a bit tedious. With no CMS involved its just a question of shoveling in another <div> in the place where it's needed instead of having to locate additional files where the html is being pulled from. I guess that's something a client cant actually do for themselves though, fortunately.
Murray *ACP* wrote:
Opening a CMS-controlled page in DW gives me the shakes....
Yeah depends on it complexity. Perch just uses some simple tags but once you get into Perch you find yourself building more elaborate templates which makes life easier for the client but a bit harder for yourself as those templates are stored somewhere else and the page itself may only have one 'include' line at the top of it.
Hey Ho its all good fun though aint it!
I still think you should keep it simple. You can use CKEditor to do all of the hard work on a so-called text file without having to go to a full blown CMS site.
Using the above method will help you to ease yourself into CMS.
Have a look at the following example http://pleysier.com.au/ckeditor/, try it out, change and save the contents.
All that is required is a PHP environment, CKEditor (free of charge) and included files (plugins)
You can go the hard way or the easy way.
Good example. I have ckeditor integrated with Perch. BUT unless the client is very careful they can easily destroy the formatting from page to page using ckeditor in any CMS. I don't think clients are that careful. You can of course take away many of the formatting options from the editor but if the client was to delete a <h2> heading it would be replaced by a <p> tag, not desirable.
Perch offers lots of different text fields to lock down the potential damage that a cleint can cause but it does require a bit more planning at the outset and in some instances you really have no alternative other than to use an editor like ckeditor.
I totally agree, it is no Perch or any of the other CMS packages.
My point is, does the OP want all of the extra features or does he want the ability to change the content of one or two pages? You can use a tip-truck or a box-trailer to cart a cubic yard of garden waste to the local dump.
so it's been awhile but I decided after some extremely painful negotiations with my client to go with perch and I must be really stupid because I am finding it impossible to use and the support guys are really arrogant and unhelpful.
have you used it? maybe you can help me?
I am trying to put in a gig calendar and a gallery. which should be really simple but it's completely screwing with my head!!!
I don't even know how many times I have read the perch documentation now and it just isn't making sense!