Long-term plan for the website

Post Reply
indolering
Posts: 801
Joined: Sun Aug 18, 2013 8:26 pm
os: mac

Long-term plan for the website

Post by indolering »

When I last tried to hack on the website, people didn't care for patches that included libraries because they made for really ugly Git commits and Phelix didn't like the idea of using PageSpeed or other server-side optimization solutions.

I am also concerned about multilingual content. The current PHP based site would require that we roll our own solution. Moving to a CMS would require a DB and break the Github workflow.

The Github workflow and maintenance concerns clearly point to the use of a static site and I would like to convert the main site into a Jekyll site. This would modularize the structure, simplify reviews of new content, bring blog posts into our Github workflow, and ease the creation of multilingual content.

The main repo would contain only the precompiled Jekyll site, ensuring clean Git commits. The deployment server would use jekyll-hook to compile the site using a webhook. This would ensure we have control over the site, our TLS keys, and enable us to use plugins. If we chose to fork Bitcoin's excellent developer guide, we will need the ability to use plugins.

For the initial reimplementation, I would try to match the style, content, and layout of the current site. I think I can even remove the jQuery dependency. WRT i18n, there are multiple solutions for creating multilingual content with Jekyll and I want to wait until I've (re)created the site before deciding which is the best.
DNS is much more than a key->value datastore.

biolizard89
Posts: 2001
Joined: Tue Jun 05, 2012 6:25 am
os: linux

Re: Long-term plan for the website

Post by biolizard89 »

I'm not particularly familiar with Jekyll, but I would support removing the depencency on PHP (static content is easier to audit for security issues). From my limited knowledge Jekyll seems to be the standard solution for a static CMS, so I'm fine with this proposal. Note that my opinion carries little weight since web dev isn't something I've tinkered with for many years.
Jeremy Rand, Lead Namecoin Application Engineer
NameID: id/jeremy
DyName: Dynamic DNS update client for .bit domains.

Donations: BTC 1EcUWRa9H6ZuWPkF3BDj6k4k1vCgv41ab8 ; NMC NFqbaS7ReiQ9MBmsowwcDSmp4iDznjmEh5

josephbisch
Posts: 69
Joined: Sun Nov 23, 2014 3:34 pm
os: linux

Re: Long-term plan for the website

Post by josephbisch »

I use Jekyll for my website. I think it keeps things simple and makes it easy to work with a website. My vote is for using Jekyll.

indolering
Posts: 801
Joined: Sun Aug 18, 2013 8:26 pm
os: mac

Re: Long-term plan for the website

Post by indolering »

josephbisch wrote:I use Jekyll for my website. I think it keeps things simple and makes it easy to work with a website. My vote is for using Jekyll.
Yeah, part of the reason I want to use Jekyll is to get experience with it before forking Bitcoin's developer documentation.
DNS is much more than a key->value datastore.

Post Reply