Code driven development session proposal at DrupalCon Copenhagen 2010
Code driven development session proposal at DrupalCon Copenhagen 2010
At Nuvole the adoption of a code driven development has completely revolutionized our working flow making it more maintainable, solid and scalable. Projects like Features and Chaos tool suite are at the heart of it, even though a lot depends still on how actually you are going to use them: good code conventions (see the Kit project), well defined features boundaries and other good practices can really make the difference at the end of the day.
Therefore, Nuvole is proposing the session "Code Driven Development: a 100% DB-free development workflow" at DrupalCon Copenhagen 2010 with the aim of sharing good design decisions, code snippets and anything else related to a pure 100% database free development. More specifically, the session will cover:
- database driven vs. code driven approach in a nutshell
- what code driven development is all about: Features, Strongarm, Drush, exportables...
- coding conventions: make the world a better place
- your friends hook_install() and hook_update_N()
- the controller feature: one feature to rule them all
- lots of tips & tricks to take back home
If you are interested in the topic help this session going through the selection process by voting for it.
Comments
Comments
Where are they? I haven't seen any documentation for ctools, and I haven't found a developer, who has ever seen that. You would mame me happy, if you can show me where are the documentation pages of ctools.
Sincerely, Péter
Where are they? I haven't seen any documentation for ctools, and I haven't found a developer, who has ever seen that. You would mame me happy, if you can show me where are the documentation pages of ctools.
Sincerely, Péter
Where are they? I haven't seen any documentation for ctools, and I haven't found a developer, who has ever seen that. You would mame me happy, if you can show me where are the documentation pages of ctools.
Sincerely, Péter
Actually "well defined features boundaries" does not refer to cTools documentation, sorry about the misunderstanding. Defining features boundaries is about defining what belongs to a feature and what doesn't in order to make them as most "atomic" as possible. Anyway, features boundaries will be covered in one of our future blog posts about code driven development.
Actually "well defined features boundaries" does not refer to cTools documentation, sorry about the misunderstanding. Defining features boundaries is about defining what belongs to a feature and what doesn't in order to make them as most "atomic" as possible. Anyway, features boundaries will be covered in one of our future blog posts about code driven development.
Actually "well defined features boundaries" does not refer to cTools documentation, sorry about the misunderstanding. Defining features boundaries is about defining what belongs to a feature and what doesn't in order to make them as most "atomic" as possible. Anyway, features boundaries will be covered in one of our future blog posts about code driven development.
Comments are closed. See our other code-driven development posts for more recent content.
Comments are closed. See our other code-driven development posts for more recent content.
Comments are closed. See our other code-driven development posts for more recent content.