The Radiant Ethic

Editor's Notes

8. *** T/BDD, Test-first *** DRY *** Convention over configuration *** "Beautiful code" **** Efficiency, Expressivity, Elegance
14. [Why is this ethical/moral?] *** Originally for ruby-lang.org *** "Static++" - flat, but easy to do typical site-management tasks *** Always had auto-expiring page cache **** 2006 custom-built expiring page cache (YML + content) **** 2009 converted to customized Rack::Cache (HTTP-friendly) *** Page/parts/snippets/layouts model strikes balance between generation and curation
15. [Why is this ethical/moral?] *** Originally for ruby-lang.org *** "Static++" - flat, but easy to do typical site-management tasks *** Always had auto-expiring page cache **** 2006 custom-built expiring page cache (YML + content) **** 2009 converted to customized Rack::Cache (HTTP-friendly) *** Page/parts/snippets/layouts model strikes balance between generation and curation
16. [Explain Pilsbury dough boy - tastes great, but leaves you fatter and wondering the contents of what you ate] [Why is this ethical/moral?] Core is < 6000 LOC (not including tests) Move non-core things to extensions and libraries Stand on others’ shoulders (Rails, Rack::Cache, RedCloth)
17. [Why is this ethical/moral?] *** if-else vs. ternary operator *** tag design - if/unless, first/last (designer and content-model focused, not generic) *** Haml - simplifies default templates, emphasizes structure *** avoiding long chains of methods *** List for page tree is more pure, but harder to control and extend - uses table with classes
18. [Why is this ethical/moral?] *** if-else vs. ternary operator *** tag design - if/unless, first/last (designer and content-model focused, not generic) *** Haml - simplifies default templates, emphasizes structure *** avoiding long chains of methods *** List for page tree is more pure, but harder to control and extend - uses table with classes
19. [Why is this ethical/moral?] *** if-else vs. ternary operator *** tag design - if/unless, first/last (designer and content-model focused, not generic) *** Haml - simplifies default templates, emphasizes structure *** avoiding long chains of methods *** List for page tree is more pure, but harder to control and extend - uses table with classes
20. [Why is this ethical/moral?] *** if-else vs. ternary operator *** tag design - if/unless, first/last (designer and content-model focused, not generic) *** Haml - simplifies default templates, emphasizes structure *** avoiding long chains of methods *** List for page tree is more pure, but harder to control and extend - uses table with classes
21. [Why is this ethical/moral?] No ivory-tower content model No standard: * comment system * file-management * version-control * event calendar... etc.
22. [Why is this ethical/moral?] 241 Extensions in the registry. Top 3 types: 1) Tweaks to admin UI or data model 2) Enhancements to page capabilities 3) Integration with external services and APIs Some core features are moving into extensions
24. The simplicity, clarity and strong principles of Radiant have inspired others to copy it (Frog and Wolf) or take it as the basis for new systems (Webvanta), or even write reactions to it (Browser CMS).
26. Extensions: proliferate, enable developer freedom Tags: some of my favorites are yield, children:if_first/last, aggregate
27. Extensions: proliferate, enable developer freedom Tags: some of my favorites are yield, children:if_first/last, aggregate
28. Extensions: proliferate, enable developer freedom Tags: some of my favorites are yield, children:if_first/last, aggregate
29. Extensions: proliferate, enable developer freedom Tags: some of my favorites are yield, children:if_first/last, aggregate
30. Extensions: proliferate, enable developer freedom Tags: some of my favorites are yield, children:if_first/last, aggregate
31. Extensions: proliferate, enable developer freedom Tags: some of my favorites are yield, children:if_first/last, aggregate
32. Static Lean code Clarity General usefulness New features in extensions
33. Static Lean code Clarity General usefulness New features in extensions
34. Static Lean code Clarity General usefulness New features in extensions
35. Static Lean code Clarity General usefulness New features in extensions
36. Static Lean code Clarity General usefulness New features in extensions
37. Extensions and initializers are difficult to test code that is hyper-critical to the system. Extensions were a hack around Rails’ weak plugin system in 1.1+, but break many boundaries of modularity. Rails 3 Engines are better. Admin::ResourceController - lots of class_eval, class-level DSLs, unclear design decisions.
38. Extensions and initializers are difficult to test code that is hyper-critical to the system. Extensions were a hack around Rails’ weak plugin system in 1.1+, but break many boundaries of modularity. Rails 3 Engines are better. Admin::ResourceController - lots of class_eval, class-level DSLs, unclear design decisions.
39. Extensions and initializers are difficult to test code that is hyper-critical to the system. Extensions were a hack around Rails’ weak plugin system in 1.1+, but break many boundaries of modularity. Rails 3 Engines are better. Admin::ResourceController - lots of class_eval, class-level DSLs, unclear design decisions.
40. Extensions and initializers are difficult to test code that is hyper-critical to the system. Extensions were a hack around Rails’ weak plugin system in 1.1+, but break many boundaries of modularity. Rails 3 Engines are better. Admin::ResourceController - lots of class_eval, class-level DSLs, unclear design decisions.