Keith, thanks, but I have a few clarifying questions for you:
Are Part 1 and Part 2 two steps in a 2-step process to allow client
CMS, or are they two different options I can choose from to
give a client CMS privileges, using either Part 1 or instead Part 2?
Obviously, I’m confused being new to this.
Regarding Part 1: So with this option, I design a site in Freeway, and
the pages are content editable/manageable by my
client, even though they don’t own Freeway? But the client has to buy
WebYep server software, is that correct?
Thank you for all your help.
Patty
On Jan 7, 2010, at 12:01 PM, Keith Martin wrote:
Sometime around 7/1/10 (at 19:33 +0000) Colin Alcock said:
If you are still quite new to Freeway, I can recommend the WebYep
option
Not just if you’re new to Freeway either. I find it seriously
useful.
Patty, note that there are two parts to WebYep: (1) the WebYep
actions, and (2) the WebYep server software.
Part 1: You buy the WebYep actions once. This is installed into
Freeway, job done. All you need to do with it is use it in your
Freeway pages.
Part 2: You buy a new copy of the WebYep server code for each new
site that you want to make client-editable in this way. This is
tweaked to have your choice of client username and password for
logging in, then uploaded to the web site. (Dead easy, honest!)
The costs for both are absolutely reasonable, but it is worth noting
from the start that each new site you want to WebYep-ify needs to
have its own copy of the server software bought separately.
k
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options