I took a look at the style guides of all of the most popular frameworks.<\/p>\n
Yii Style Guide<\/a> Yii is the simplest. They just tell you what should go in the Model, Controller and View. I actually believe that’s the best thing when thinking of a framework as a framework, since a framework shouldn’t be telling you how to write your code, and you should never be mixing your code within the framework. A framework is a tool, but it should be on the primary developer to decide on the style that’s right for them and their team. However, I do understand that most of these style guides are talking about their framework as a project, which of course it is<\/p>\n There are a lot of topics to consider in a style guide. A lot of things popped up as I looked at the different style guides that I hadn’t even considered. <\/p>\n File Names Some of the style guides got so long I kind of got angry. Trying to enforce things like whitespace, logical operators or indentation is foolish. It’s just too much and it takes away from the things that are actually important.<\/p>\n So what’s actually important?<\/p>\n What’s important is what people are going to read. Nobody wants to read through a 30 page style guide, and they won’t. The best solution I’ve found is to have 2 style guides. The first, important style guide is to outline the very essential rules you want for your project. Try to keep it short enough to fit on one page so someone may actually read the whole thing. Then, if you choose, you can have a nitty gritty style guide that outlines how you want your variables named and if you’re an indent nazi. You can always refer back to the nitty gritty if someone is submitting code that you find repugnant.<\/p>\n My style guide for Quizmo<\/a> I took a look at the style guides of all of the most popular frameworks. Yii Style Guide Codeigniter Style Guide Zend Style Guide Symfony Style Guide CakePHP Style Guide Yii is the simplest. They just tell you what should go in the Model, Controller and View. I actually believe that’s the best thing when […]<\/p>\n","protected":false},"author":4571,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[63924,3163],"tags":[63960,63958,63962,1029,63956,63959,63943,63961],"class_list":["post-76","post","type-post","status-publish","format-standard","hentry","category-atg","category-php","tag-cakephp","tag-code-standards","tag-codeigniter","tag-open-source","tag-style-guide","tag-symfony","tag-yii-2","tag-zend"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/posts\/76","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/users\/4571"}],"replies":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/comments?post=76"}],"version-history":[{"count":8,"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/posts\/76\/revisions"}],"predecessor-version":[{"id":158,"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/posts\/76\/revisions\/158"}],"wp:attachment":[{"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/media?parent=76"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/categories?post=76"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/tags?post=76"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\nCodeigniter Style Guide<\/a>
\nZend Style Guide<\/a>
\nSymfony Style Guide<\/a>
\nCakePHP Style Guide<\/a><\/p>\n
\nClass Names
\nMethod Names
\nMethod Definition
\nClass and File Names Using Common Words
\nDatabase Table Names
\nConstants
\nVariable Names
\nMember Visibility (Private \/ Protected)
\nIndentation
\nCommenting
\nControl Structures
\nThe PHP Tag
\nComparing Return Values and Typecasting
\nLogical Operators
\nDebugging Code
\nPHP Errors
\nWhitespace
\nLinebreaks
\nCompatibility
\nOne File per Class
\nBracket and Parenthetic Spacing
\nLocalized Text
\nOne Statement per Line
\nStrings (When to use Single or Double quotes)
\nSQL Queries
\nDefault Function Arguments
\nAssociative Arrays
\nUnit Tests<\/p>\n
\nMy nitty-gritty style guide for Quizmo<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"