Blazor documentation is really poor

[Tom]

Your documentation is really bad and very frustrating. It feels like your main goal was to get your product to market without much thought about the user experience.

The API documentation often says nothing more than, for instance, the name of the property. It should explain what the property's for and show an example of how to use it.

Also you need many more more examples of how to use the product in general for common scenarios. And when customers ask for help on the forum, that's a great source of material to improve your documentation.

I constantly find myself going to competitive products to see if their API and documentation is better. It feels like it's just a matter of time until I abandon yours once other company's catch up on the number of components.

[Saranya Dhayalan]

Hi Tom, 

 

We deeply regret the inconvenience caused. 

 

Currently we are working to improvising our UG & API section in the detailed explanation. we will improve the documentation section in a progressive manner. We will consider your suggestion in our end, please find the below feedback link for this. 

 

https://www.syncfusion.com/feedback/12838/improvement-of-api-documentation-for-ej2-blazor 

 

Regards, 

Saranya D 

 

[Jose Antonio]

Hi Tom, 

 

We deeply regret the inconvenience caused. 

 

Currently we are working to improvising our UG & API section in the detailed explanation. we will improve the documentation section in a progressive manner. We will consider your suggestion in our end, please find the below feedback link for this. 

 

https://www.syncfusion.com/feedback/12838/improvement-of-api-documentation-for-ej2-blazor 

 

Regards, 

Saranya D 

 

Saranya is October, and you still have the same issue. The worst documentation in town for one of the best ones...You don´t get too much by being an excellent product if nobody is able to use it. The "starter" approach with videos y really good, but once you want to go a little bit far than "Hello World," you are stacked in the complete darkness of the product. Just take a look at all the tickets you have .... most of them are due to lack of knowledge...

[Mohan Kumar Ramasamy]

Hi Tom, 

 

Sorry for the inconvenience caused. 

 

Currently we are working to improvising our UG & API section. we will to refresh this documentation link. Once we refreshed the documentation, we will inform you. 

 

Regards, 

Mohan kumar R 

[Z flower]

Your documentation is realllllllllly bad.   Your example code is misleading, confusing, and untrustworthy.  I am just starting out with Blazor and then we come across your stuff for components. You apparently forgot to allow for putting text from a file (i.e. a block of text) in your textbox?  If there is a way, you didn't tell anybody.  That is like step number 3 in using a textbox, don'tcha think?  BTW, step number 2, how do you name a textbox?  Your examples, written by somebody obviously late for something, uses "textbox1.text = "ABCD" and never bothers to indicate how the code is supposed to know which textbox is "1"?  Sloppy work guys.

[Rajendran R]

Hi flower,

Apologies for the unfortunate experience you had with our documentation. We appreciate your perspective, and we strive to provide clear and helpful documentation for our users. We continuously work on improving it based on user feedback.

Regarding your requirement to input text from a file, we apologize for any confusion. If you could provide more context or clarify your specific requirements, we would be glad to validate the requirement and provide an appropriate solution.

In terms of naming textboxes, our documentation provides guidance on how to bind text to a Blazor Textbox component that supports two-way binding to its value. With two-way binding, there is no need to assign an ID or explicitly set the text value. You can find more information in our documentation's "Getting Started" section for the Textbox component: link to the Textbox documentation.

We value your feedback, as it helps us identify areas where we can further improve our documentation and examples to better serve our users. If you have any specific suggestions or further questions, please feel free to share them with us. We are here to assist you.

Regards,

Rajendran R