I guess it doesn't fit the theme but for indie developers there is an equally important roadmap called the marketing roadmap or getting your product out there roadmap which consists of seo, email marketing, side project marketing, blogging, contenting marketing, etc which is even more complex than this and 1000 times more important than any web development you will ever do.
Great work putting this together! Reminds me that being a developer these days is a lot of work with the insane number of tools and frameworks one is expected to know.
An aside: what would be a good one to try? My purpose: helping kids (10+) rewrite their Scratch games for the web. So something with a nice clean API for pushing sprites around.
It is a simplified API for p5.js, and very quick to get up and running with.
You might also find code.org's Game Lab a useful environment, which is p5.play based, has a sprite editor built in, and has both block based & text based editing support: https://code.org/educate/gamelab
Thanks, I've just had a look at both & they look like great suggestions. I had passed over code.org before, assuming (often an error!) it to be a Scratch clone, but actually it seems like a really useful resource.
All the tools seem to mostly concern web-apps (something interactive). I have to build a essentially static website, what are my options? I am a bit out of the loop, but the appearance of the website is a bit unusual so using just a template is not possible. Should I still use a framework or just code it in raw html? If raw html is an option, how can i reuse stuff (for example hamburger menu on mobile)?
Check out static website generators like Jekyll (https://jekyllrb.com). If that doesn't meet your needs, you can still use the same tools as for a bigger webapp e.g. Node + React + Bootstrap/Materialize.
A CSS framework like Bootstrap (https://getbootstrap.com) will provide you with some easy to use components.
thank you, Jekyll probably won't suffice. What is the better option for a custom look? The style of the buttoms etc. is custom and not based on material design or any other (and also the main focus of the website). I can't share it the mockups publicly, unfortunatly.
Jekyll (and other similar projects like Hugo) will let you do custom styles. You have to write your own theme, but this is just HTML+CSS with a bit of templating. Far larger projects I would recommend using a CSS framework such as inuit.css with SASS, but for smaller projects you can get away with plain CSS.
Your other option is to use something like Laravel or Rails or Express, and just do server-side rendering. A lot of people are still doing this, and it's still well supported.
The advantage of the static site generators is much better performance / lower resource usage, at the cost of flexibility.
The graphic work is good, but the hierarchies are inconsistent and need more work.
This map is vast but it has a lot of important gaps.
Some other things are just inaccurate. e.g: github required for any path. You could use gitlab, bitbucket, gerrit... plenty of good solutions out there.
As I understand it, Flow is to Go as flowtype is to golang. The project should be referred to as Flow in prose, while flowtype is primarily a tag/keyword for searchability.
This seems to be intended as a tree of achievements gained in the process of developing web, rather than a guide for what to use for any particular instance. Several of the paths I have happily skipped.
The backend could be further broken down into separate parts, each potentially using a different language, in order to give a clearer picture of the options and complexity. 1) web server (request/response), 2) search 3) database/store/access 4) data pipeline/ETL 5) payments
