golanghr / website Goto Github PK

"vizualizacija strukture u memoriji, ono sve razlike izmedu []*Nesto i []Nesto"
@dvrkps proposed on slack

@dvrkps proposed on slack

Please think and comment about future site structure.
Because we all have limited time for participation I suggest we decide what parts of structure are feasible in nearer future, everything else will have to wait later date.

Structure overview (see bellow for description):

• Homepage
• Events (later?)
• Blog
• Community projects (later?)
• Jobs (later?)
• Links
• Video (not?)
• Code of conduct

Homepage

We can only have 3 things on the homepage because less is more and we develop in Go!
This are by priority:

1. Braking news, this can be "Go ver 1.7 is out!" or "Next week meet-up in Dubrovnik!". Content is title, max two line description, maybe picture, if you want to know more click it and go to page with more info.
2. Who we are, we have this. Also if we do not have braking news this is the first thing site visitor notices.
3. Latest from blog, 2 to 3 short form post from Blog section.

Events

This is arguably most important site content. It should have info from all upcoming and past events with all the extra material.
I see here slides and videos of lectures.
As we are far from events of this type I suggest we do not include this page in near future site structure but keep this page in mind when we make design decisions for the site.

Blog

Blog with tags. Categories are also possible but I think tags are simpler and more organic organization element.

Community projects

Page with list of projects of community members. This list includes personal projects, organization projects and "official" community projects like this web site.
Every project has it's own page with short description, how to participate, link to repo, documentation etc.

Jobs

Firms looking for Go developer could put Ad here. Every Ad should have it's own page with short info.
Old content is a problem with this type of content and we must consider solutions.
I think this page is not a priority.

Links

Links to other Go content. One page well structured.

Video

Video section with tags. Maybe have a simpler form of just putting video on Blog and tag them appropriately?

Code of conduct

Already written, we should translate it. Link in footer?