Update to the about page #86
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks for the PR @turboki! The docs definitely do need a lot of work, and it's something the team is aware of, and definitely something we want to focus on before launching our 1.0 |
hborawski
reviewed
Oct 17, 2022
The Why and What sections of this page were talking about internal reasons for this version of Fuego, something that 99.9999% of the people who will read this page would have no context of or care about. The fact Player-UI was rewritten in Typescript is not something relevant to people exploring this repo. This page should talk about what the customer problem the framework is solving. What is Player-UI, what problem does it solve, and why should I use it rather than using React, or Angular, etc, etc. I'm super excited that you guys got this open sources finally, but the docs need a lot more context and examples if you want to see any adoption of it.
Co-authored-by: Harris Borawski <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Why and What sections of this page were talking about internal reasons for this version of Fuego, something that 99.9999% of the people who will read this page would have no context of or care about. The fact Player-UI was rewritten in Typescript is not something relevant to people exploring this repo. This page should talk about what the customer problem the framework is solving. What is Player-UI, what problem does it solve, and why should I use it rather than using React, or Angular, etc, etc.
I'm super excited that you guys got this open sources finally, but the docs need a lot more context and examples if you want to see any adoption of it.