Description
Something the Website WG has discussed for quite a while now is the need for a redesign (ref: #1375, #1338, #1075, #1074, #508, and many others).
@hackygolucky and myself had a discussion with @leo a while back to try to understand the state of the former redesign (living at https://github.com/nodejs/nodejs.org-new) and came to the understanding that we need to have the discussions around a redesign and rework this in the open, rather than in private - the goal being to enable everyone to participate and engage in the work and discussion around the direction of the website.
So, I'd like to kick that discussion off.
There are many issues, both minor and major, with the current website. It's functional for downloads and docs, but we can do better. I'd like to propose that we don't rush this, as we don't just need a redesign - we need a restructuring.
Here's my proposal for how we move forward:
- Site Structure
- Assess current site structure, see what's needed and what's not.
- Call for feedback on what the current site is missing in terms of content.
- Propose a suggested site structure that we can pass to designers
- Design
- Begin the process of conceptualizing design.
- Enable multiple people to work on the design from a base. Do not enable a single user / individual to implement the design - we've attempted this in the past with io.js and Node.js, and haven't had success.
- Apply design to the site structure and begin implementation
- Implementation
- Figure out what kind of implementation will enable more collaborators and contributors to come into the project
- Begin implementing design and site structure with code
That's a very crude outline, and I'd truly appreciate any feedback/suggestions on how it can be improved or changed to fit the needs of this project moving forward.
I'd also like to share an article by Adam Miller (@amiller-gh), Redesigning Nodejs.org, in which he did a significant amount of work in assessing the strengths and weaknesses of our website currently - and an impressive assesment of sites with a similar purpose. This article stemmed from discussions at the Node.js Interactive 2017 Collaborator's Summit.