@allenholub @productdreams @IBespalchuk No, devs like to biuld nice things. They do not understand business (and they don’t have to)

New people jumping in to #Angular are in a hell of a bad situation. There are: - articles with signals. - old articles with RxJS based solutions. - new standalone components - old components with modules - new control flow - old directive based syntax - 8 ways to unsubscribe …and so on It’s all over the place! If you don’t know anything about Angular it’s near impossible to understand and get things right. If you don’t know who to follow and read material from you are doomed. Old/Current docs are hard to navigate to find basic stuff. New docs are easier to reason about but still incomplete. The transition period is going to be a nightmare for a long time. ————————————- Angular Space is aiming to make a dent. Be a place where you don’t have to worry about content validity. It’s a hard mission that is going to take a long time to fulfill. But we can do it. Together :). What I cannot help do is fix officials parts. ————————————- As for the official parts of angular docs I would encourage to open up to invite more community members as maintainers instead of keeping it closed. There are not enough hands to go through and manage contributions. Prime example would be AngularFire. State of the docs is bad, people have hard time finding anything in there. Community members invited to help managed it as maintainers would: - drive traffic - bring up morale and bring their own communities to uplift the state of official docs - be able to maintain higher volume of contributions - also a great PR move —————————- Do you agree? Maybe you have better ideas? Please share :) 👇