Rebranding hack.aragon.org

[john-light]

Background:

The current URL of the developer portal is hack.aragon.org. It was created for a hackathon and has served us well since then. However I think we have outgrown this name and it would be more consistent if we changed the URL to build.aragon.org. This may be easier to remember and it's also a bit more formal than "hack".

Next steps:

We invite other contributors to comment just in case anyone has strong feelings about it. If there are no strong objections then next we can create a task list of what would have to be done to ensure a smooth transition, then we could execute the change and forward hack.aragon.org to the new build.aragon.org URL.

We will also rename the developer portal to "Aragon Builder Portal", so that it is more inclusive of both developers and designers. I'm not sure how designers feel about getting lumped in with developers the way it is done now so I don't have strong feelings about it personally, but maybe it does matter. Would be curious to hear what others think about it.

Preliminary to-dos:

• Change URL from hack.aragon.org to build.aragon.org, set forwarding as well
• Change repo name from hack to build
• Change site name from "Aragon Developer Portal" to "Aragon Builder Portal"
• Update URLs in other docs, even with forwarding people should get used to seeing the new URL

cc @bpierre @dizzypaty @owisixseven

[sohkai]

No strong feelings, but build.aragon.org does sound a bit like a nightly build URL (but maybe not for most of the audience). If anything, developers.aragon.org might sound the best.

We will also rename the developer portal to "Aragon Builder Portal", so that it is more inclusive of both developers and designers

"Aragon Builder Portal" is less clear to me than "Aragon Developer Portal", and I'd be inclined to move the design content away to something like design.aragon.org once we have lots of content.

However, the current content has also started branching off from just developer-centric documentation into more advanced user guides (via the CLI, etc.), so another idea is to lump it all together as a "Documentation Center".

[0xGabi]

I have mixed feeling on build.aragon.org as well, but as Brett mention, could be for a similar reason. On the other hand developers.aragon.org it's a bit focus oriented on the developer audience.

However, the current content has also started branching off from just developer-centric documentation into more advanced user guides (via the CLI, etc.), so another idea is to lump it all together as a "Documentation Center".

I strongly agree here. In my experience so far the current Aragon users are currently divide between Aragon developers (mostly Aragon apps devs) and Aragon power users. I think we been mostly center our conversation and efforts on the developer narrative. This could be a great opportunity to think more deeply about the other kind of user using the product and start targeting specific content and tools for them.

The two main ideas that come to mind are:

1. Having documentation that aims to instruct power users on the specific knowledge for their needs (e.g. they might need to lear about aragonPM but not about aragonAPI)
2. Having a specific aragonCLI tool (e.g. in my experience power users are only interested in the dao commands, so we can get rid of the rest for them)

[sohkai]

Highly agree with @0xGabi; we have a lot of room to improve the experience for both technical power users as well as developers, and these two have very different needs.

We should have a dedicated documentation track just for power users, that focuses on the terminology, architecture, and commands that they'd most likely use as tools for deeply exploring or interacting with organizations.