Replace the current website with inexor-game/site

[Fohlen]

I've built a new website using vue.js as a single page application. I'd like it to replace the current blog site because

• it ships with Bootstrap 4, no more custom HTML framework
• it's entirely in the browser, get rid of the server and cronjobs
• since babel is used, it runs consistently in all major browsers and even IE8
• it uses the Github API, making it capable of in-depth blog search

Stll the following is to-do for the repository:

• [x] fix the bootstrap layout for blog and blog entries
• [x] enhance the current blog page to display more entries
• [x] fix a bug where the entry list constantly shrinks when using the search (should be notably easy)
• [x] sometimes in the future replace vue-resource with fetch, and a polyfill

[Croydon]

it's entirely in the browser, get rid of the server and cronjobs

Do I understand it correctly, that at the point of time, where we want to have dynamic features to interact with users on our website, we will need a rewrite again? Or of course some third party integration, but this may be contradictionary for the long term goal of having players chats/contacts and an own eco system in general etc.

For example what is about #267? We should find common ground about these things before we have yet another complete rewrite of our website (remember the many versions we already had?)

[Fohlen]

No we don't. We add an API in the back (for instance with Node.js) and make requests to that. Same website, still no dependence on server-side rendering.

[Croydon]

Alright. @Fohlen How do you want to implement the blog in general? Can the current structure stay or is the plan to replace it completely?

[Croydon]

@Fohlen please don't introduce again external css/js resources, keep it local

[Fohlen]

The structure stays exactly as it is.. Since the external CSS and resources are verified using subresource integrity in my opinion there is no problem with including them via a CDN. Furthermore it brings benefits for us:

• the load is distributed among multiple servers
• due to the async nature of CDN the page speed is notably boosted
• the toolchain required to build/update and pull in the latest version of assets is immense compared to including them via a CDN

[Croydon]

• we still need some kind of cronjob; the website should refresh after some short time when somebody pushed to git (or the next point)

• to further reduce our need for resources, we can setup an extremly simple Travis hook, which executes only npm install && npm run build and pushes then everything to some kind of inexor-game/site-binary repository. When I understand the nature of your rewrite correctly, we can then simply use GitHub Pages with our inexor.org domain (more uptime, more resources for other stuff!)

  • if we add some dynamic user interaction stuff in the feature, we can use a subdomain and it should be fine

• so if you care about the load see last point. In general I like it when the production site is self-contained. speed advantages with CDNs are not always given since more DNS lookups have to happen. Privacy+security advantages may not be that big when hashes used, but still there.

the toolchain required to build/update and pull in the latest version of assets is immense compared to including them via a CDN

We can use for Bootstrap, Font Awesome and Bootstrap NPM as well. Updates should be finished with changing two times a version number and npm update

[Fohlen]

• true, but this does involve quiet less logic since no merge conflicts can happen due to the multiple configurations and the submodule
• the problem is not only keeping them up-to-date, but as well the boilerpalette code needed to get it working with bootstrap
• no, we can't host it at Github Pages, since that is not possible with SSL
• that is also not true, since the boilerpalette produced by webpack is usually quiet a bummer, splitting up the css produces bummers as well
• I guess no setup that we can provide comes nearly close to the used CDN services

In summary, it requires quiet an effort to include those assets into the project. Nevertheless, if you really want to, feel free to add a patch compiling all the files using webpack.

[Fohlen]

Once @aschaeffer helped me auditing the styles, the site should be ready to be used. Pagination can be added, but is quiet an effort compared to what can be done in the same time, and since we only have 10 blog posts, it'll be better to add this as a separate issue.

[Fohlen]

The following is on my/our to-do list for the new website:

• [x] adjust and fix the styles for blog, disqus, the main page, the team page, @IAmNotHanni
• [x] add a link to the riot logs
• [x] add a youtube forward on inexor.org/yt
• [x] use history mode, so we don't break the links
• [x] add a download button and link for the nightlies @aschaeffer

[Fohlen]

Notably, the aggregator is ready to use. Only a uWSGI file is needed to get it started.

[terencode]

I'm currently working on fixing the layer for Blog and People section.

[Fohlen]

Since @terencode did a major bug fixing and the layout is now clean and nice, and the website works, can we ditch the old site?

[Fohlen]

I will add the content aggregation to another ticket.

[Croydon]

Is there anything left which the old website supported/had but the new one doesn't?

[a-teammate]

Fohlen[22:53]: Croydon (Nooby): no