Thanks for your offer to help, Louise!
Right now, it is not so easy to edit the web site. I use an HTML editor,
but have to know a little code, and FTP, and it's sorta technical. What
Dale and I plan to do is migrate the content to WordPress. We understand
that it's pretty easy for any authorized user to edit a WordPress site.
I don't entirely agree that StJohnW needs updating. I leave some of the
older postings, like the Harvest Fest, up because they give a flavor of
what we do. My intent is to have a balance of parochial news and some of
wider context, Jesuit Pope, Millennium Development Goals, etc. On the
other hand, it would be wonderful to have fresh copy on our music, our
ministries, our leadership.
To implement this plan, I've gotta learn new stuff, like installing
WordPress on our 1&1 hosting platform. It'll happen one of these days,
in a burst of coding enthusiasm.
----------------
Step 1
WordPress installation requires a MySQL database. If you have not set up
a MySQL database already for the Wordpress install, you will need to
Create a New MySQL Database.
and on thru Step 12...
> <
http://garymatthews.com/2013/__03/10-more-reasons-to-choose-__weaver-ii/
> <
http://garymatthews.com/2013/03/10-more-reasons-to-choose-weaver-ii/>>
>
> I came across this because my church,
http://cccambridge.org/ ,
> is shifting to this template after frustration with prior design
> that could not be edited by the client (I looked into it for the
> rector, found the proprietary design nearly incomprehensible).
> If you examine their WordPress/WeaverII site, you'll find an
> awful lot of infrastructure. Too much of this is devoted to
> pandering to users of ancient browsers. (My own practice is to
> ship clean HTML and let the browsers make of it what they are able.)
>
> Anyway, this is the direction I think we are moving...
>
>
> --