Pulse CMS is wonderfully simple to implement and use, it also keeps getting better, a new update just announced.
The Basic is free and the Pro is very reasonable.
In these solutions where you have to alter code, how easy is that to do with a Freeway site? Doesn’t FW produce the code when you publish and then you can’t really alter it at that point.
Still deciding which solution to use. It has to be easy for the client to use (in one case, many people will be accessing different areas) and easy for me to implement!
Still deciding which solution to use. It has to be easy for the
client to use (in one case, many people will be accessing different
areas) and easy for me to implement!
A lot is dependent on the amount and type of control your client needs
to implement. Meaning, if granular control over who can and can’t edit
certain sections is required then WY may not be the best choice. If
all they need is the ability to provide each “editor” with their own
username/password but don’t need to restrict certain areas from
certain editors then perhaps WY will be just fine. You need to ask a
lot of questions and find out precisely what they need or expect. Once
you know that it’ll be easier to shave down the list of possible
candidates. Of course, what may be best for the client may require
more effort from you to execute. Also, try to look a year or so down
the road with regard to your client’s needs, because if you go with
something very basic now will they outgrow it in a year or two? These
are important considerations.
In the bigger picture of CMSs, WY is squarely on the easier end of
things both to use (client) and implement (designer), especially with
Max’s action suite.
OK. Thanks. and Max has been a lot of help so far, too.
Basically, the one site (the bigger one) will require coaches to update pages for their team. There are lots of teams and lots of different divisions. Update the standings as well as upload PDFs.
Other than that, probably the home page with announcements.
They need quite a few editors (not sure how many, yet) to be only
allowed to edit their own specific area and restricted from the rest.
WebYep is out. MojoMotor might offer some degree of editor control but
I’m not certain, you would need to investigate. If it does then it’s a
great option; simple to use, flexible, powerful, well designed and if/
when your client needs more power it’s a simple process to upgrade it
to Expression Engine (MM’s big brother). Or you could go straight to
EE (there is an action suite available).
Aside from Mojo and EE, look at MODx Revolution <http:// www.modxcms.com>. Very capable and free.
WebYeb does have multi editors in its latest version.
I just completed a site with various levels of editor capabilities, which runs to 50+ pages.
Choice of CMS depends a lot on the capability of the editors skill set. WebYep’s favour is it’s ease of use for the editor that has little or no web skills.
David
On 12 Nov 2010, at 20:00, Todd email@hidden wrote:
Actually, not true, if you mean not having separate logins for different areas. Latest WY does have that option. Not suited however for complicated sites needing specific kinds of detailed data oriented info that need a database structure.
If only one team involved then you just need to give multiple people the same login. If multiple teams are involved then you can have separate pages for each team and each team page would have a separate login.
I’m not 100% sure this will work for you but… I created a page in freeway and applied the PHP make insert page action to it. This action stripped out all the headers. Then in FW I created a page and put a php includes piece of mark up into and expandable html item. The client now edits the page I applied the PHP make insert action to. See the results here. Basically all the framework / navigation is in FW but the main content is edited ny the client in an html editor.
So, the client signs in somewhere and then just edits the pages in the browser?
That is basically how all these systems work.
Nathans real point was that the pages that are to be edited can be a folder structure unrelated to the site structure as the include can pull that page in from anywhere.
So you could have all Jimmy’s editable pages/sections in a Jimmy folder with a single log in for that folder.