[Rhodes22-list] Website Development

[Larry Gioia]

This may be a good description of how to integrate AWS Cloudfront / Wordpress / S3:
  
https://blog.lawrencemcdaniel.com/integrating-aws-s3-cloudfront-with-wordpress-2/
  
It probably requires the least technical experience (still needs documentation of how to maintain) but is subject to changes in or loss of support of the components that integrate Wordpress with AWS (not Wordpress itself, seems like it will always be stable) over the years.
  
Peter’s prototype is like the website my small company has created and maintained for 22 years: handcrafted HTML with CSS. Not subject to changes in integrated components, but does require more programming skills that are becoming harder to find.  It requires a person like Peter or myself who understand it. 
  
It’s difficult to decide: the trend is more toward integrating components vs doing underlying programming, yet the tools used go in and out of fashion. 
  
Several people have said to go the route requiring the least technical programming (which may be AWS/Cloudfront/S3 described in the link above) and it’s hard to disagree with them. 
  
Larry

> On Jul 22, 2020, at 9:55 PM, Mark Whipple <mark at whipplefamily.com> wrote:
> 
> I wouldn't be surprised if people who are well-versed in web development
> find Wordpress to be much less than ideal. That's because it's designed for
> people who don't know much (or anything) about web development. I've
> created Wordpress sites for groups and I've then taught one or more people
> how to maintain them. I like setting things up but I'm not a fan of
> maintaining them. Wordpress gave me an exit strategy.
> 
> Whatever tools are used for the R22 group site, I'd suggest that the site
> be documented so that someone with little or no experience can maintain it.
> Because sooner or later, that will probably need to happen.
> 
> Mark
> 
>> On Wed, Jul 22, 2020 at 8:46 PM Peter Nyberg <peter at sunnybeeches.com> wrote:
>> 
>> As I mentioned, the prototype replacement website that I developed was
>> done with hand-coded HTML and CSS.  Naturally, this was done with an eye
>> toward keeping the code maintainable and as simple as possible (but no
>> simpler).  The prototype can be viewed at
>> http://sunnybeeches.com/rhodes22/ and the code can be inspected by anyone
>> who cares to.
>> 
>> I’ll admit to not knowing anything about Wordpress, but two different
>> people have thanked me for NOT using it.  So,clearly, opinions differ.
>> 
>> —Peter
>> Currently anchored in Three Mile Harbor, LI, NY
>> 
>>> On Jul 22, 2020, at 10:32 AM, Frederick Lange <sloopblueheron at gmail.com>
>> wrote:
>>> 
>>> Mark,
>>> 
>>> Good advice.
>>> 
>>> I volunteer to administer websites for some nonprofits and a club.  These
>>> sites range from averaging 5000 visits a month to less than 100.
>>> 
>>> Most sites I have taken on due to the previous admin leaving this world.
>>> The absolutely worst nightmare is taking on a site that has been running
>> on
>>> a private server.  Next worst to transfer admin is a site on goDaddy, and
>>> it is overpriced.
>>> 
>>> The easiest is Wordpress.com.  It is very inexpensive for nonprofits who
>>> don't sell anything.  For content management, it only uses Wordpress
>> which
>>> is familiar to many.  So new talent is easy to find.  And support is
>>> non-geeky and effective.
>>> 
>>> Regards,
>>> 
>>> Rick Lange
>>> 
>>> 
>>>> On Wed, Jul 22, 2020 at 9:57 AM Mark Whipple <mark at whipplefamily.com>
>> wrote:
>>>> 
>>>> As someone who worked in IT for years before becoming a technology
>> teacher
>>>> I have one caution. Whatever you do, do it with the future list members
>> in
>>>> mind. Someone else is going to have to maintain this site down the road
>> so
>>>> I'd suggest favoring basic, commonly-used technology over cool new stuff
>>>> with bells and whistles. None of us will be list members forever and we
>>>> don't have any guarantee that anyone who joins the list years from now
>> will
>>>> have the skills that some of you possess. Just something to think about.
>>>> 
>>>> Mark
>>>> 
>>