Editorial changes and new blog posts to DB4S website.

[richb-hanover]

Here's my take on an updated DB4S website. All comments are welcomed. Interesting changes are:

• Revised home page.

  • New "elevator pitch". Four sentences, five lines. Tells the most important part of the story right at the top
  • Updated screen shot to show modern macOS; moved it below the elevator pitch
  • Other editorial changes to the page to eliminate redundancy
  • Revised the CSS to tighten up the appearance of blog posts

• Two new blog posts:

  • Code signing for Windows is in the works
  • Mention 3.13-rc1, but more gently than a full "announcement"

• About page:

  • added a place to mention current contribuors

• Download page:

  • Fixed a typo

• README for the repo tells how to add pages, and how to run Docker

Possible future To-Do's:

If I were to do any further work on the repo, I would ask for guidance before doing the following:

• Remove all vestiges of blogdown - is it needed at all?
• Remove redundant CSS file? (main.css and mainstats.css - seem to be duplicates)
• Also review CSS files - there seem to be a few duplicate declarations
• Maybe remove blog postings from the home page (perhaps provide link to Blog page)
• Is it necessary to track /docs in Github? That would remove a source of big diffs that aren't necessary

Thanks.

[richb-hanover]

Updated the Dockerfiles to handle both interactive development and building a final site.

[justinclift]

Remove all vestiges of blogdown - is it needed at all?

Nah, happy to have it ripped out. That'll make things easier for others to work on this too. :smile:

Remove redundant CSS file? (main.css and mainstats.css - seem to be duplicates)

Go for it. Never noticed the redundancy before. :innocent:

Also review CSS files - there seem to be a few duplicate declarations

If the end result looks ok for people - and it sounds like there'd be pretty much no change - then I'm personally completely fine with it. :smile:

Maybe remove blog postings from the home page (perhaps provide link to Blog page)

Nah. We should probably have at least the most recent few on the front page, so people can see what it's updated.

Is it necessary to track /docs in Github?

When you say "track /docs", are you meaning keeping the generated version of the docs in GitHub?

We do that because it's super easy for deployment. "git pull" and we're done. :smile:

[richb-hanover]

Updates to the PR:

• I cut out as much of the "blogdown" stuff as I could. hugo-lithium still has remnants, but I don't think they have an effect.
• All blog links remain on the home page
• I switched the Dockerfiles to alpine:latest, and force Hugo 0.111.3
• I put a stake in the ground re: License - same as DB4S - GPLv3 and Mozilla
• re: Deployment... I left the /docs directory in the files to be committed. Although I think that deployment could be as simple as docker run ... hugo-build; git push ... (But I ain't gonna do the work, so I will step back from any further decisions.)

Further comments welcome. Thanks.

[justinclift]

Awesome, that's all workable, so just merged it. :smile:

Thanks heaps for getting this done @richb-hanover, especially getting it running without the need for Blogdown to be involved any more. :grin:

[justinclift]

k, it's been deployed. The updated website mostly looks ok, with the exception of the Stats page:

https://sqlitebrowser.org/stats/

The header and footer for that one seems to be busted. CSS not working or something?

Hmmm, I need to hit the sack soon so I'll leave this as-is for the moment. It's only a usability issue rather than a blocker.

We'll want to get it fixed in the next few days though. :smile:

[richb-hanover]

Yikes! You're right. I deleted the mainstats.css file which was (I now understand) the CSS file for the Stats page. Given that the main.css and mainstats.css files were nearly (if not completely) identical, I'll track it down and make a PR. Thanks for merging