Welcome to webdoc Discussions!

[ShukantPal]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

[Zekfad]

Bump

[lazarljubenovic]

I like the idea of a highly modular documentation generator which works with TS. Currently trying to find my way around the source code, but Flow “instead” of TypeScript and rush “instead” of just yarn are making my head hurt (funny -- it's Facebook instead of Microsoft and Microsoft instead of Flow) -- by “instead“ I mean what I'm usually used to. Although I have to admit, I've never heard for rush before and I thought Flow was long forgotten. What was the decision process behind using Flow over TypeScript which has arguably more tooling and is generally way more popular?

What I currently see lacking is the documentation around the project, so I'll try to help with that. I'm counting on your help to figure out the system so I can contribute more -- as the say: help me help you 😄

(I apologize in advance for the amount of questions and issues I'm about to open -- don't worry, I plan on submitting PRs for most of them!)

[ShukantPal]

Don't worry about the questions - it helps that I'm not alone on this.

Flow: Babel used Flow, and also you can add Flow typings in comments (which is useful in templates - template writers don't want to have a build process).

Rush: Rush will skip building packages that haven't changed (in Git). I see Rush used in large projects, which I think webdoc will grow into.