codingforeveryone / codingforeveryone.github.io

Website repo
7 stars 1 forks source link

What do we want people to see while site is in development? #25

Open pjcevans opened 8 years ago

pjcevans commented 8 years ago

At the moment codingforeveryone.github.io is a 404 page - Do we mind if people are able to see our work in progress site, or do we want to keep it hidden?

If we don't mind what people see at codingforeveryone.github.io while it is in development then we can close this issue.

If we do mind what people see then we'll need a placeholder site at that URL while the main Jekyll site is being constructed. We could potentially route people to the proof of concept site, but I had an idea for a Jekyll solution:

We could set up a basic 1 page index.html and set it up to look something like our PoC site, with links to Meetup and Gitter. If we use a different Jekyll layout for that 1 page placeholder then while we work on the main site the 1 pager will be unaffected. We could also have a homepage.html or similar which could serve as the in-development site's index page which can just be renamed & rewired when we we want to publish the main site.

ozym11 commented 8 years ago

I like that idea.

While I am not opposed to displaying a WIP, I do think that for the sake of our core goals - plug people into the community, give them resources to start them learning coding - a 1-page placeholder with a a small number of links would be more appropriate.

We could also link to the gitbook as a learning resource, since most folks will probably end up finding their way there anyways. This would reduce the otherwise circuitous route from gitter -> f&c site -> gitbook that they would otherwise take.