Page MenuHome

user flow improvements for getting involved(blender.org)
Closed, ResolvedPublicTO DO

Description

I was trying to put myself in the place of a new developer that knows nothing about blender and wants to start contributing.

In the Getting Involved Section on blender.org (http://www.blender.org/get-involved/)

  1. Change "developer docs" button to "Getting Started". It should go directly to the getting started wiki page.

http://wiki.blender.org/index.php/Dev:Doc/New_Developer_Info

Getting involved needs to be more linear for newbies since they know nothing about how blender operates. Showing new people the entire wiki right away is confusing since they already know they are trying to get involved.

  1. Remove bug tracker from options. New members will probably know nothing about how the process works, let alone trying to fix any bugs. I don't see how this would benefit people wanting to get involved.
  1. What is the purpose of the developer sub-menu?

http://www.blender.org/get-involved/developers/

It looks like it has the same information as the wiki has. If new developers are going to the wiki for getting involved, what audience does this page have? A more appropriate name might be "Technology Overview".

Event Timeline

I just removed all the quick links from the Developers box, because I realized it's simply not possible to put enough information there for everyone who wants to get involved in the development process, I really want people to click through. This page is not only for developers but also addon scripters, translators, users testing and giving feedback, and people who just want to follow what's going on.

I've reshuffled the http://www.blender.org/get-involved/developers/ page now and renamed it to Development, and added more prominent links for how to get started.

The wiki page duplicates some things and I'm not really happy about that, but there's no obvious way to merge them. One is a bird's eye view to find out all that's going on in Blender development, the other is the reference documentation.

Brecht Van Lommel (brecht) lowered the priority of this task from 90 to Normal.Nov 18 2013, 7:56 AM
Brecht Van Lommel (brecht) changed the task status from Unknown Status to Resolved.Nov 18 2013, 8:08 AM
Brecht Van Lommel (brecht) claimed this task.