Enable discussions on this repository

[ryota-murakami]

I've really empathize these README section.

The goal of this repo is to serve as a collection of good practices when developing React applications. It is supposed to showcase solving most of the real-world problems of an application in a practical way and help developers writing better applications.

I have a project create-react-app-typescript-todo-example-2021 on similar mind,(It's not high quality though 😅)

And @markerikson also planed close concept website React Community Tools and Practices Cheatsheet .

I like those project even though this topic contained a lot of subjective things.
I hope to we got space for exchange information about practice that doesn't matter each developer's preference/style/opinion.

Actually I don't know ideal roadmap to the goal even though this repository showing Github trend page these days,
So if Github Discussions available visitors may create some topics or answer some questions or surveys, and the communication of information exchange may flourish.

Do you have a plan about setup Discussions on here? 👨‍💻

[alan2207]

Hey, that is a great idea!

It had crossed my mind to enable discussions too. That would be a nice way to discuss different solutions in more detail since not everything can fit in a single codebase. I might enable it soon.

Another thing I am considering is creating a documentation website based on Docusaurus or Nextra where all the best explanations and resources could be found easily, but that could happen if the docs become larger.

[markerikson]

FWIW, that's exactly what I've already tried to create in that "community tools and practices" site:

markerikson/react-community-tools-practices-cheatsheet#1

https://react-community-tools-practices-cheatsheet.netlify.app/state-management/overview

The problem is I don't have time to put into actually adding more content to it right now, and I really want that to be a community-maintained site - not just a "Mark sat down and wrote a dozen docs pages" thing.

Thus far, no one else has actually contributed any material, although a few folks have expressed interest.

[alan2207]

Now that I took a quick look at the repo @markerikson made, I think it might be a more suitable resource for community-based content because he already made a solid base for that. Another reason is that bulletproof-react might be a bit opinionated and I want it to stay that way, at least for now.

[marcustut]

@alan2207 I have successfully set up a project according to opinions made in bulletproof-react, but I swap the build system to Vite and Tailwind to WindiCSS, it's building blazingly fast.

Maybe we could mention about the build system in this section?

[ryota-murakami]

It's might be too late, thank you for enabled discussion @alan2207 🤗
I'm considering should I close this issue or stay open mean while because
@markerikson 's platform doesn't seem kicked off.
Can I fill out from basic part like starter Next.js, Vite, CRA etc...?

[ryota-murakami]

There is no topics number badge as same as Issue and PR tabs, Hence, Discussion tabs cannot get people's pay attention? 😅