<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>I've been using Jekyll and storing static content on s3. Sure you pay for some of it but my bills rarely get past 10$/month with a global cdn in front of it too<br><br>Sent from my iPhone</div><div><br>On Aug 12, 2016, at 10:15 AM, B. S. <<a href="mailto:bs27975@gmail.com">bs27975@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-15">
<meta name="Generator" content="HTML builder 1.0">
<title></title>
<!-- Converted from text/plain format -->
<p><font style="font-family: courier" size="2">
blogger?<br>
<br>
facebook?<br>
<br>
google plus?<br>
<br>
google apps / site?<br>
<br>
Such seem to have been making efforts towards meeting the needs of small <br>
businesses, perhaps they have evolved to a point you find sufficient. <br>
Working on the K.I.S.S. principle, and the likelihood of good <br>
documentation and help for any given thing.<br>
<br>
I would be surprised if each satisfactory blogging solution didn't have <br>
some form of 'contact me' present as well. Question will be, if such <br>
isn't exactly what is desired, is the effort delta to deliver that delta <br>
really worth it to her.<br>
<br>
<br>
Consider whether you need one stop shopping / one size fits all <br>
solution, or not. Just as your e-mail and web servers can be in two <br>
completely different places in the world, you could pick 'best of breed' <br>
for each class of functionality you need. e.g. <a href="http://www.mydomain.com">www.mydomain.com</a> == <br>
<a href="http://mywifes.blogger.com">mywifes.blogger.com</a>, and have a static contact form web page elsewhere <br>
at <a href="http://contactme.mydomain.com">contactme.mydomain.com</a>.<br>
<br>
<br>
You might google about around Google Sites / Apps <br>
<a href="https://apps.google.com/products/sites/">https://apps.google.com/products/sites/</a> to see what's what. There are a <br>
number of 'plugins' possible, you may be able to find sufficiently good <br>
while limiting such so that you don't have to swallow 'all <br>
possibilities' (and the accompanying maintenance burden). All while <br>
integrating with all google'ness, including the measures google evolves <br>
for security / abuse prevention. I'm not advocating google, but it may <br>
define a possibility range to look for / avoid when comparing other <br>
solutions.<br>
<br>
<br>
Thinking back to the <a href="http://kwlug.org">kwlug.org</a> platform discussion not long ago, there <br>
was some advocacy for what is essentially static web pages. There may be <br>
some merit in that - it sounded like 'create a document', 'git push', <br>
and get on with your day.<br>
<br>
<br>
On 08/12/2016 09:37 AM, CrankyOldBugger wrote:<br>
> I currently have my wife's website running on WordPress. It's hosted on a<br>
> very cheap (i.e. free) provider that I got in under the radar, so to<br>
> speak. I have two other sites with this same host. With the constant<br>
> barrage of security updates, site-related issues, and other WP annoyances,<br>
> I've decided that I no longer like WordPress. So I've been shopping around<br>
> for an alternative.<br>
><br>
> All three of my sites are using WP, as a matter of fact, so I could<br>
> experiment on one of my own sites before I start messing with my wife's<br>
> site (as it's for her business).<br>
><br>
> I started these sites with WP as they really are simple blog sites, and<br>
> back in the day WP was actually fun to use. Now it's a pain in the <place<br>
> where you don't really want pain>.<br>
><br>
> I was looking at Drupal but someone told me that it was very finicky and<br>
> needed constant fine tuning.<br>
><br>
> Her requirements are relatively simple:<br>
><br>
> 1) Low maintenance for me (i.e. without the constant barrage of security<br>
> updates that I finally gave up on and now ignore regularly)<br>
> 2) Some way for my wife to post new articles in a blog-like fashion from<br>
> her Ubuntu laptop or her Android tablet. Please keep in mind that while<br>
> she's very smart, she wants something very simple and easy to use (and she<br>
> doesn't want to learn any programming).<br>
> 3) We don't (at this time) need any ecommerce type stuff (we're not selling<br>
> stuff online), but we would probably be open to some simple tricks like<br>
> having a customer fill out a form with their contact information, that sort<br>
> of thing. So HTTPS isn't mandatory (although it wouldn't hurt).<br>
<br>
<br>
_______________________________________________<br>
kwlug-disc mailing list<br>
<a href="mailto:kwlug-disc@kwlug.org">kwlug-disc@kwlug.org</a><br>
<a href="http://kwlug.org/mailman/listinfo/kwlug-disc_kwlug.org">http://kwlug.org/mailman/listinfo/kwlug-disc_kwlug.org</a><br>
<br>
</font>
</p>
</div></blockquote></body></html>