Folder paths
-
One of our developers has ( to me ) a very different perspective of making folders for his websites. I lean towards making folders similar to content structure ie: Admin folder with pages etc or a sub-system folder etc. His folder structure revolves around having folders named after functions ie: Search folder with various pages that search different objects or sub-systems. I've always pretty much run with my physical folder structure similar to my content. I can see benefits for doing it another way but I've never seen another developer use that manner. It makes no difference in the end as the actual page addressing can be handled via links/ site maps etc. Anyone else do it in the same manner? Or maybe something different again? Quite intrested to see what everyone does.
-
One of our developers has ( to me ) a very different perspective of making folders for his websites. I lean towards making folders similar to content structure ie: Admin folder with pages etc or a sub-system folder etc. His folder structure revolves around having folders named after functions ie: Search folder with various pages that search different objects or sub-systems. I've always pretty much run with my physical folder structure similar to my content. I can see benefits for doing it another way but I've never seen another developer use that manner. It makes no difference in the end as the actual page addressing can be handled via links/ site maps etc. Anyone else do it in the same manner? Or maybe something different again? Quite intrested to see what everyone does.
I tend to do it as a mix of the two:
Root
Open
Help
Registration
User
...
Admin
...If only because it keep the number of different web.config files down.
Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together. Manfred R. Bihy: "Looks as if OP is learning resistant."
-
One of our developers has ( to me ) a very different perspective of making folders for his websites. I lean towards making folders similar to content structure ie: Admin folder with pages etc or a sub-system folder etc. His folder structure revolves around having folders named after functions ie: Search folder with various pages that search different objects or sub-systems. I've always pretty much run with my physical folder structure similar to my content. I can see benefits for doing it another way but I've never seen another developer use that manner. It makes no difference in the end as the actual page addressing can be handled via links/ site maps etc. Anyone else do it in the same manner? Or maybe something different again? Quite intrested to see what everyone does.
I'm also very picky on that. The structure has to be followed and may not be changed just because someone has a lazy day. Recently I had to have an argument about libraries and if they need to be set up in "project/resources/lib" or "where the dev feels to have them today". Beside of that: Folders are always named by the function - so the Folder "header" contains the header files and the folder "XXXDialog" contains the XXXDialog. Resources are (as mentioned above in a separate folder "resource" and sorted in subfolders by the content - "properties", "images", "printtemplates". Properties are named after there position - "header.name.title" is the title of the field name in the header.
regards Torsten I never finish anyth...
-
I tend to do it as a mix of the two:
Root
Open
Help
Registration
User
...
Admin
...If only because it keep the number of different web.config files down.
Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together. Manfred R. Bihy: "Looks as if OP is learning resistant."
-
I'm also very picky on that. The structure has to be followed and may not be changed just because someone has a lazy day. Recently I had to have an argument about libraries and if they need to be set up in "project/resources/lib" or "where the dev feels to have them today". Beside of that: Folders are always named by the function - so the Folder "header" contains the header files and the folder "XXXDialog" contains the XXXDialog. Resources are (as mentioned above in a separate folder "resource" and sorted in subfolders by the content - "properties", "images", "printtemplates". Properties are named after there position - "header.name.title" is the title of the field name in the header.
regards Torsten I never finish anyth...
And then you decide to use a MasterPage and nothing is as easy as it should be anymore. (And he runs off maniacally singing with a .. here and .. there here a . there a . everywhere a .. )
It always itches for the first week or so. My Mu[sic] My Films My Windows Programs, etc.
