how should I organize my project?

Hi makers,   We were having an internal discussion regarding organizational best practices and naming conventions, folder structures, module structures and were curious about the things you guys like, or dislike?   I know mendix has a docs page about this, but are there things you do differently?   ps: you can also edit the documentation on this page if it is outdated on the github do you do things like: ACT_Create_Student ACT_Edit_Student or ACT_Student_Create ACT_Student_Edit   Is project organization just personal preference? what is the goal? maintainability? readability? who can help me have a meaningful discussion around this?
1 answers

We mostly try to adhere to the Mendix best-practices, only adding or adjusting them when we feel it's beneficial.


For example, we also use the SUB prefix in microflow as it makes sure there's always a similar order in the microflows for an entity(if you don't use SUB, the ‘sub’ microflows for an entity starting with a ‘AB’ would be on top, while the sub flows starting with ‘ZZ’ would be on the bottom of the list).

Another example is the folder structure. We usually adhere only an Entity Related folder structure. For example a flow ‘SUB_Order_SetStatus’ could be triggered by multiple processes, thus organizing them by process makes it easier to forget to reuse the same logic(an increases the changes of unwanted duplicates). For this same reason we also always organize the documents within a folder to group them by their document type(Microflows, Nanoflows, Pages etc).


Adhering to the best practices is really important in our opinion as it makes it much easier to onboard new developers to a project and helps devops to do their work better.