# For Developers Website Review One of the first thing a developer want to see on the developer's website is the `GET STARTED BUTTON`. Some of the best documentation I have seen makes the `Get started` link or button visible as quickly as possible. As described in an article posted on [zapier](https://zapier.com/engineering/great-documentation-examples/), when a developer lands on the documentation or developer's home page, they’re likely: - Curious what you’re offering - Eager to get started - Stuck and in need of help Examples of where this can be found: - `GET STARTED` on the call to action button on the front page of Reactjs: https://reactjs.org/ - Flutter home page: https://flutter.dev/ - Vyper doc has a table of content on the left that makes it easy for a developer to quickly navigate to the example section of the doc. - Ethereum.org has a very little intro on their homepage. But, one of the links that can be quickly located under `For developers` is the `Getting started guides` The reason why I believe we should restructure the developer's page is that `larger percentage of those on the developer page are developers who are ready to try their hand on something as quickly as possible` ## Get Started The get started section of our developer should quickly point developers to 3 things: - A quick editor to get started with. - A simple and self-explanatory example. - A link to more examples and work through. Aeternity already has a very good editor. We must keep this editor as simple as possible while we also make sure that it continues to be `feature-rich`. The first sets of examples on our `Get started` section should be very simple. I would suggest a `Hello World` and `A simple token` example. These are examples that developers are used to. Other sections that I believe should be on our developer's page includes: - More example links - Setting up locally - About the language: data structure, control flows, inbuild functions etc - Dev groups where help can be easily sorted [Forum, StackOverflow, telegram, devchat] - Link to Aeternity apps [for inspiration and ego boost] - How to Contribute [git link] - More resources ## Observations and Suggestions: - The main website of Aeternity still looks like we are advertising an ICO. - The main Aeternity website should be a map to all other Aeternity websites or links. - Important cities (links to important resources) on our map should be visible as quickly as possible. Developers are our main target. Therefore, the link to their resources should be spotted easily. - Users of Aeternity and Aepp built on Aaeternity are also very important. Therefore, links to their resources should also be easily spotted on the website. - A good UI/UX developer that is, given these points, will be able to draw out a good map for the content we currently have. A distinction should be made between Aeternity and Sofia (the programming language). Currently, Sofia appears as a third class citizen in all the places I have seen it. This should not be the case. Developers would want to add Sofia to their resume as part of the programming language that they write. This makes it important to have a link for Sofia programming language. Examples, where frameworks or entities are distinguished from their programming language, includes: - Dart is the programming language for Flutter, each of these have their website - Solidity and Vyper are programming languages for ethereum and each of these three has a separate website - Sofia is the programming language for Aeternity and should have its website ## Summary - Aeternity Website: it should be the main map that links to other resources. Link to the developer's website should be the main link (call to action) on the website. - Sofia website: It should teach developers how to use Sofia. It should also include examples of how to build Aepps from start to deployment. - Technical guide: Wallet download and Node set up should be separated from the developer's website. - Aepps website: We should facilitate and promote a website for users to easily browse Aepps developed by developers. ###### tags: `aeternity` `review` `developer` `website`