A comprehensive Objective-C style guide focused on readability for print and web, used by Kodeco (formerly raywenderlich.com).
The Kodeco Objective-C Style Guide is a set of coding conventions used to maintain consistency across Kodeco's educational materials, including books, tutorials, and starter kits. It solves the problem of inconsistent code styles when multiple authors collaborate, with a specific focus on readability for print and web formats. The guide covers everything from naming and spacing to modern Objective-C features like literals and enumerations.
Objective-C developers, particularly those working on iOS or macOS projects, and authors or educators creating technical content where code readability is crucial.
Developers choose this guide because it's battle-tested by a major educational publisher, emphasizes readability for learning, and provides clear, opinionated rules that reduce style debates. It's specifically tailored for collaborative and educational contexts rather than just general app development.
A style guide that outlines the coding conventions for Kodeco
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Explicitly optimized for print and web tutorials, with rules like 2-space indents and the Golden Path principle to reduce nesting, enhancing clarity for learners as stated in the introduction.
Covers modern Objective-C features such as literals, NS_ENUM, and instancetype, ensuring code adheres to current best practices and reduces legacy boilerplate.
Adheres closely to Apple's naming and memory management guidelines, reducing cognitive load for developers familiar with official documentation and promoting consistency.
Designed for multiple authors, with detailed rules on spacing, naming, and code organization to maintain uniformity across books, tutorials, and starter kits.
Does not provide built-in linter configurations or formatting tools, relying on manual adherence which can be error-prone and inefficient for large teams or CI/CD pipelines.
Includes mandatory rules like the smiley face comment style and strict avoidance of colon-aligning with blocks, which may seem arbitrary or distracting in non-educational contexts.
Prioritizes space conservation for print, such as 2-space indents, which might not align with teams preferring 4-space indents or other visual styles for digital-only projects.