CollabCamp website should be collaborative

[mozboz]

All people who have been recently hacking on the website 1) stop 2) wtf.

Alex and Charlie's work to make a super simple functional website was great. HTML and CSS is what we need for a website. Collaboration = everyone learning simple HTML, CSS and git skills and everyone being able to hack on the code with notepad, and a simple deploy process around make changes and pull requests that are acknowledged by the group. Having to install node and all its dependencies, learn docpad and twelve different types of markup, and compile your website to unreadable unhackable code is eleventeen-thousand steps ahead of where we need to be and mega unneeded complexity.

Let's roll back: HTML, CSS, 3 step git process that anyone can use to edit the website with notepad, as Alex and Charlie were doing.

[mozboz]

@dahacouk @chozabu @wvengen @almereyda

[dahacouk]

Agreed! Don't know what else to say other than "Agreed". And definitely "eleventeen-thousand"! ;-)

[almereyda]

Isn't it by being deployed via gh-pages?

On 27 May 2015 at 12:11, Daniel Harris [email protected] wrote:

Agreed! Don't know what else to say other than "Agreed". And definitely
"eleventeen-thousand"! ;-)

—
Reply to this email directly or view it on GitHub
#3 (comment)
.

[mozboz]

My concrete proposal here:

1. Revert the website immediately to the simplest possible version that enables maximum collaboration, re-use, and understandability:
   1.1) 2 files: index.html and style.css, that are extremely well layed out and commented, and contain what we need, and nothing else.

2. facilitate a collaboration process that anyone can do on any platform, where if learning is required the skills are useful, cross functional, and not tied to any platform or tools, other than our choice to use git and github
   2.1) skills required: git, html, css
   2.2) deployment process is standard git process with pull requests

[dahacouk]

@mozboz I like that idea.

[wvengen]

Simple html&css is great for a single-page site, but the design has multiple pages. That's why it needs a simple templating system, or you need to update footers and navigation on all pages at once, maintaining this would be terrible. Docpad @almereyda had experience with, but seeing it in practice I agree that it's overcomplicated to use here, requiring a manual deployment step.

I've moved master to use jekyll, which is compiled by Github automatically.

[wvengen]

TODO

• Adding a README explaining where to edit what. We need a nice README.me #7
• Add pages for events and integrate it into the design (some test started, but unfinished) Pages for previous events #6

[wvengen]

And, thanks for bringing this up! Is this better?

[chozabu]

Hey, Interesting to see jade and jekyll, jekyll does indeed seem to be a better fit for a github page.
plain HTML/CSS is sure simpler, and a lower barrier of entry, but jade/jekyll seems a more able and expandable solution.
Personally I am probably happier with jekyll for this site than plain HTML/CSS or jade, though I've not had a really good look yet.
+1 to wvengens TODO List

[wvengen]

So how about now?