Search the Community
Showing results for tags 'convention'.
Found 2 results
-
It's common sense to name things based on meaning -- search, sitemap, home, basic-page / default etc. -- but I'm interested in hearing if you folks are defining / following more specific rules than these. This is something I've been thinking quite a bit lately and unfortunately I feel a bit lost here. IMHO this becomes an important thing especially when you have multiple developers working on / providing support for same projects, which they aren't necessary familiar with. It's one of those things that make it easier for a new developer to jump on board of a project and instantly understand what's happening under the hood (or at least make educated guesses.) So after this (longish) explanation, I'd really love to hear what you think about this subject -- what kind of naming conventions do you apply for your templates and/or fields? (If any.)
- 4 replies
-
- 2
-
-
- convention
- templates
- (and 1 more)
-
I've read several of the tutorials, just wondering what is a better convention, use .inc or.php extension (e.g. main.inc or _main.php)? Why have two naming conventions? Never mind,I think I got this mixed. main.inc you include,also called main.inc strategy, the _main.php is a different delayed strategy (_init.php, template, then, _main.php executes). Two different things. What to choose? I think the _main.php is more flexible.
