Status of the VJ Makers’ website

[bnjmnt4n]

Current status of VJ Maker’s Website

Right now it's a pretty simple website made up of a few base files for the layout and design, and files for each page. It’s currently built by hand, using HTML, CSS, Jekyll and a few other technologies.

The first thing we should decide is whether to continue to use this setup, or switch to a separate system like WordPress or Blogger.

Components of the website

Component	Description
HTML	Simple markup language used to display content of the site
CSS	Used to style/design the site
Jekyll	Simple static site generator - converts our templates into a proper site
Markdown	Allows people to write text which can be formatted into HTML easily
GitHub	Online storage for code
GitHub Pages	Simple way to host pages on GitHub

List of VJ Makers’ Sites

	Link
Website	https://vjmakers.github.io/ (Source Code)
Instagram	https://www.instagram.com/vjmakers/
YouTube	https://www.youtube.com/channel/UCdF_Fxfn2WNCpO5eB_UjD_w
GitHub	https://github.com/vjmakers

[bnjmnt4n]

/cc @casualvisitor @wei2912 @knowyourenemy

What do y’all think? Just look through this and after that we can discuss with Mr Ho and Joshua.

[wei2912]

@demoneaux what exactly is this for? Status wise, I think we should stick to Jekyll, but with Ruby plugins (meaning we build on a separate server, similar to what I do on my website). It's Makers Club so we should probably make good use of the flexibility that Jekyll offers us as opposed to using WordPress or Blogger with way less flexibility.

…

On Sun, 27 Nov 2016, 19:10 Benjamin Tan ***@***.***> wrote: /cc @casualvisitor <https://github.com/casualvisitor> @wei2912 <https://github.com/wei2912> @knowyourenemy <https://github.com/knowyourenemy> What do y’all think? Just look through this and after that we can discuss with Mr Ho and Joshua. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <https://github.com/vjmakers/vjmakers.github.io/issues/2#issuecomment-263116056>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB-Xl3FFbbHY01qC4j_BHd6eCHsHt4MAks5rCWUIgaJpZM4K9Hsz> .

[bnjmnt4n]

@demoneaux what exactly is this for?

Just listing our options, for us to consider.

Status wise, I think we should stick to Jekyll

Yep.

but with Ruby plugins (meaning we build on a separate server,
similar to what I do on my website)

Currently it's built on Travis servers and pushed to GitHub pages.

[wei2912]

@demoneaux There's no separate repository for the generated files? Or has GitHub Pages changed

…

On Sun, 27 Nov 2016, 19:41 Benjamin Tan ***@***.***> wrote: @demoneaux <https://github.com/demoneaux> what exactly is this for? Just listing our options, for us to consider. Status wise, I think we should stick to Jekyll Yep. but with Ruby plugins (meaning we build on a separate server, similar to what I do on my website) Currently it's built on Travis servers and pushed to GitHub pages. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <https://github.com/vjmakers/vjmakers.github.io/issues/2#issuecomment-263117433>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB-XlwXx0jPzSZBVFZ2vwN-WwAEg-4Foks5rCWx2gaJpZM4K9Hsz> .

[bnjmnt4n]

@wei2912 nope, but instead of using a separate repo I use one branch for the source and the master branch for the generated code.

[wei2912]

@demoneaux I see, that's a pretty nice solution. I'll push my edits soon.