Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement home page structure #22

Open
gsambrotta opened this issue Dec 7, 2016 · 4 comments
Open

Implement home page structure #22

gsambrotta opened this issue Dec 7, 2016 · 4 comments
Assignees

Comments

@gsambrotta
Copy link
Member

gsambrotta commented Dec 7, 2016

We will redesign entirly our home page.
On this ticket please implement just the main structure of the home page, so that each section can be filled separately later on.

Here is the mockup of the homepage.
The idea is taken a lot from opensourcebash.org, so if anything is not clear, please refer to that website.
If any other information is missing, feel free to fill gaps how you feel make more sense.
In order to be merged, this ticket will require at least 2 +1 from the community.

Also for the footer just build the space for it.
It will then develop in another ticket.

ots-homepage

@gsambrotta
Copy link
Member Author

@gnunicorn @xMartin and whoelse is interested, can you please give a look at the mockup of the homepage and give feedbacks?
Use little imagination merged to opensourcebash.org layout :)
Keep in mind that all the text content is just a placeholder!
(Thanks Ben for the link/idea!)

@gnunicorn
Copy link
Member

Oh, @gsambrotta that looks really great! I like it.

Questions:

Top:

  • What picture do we want in the hero? I think the current one is a great composition but visually not very appealing (too light, resolution not high enough). We could stage one similar to it at the event, too (if there is any decent camera around).
  • I played around with a static menu, one that sticks to the top of the visible screen and it works well for OSB (as it was mostly about having that "join" in the face all the time), but I found it rather unappealing for OTS. Unless we come up with something super important that is in there and the person can't be expected to scroll back up to, I'd vote against a sticky menu. (Also with two layers, it is rather big and awkward.)

General:

  • I'd vote for Background OTS blue with White Text for the boxes. I'd even vote for full-width boxes rather than framed. Break the design into neat little sections and give a visual feel of progressing while reaffirming the brand.
  • The Numbers: you want them to "count up", like on OSbash? That requires a bit of JS
  • in General, do you want the "floating in on scroll" animations from OSBash? That requires quite som JS and isn't always working super well (especially when linked "into" the side). I personally also think it is nicer without it and just static blocks. It was neat at the time, but OTS doesn't need that appeal and should be more "nüchtern".
  • I assume the last set of links is going to be the general footer? I'd give it a background on full-width, potentially in a completely different color (dark grey?) but we'll discuss that in the other ticket then.

@xMartin
Copy link
Member

xMartin commented Dec 9, 2016

First of all, I like it, too! :)

Sticky menu, animations: I don't think these are really needed for the layout/interaction concept so we should not make them part of the specification. Let's get done with a simple "nüchtern" version, first. Numbers also don't have to count up.

Order of sections: I propose the following order:

  1. Numbers
  2. Upcoming events
  3. Get in touch
  4. Discussion (+ OpenTechSchool tweets maybe)

and no "Become a member". Homepage space is precious and I don't see this so important.

@gsambrotta
Copy link
Member Author

@xMartin how can be "become a memeber" not important??
Is the way how me make people be more interested and feel more part of OTS. IF we don't take care that part more, we will mostly get turn over people and not so many willing to be core part of OTS

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants