Croogo: The CakePHP CMS
7 likes6,466 views
Croogo is a content management system (CMS) built on the CakePHP framework. It started as a personal tool for the creator's projects. Key features include organizing content into different types like pages and blog posts. Users are assigned roles that determine their permissions. Extensions can be added through themes, plugins, and hooks. The developer is looking forward to migrating Croogo to CakePHP 2.0 and improving the terminology. It has an active community contributing code on GitHub and discussing the project on its Google Group.
Croogo: The CakePHP CMS
- 2. About me Fahad Ibnay Heylaal @fahad19 on Twitter/GitHub/IRC From Bangladesh Currently living in London Working at SkylightIT.com
- 3. Introduction
- 5. What is Croogo? Yet another Content Management System
- 6. What is Croogo? Yet another Content Management System Built on top of CakePHP framework
- 7. How did it start?
- 8. How did it start? It started as a personal tool for projects
- 9. How did it start? It started as a personal tool for projects With common features I needed
- 10. How did it start? It started as a personal tool for projects With common features I needed Later open sourced
- 11. Weird name?
- 12. Weird name? Name taken from a Bengali novel called Krugo
- 13. Weird name? Name taken from a Bengali novel called Krugo Written by Muhammad Zafar Iqbal
- 14. Weird name? Name taken from a Bengali novel called Krugo Written by Muhammad Zafar Iqbal Wanted a unique name that Google didnt know about
- 15. Download
- 16. Download From GitHub: http://github.com/croogo
- 17. Download From GitHub: http://github.com/croogo Two options:
- 18. Download From GitHub: http://github.com/croogo Two options: Zip archive with all dependencies included
- 19. Download From GitHub: http://github.com/croogo Two options: Zip archive with all dependencies included Grab latest code from the repository
- 20. Installation
- 21. Installation Upload Croogo 鍖les to your server
- 22. Installation Upload Croogo 鍖les to your server Visiting your site starts the web based installer
- 23. Installation Upload Croogo 鍖les to your server Visiting your site starts the web based installer Whole process takes less than 5 minutes
- 24. Content
- 25. Content Content is organized in different types
- 26. Content Content is organized in different types There are two primary types:
- 27. Content Content is organized in different types There are two primary types: Page
- 28. Content Content is organized in different types There are two primary types: Page Blog post
- 29. Content Content is organized in different types There are two primary types: Page Blog post You are able to create more content types
- 30. Taxonomy
- 31. Taxonomy Basically means categorization of content
- 32. Taxonomy Basically means categorization of content Terminologies to understand:
- 33. Taxonomy Basically means categorization of content Terminologies to understand: Term: individual category names
- 34. Taxonomy Basically means categorization of content Terminologies to understand: Term: individual category names Vocabulary: a collection of Terms
- 35. Taxonomy Basically means categorization of content Terminologies to understand: Term: individual category names Vocabulary: a collection of Terms Two default vocabularies: Categories, and Tags
- 37. Users & Permissions Croogo uses CakePHPs ACL
- 38. Users & Permissions Croogo uses CakePHPs ACL Users belong to a Role
- 39. Users & Permissions Croogo uses CakePHPs ACL Users belong to a Role Roles are given access to controller actions
- 40. Users & Permissions Croogo uses CakePHPs ACL Users belong to a Role Roles are given access to controller actions By default, there are 3 roles: Admin Registered Public
- 41. Extensions
- 42. Themes Extra layer on top of your Views Helps customize the appearance of your website Find themes at Croogo wiki
- 43. Plugins Need to be activated from admin panel
- 44. Plugins Need to be activated from admin panel Plugins have bootstrap and routes
- 45. Plugins Need to be activated from admin panel Plugins have bootstrap and routes Callbacks on activation/deactivation
- 46. Plugin activation File at /温沿沿/沿鉛顎乙庄稼壊/艶恰温馨沿鉛艶/界看稼鍖g/艶恰温馨沿鉛艶喝温界岳庄厩温岳庄看稼.沿鞄沿
- 47. Hooks
- 48. What is a Hook? Ways plugins can integrate with the app without modifying core 鍖les
- 49. What is a Hook? Ways plugins can integrate with the app without modifying core 鍖les Hooks are set from plugins bootstrap 鍖le
- 50. Hook examples Attach Example behavior to Node model Load Example component in NodesController Load Example helper in NodesController
- 51. v2.0?
- 52. Changes in v2.0 Migration to CakePHP 2.0
- 53. Changes in v2.0 Migration to CakePHP 2.0 Development will start as soon as v1.3.x leaves beta
- 54. Changes in v2.0 Migration to CakePHP 2.0 Development will start as soon as v1.3.x leaves beta Terminology will be made easier to understand
- 55. Changes in v2.0 Migration to CakePHP 2.0 Development will start as soon as v1.3.x leaves beta Terminology will be made easier to understand Plugin based architecture very likely
- 56. Who uses Croogo?
- 61. The Community
- 62. Getting people involved in open source is not as easy as appointing them Mark Story
- 63. Community Activities Contributions coming in from 20+ developers
- 64. Community Activities Contributions coming in from 20+ developers Lighthouse account with 200+ tickets
- 65. Community Activities Contributions coming in from 20+ developers Lighthouse account with 200+ tickets Google Group with 300+ members
- 66. Community Activities Contributions coming in from 20+ developers Lighthouse account with 200+ tickets Google Group with 300+ members Translated in 12 different languages
- 67. Community Activities Contributions coming in from 20+ developers Lighthouse account with 200+ tickets Google Group with 300+ members Translated in 12 different languages 70+ repos on GitHub related to Croogo
- 68. Links Of鍖cial Website: http://croogo.org Wiki: http://wiki.croogo.org Issue Tracker: http://croogo.lighthouseapp.com Google Group: http://groups.google.com/ group/croogo @Croogo
- 69. Thank you!
Editor's Notes
- #2: \n
- #3: \n
- #4: \n
- #5: \n
- #6: \n
- #7: \n
- #8: \n
- #9: \n
- #10: \n
- #11: \n
- #12: \n
- #13: \n
- #14: \n
- #15: \n
- #16: \n
- #17: \n
- #18: \n
- #19: \n
- #20: \n
- #21: \n
- #22: \n
- #23: \n
- #24: \n
- #25: \n
- #26: \n
- #27: \n
- #28: \n
- #29: \n
- #30: \n
- #31: \n
- #32: \n
- #33: \n
- #34: \n
- #35: \n
- #36: \n
- #37: \n
- #38: \n
- #39: \n
- #40: \n
- #41: \n
- #42: \n
- #43: \n
- #44: \n
- #45: \n
- #46: \n
- #47: \n
- #48: \n
- #49: \n
- #50: \n
- #51: \n
- #52: \n
- #53: \n
- #54: \n
- #55: \n
- #56: \n
- #57: \n
- #58: \n
- #59: \n
- #60: \n
- #61: \n
- #62: \n
- #63: \n
- #64: \n
- #65: \n
- #66: \n
- #67: \n
- #68: \n
- #69: \n
- #70: \n