How to Design Project structure with KenodReact

Hi.

I think this is very hard to answer because it depends on a lot of details regarding your project(s), your team structure, your repo handling, etc.

I can give you an example. In our team we have several frontend projects in a monorepo that we handle with NX. This software helps us to setup our projects and libraries, our repository handling, etc. but it is all very specific tailored to our needs. For example, we have a kind of container application that is able to dynamically add sub modules but that might just not be the same for you. 

One advise I can give is that you should try to make the KendoReact components as re-usable as possible. Meaning, just using the same components over and over again could be tedious and therefore creating customized parent components with custom properties that add a certain level of automation tailored to your needs could help you a lot when using these components. For example we use the DataGrid component a lot and we have a customized parent component that uses the DataGrid and adds some data handling functionality to it so that we don't have to re-develop this over and over again. Another use case is that we started now to use JSON-SCHEMA to automate the process of creating forms using the KendoReact components to simplify the dev process.

As far as file structure goes, for one of my bigger projects (before we used NX), the folder structure looks like the attached image. I'm not saying this is ideal or perfect by any means, it's just how I handled it for this project and this might differ for others. And actually nowadays it might even look different for this project if I would have to start it again. In my opinion there is no such thing as a perfect file structure as at least for me it also depends on the project and sometimes it just evolves during development.

I hope this helps...

Greetings,

Bernd