Skip to Content.
Sympa Menu

discuss - Re: [opennic-discuss] New Homepage - Gathering Opinions

discuss AT

Subject: Discuss mailing list

List archive

Re: [opennic-discuss] New Homepage - Gathering Opinions

Chronological Thread 
  • From: Fusl Dash <opennic AT>
  • To: discuss AT
  • Subject: Re: [opennic-discuss] New Homepage - Gathering Opinions
  • Date: Mon, 20 Feb 2017 04:50:28 +0100

Hi Jonah,

I have to admit the design looks not bad but what is the reason we need
Jekyll for this?

I do understand if we'd be using Jekyll to generate multiple versions of the
same page in lets say different languages but this is static HTML content
generated by more or less static code that needs to be parsed and IMHO using
Jekyll for this is just overkill and should be removed.

There is currently two ideas on how we want to host the front page:

- As a simple overview and front page in the WikkaWiki
- As a static HTML page in GitHub that the auto-scaling pulls into Varnish
when booting new instances

We probably go with the 2nd choice as it allows us to take down WikkaWiki for
maintenance without having to break the frontpage as well and both systems
are going to be running independently.

On 2017-02-19 01:56, Jonah Aragon wrote:
> Hi!
> I've been working on a new design and system for the homepage, and I wanted
> to gather some opinions on what works, what doesn't, and what you think
> about replacing our current WordPress site (at
> You can check out my design at
> Some background:
> The WordPress site currently host a simple homepage, a basic membership
> system (essentially providing a profile frontend for the LDAP system), and
> a blog that's rarely been used. WordPress creates a lot of load on the
> servers and is just in general bloated. MySQL databases, dynamically
> generated pages, none of this is needed for our homepage, especially if we
> try to move everything to the wiki. In addition, the website (mainly the
> aforementioned login system) is susceptible to XSS attacks, among other
> vulnerabilities. Coupled with the massive amount of security holes that
> just appear to show up in WordPress all the time
> (,
> I'm honestly surprised we haven't migrated to anything else already.
> My site (code at is complete
> static HTML (which is compiled with Jekyll) homepage. It includes all the
> important features of our current site, even the closest servers
> information, with a cleaner, simpler design and setup. It places more
> emphasis on our top level domains, and it still includes a blogging system
> for future Press Releases and updates (which I think we should utilize
> more):
> Because it's a static site, the security risks are nonexistent and it can
> be hosted anywhere. If this were to gather relatively good opinions from
> all of you, I'd push it to our organization at
> so anybody would be able to edit it (via Pull Requests). Ideally we could
> setup a system to automatically pull (from GitHub) and build the site on
> our webservers behind some lightweight server like Nginx. That way we'd be
> able to keep the existing servers and TLS functionality (which GH Pages
> does not support with custom domains) everything is just more open,
> compared with random WordPress administrators who as far as I can gather
> fall between the "not having enough time to update the site" and the "have
> no idea how to operate WordPress" categories.
> Anyways, this was a really long email about a really simple topic. Sorry
> about that.
> Hopefully all of you are on board,
> Jonah
> P.S. Also this would be the perfect time to switch to our
> <> domain for the homepage and add some 301 redirects
> when we move, that'll just look nicer in general (and there'd be no need to
> move all the sites to that domain, at least not right away).
> --------
> You are a member of the OpenNIC Discuss list.
> You may unsubscribe by emailing discuss-unsubscribe AT

Best regards

Fusl - root AT -

Attachment: signature.asc
Description: OpenPGP digital signature

Archive powered by MHonArc 2.6.19.

Top of Page