In order to help though we first need to become power users of the platform itself, as if we were the eventual customer.
Over the next year we will implement the CMS many times with POCO and C# and custom controllers and actions. Then using the same sample project we have built we will tackle first class methods of doing this in the CMS without the need for custom code.
Project #2 is implementing a help center, the help center can be completely implemented without any custom code
Project #3 is implementing a job board, here we will have to use custom code that should not be merged back with Raytha core; this is an example of building a custom website as if we were an agency building it for a customer
Project #4 will start to explore features we can add add to the core to reduce / remove our custom C# code; these features will be sent back to Raytha core with a pull request
The long term task of this CMS Research repo is to build pull requests and make meaningful contributions to the open source CMS upstream.
There is a long list of features that we will want to help with: https://github.com/RaythaHQ/raytha/issues
In order to help though we first need to become power users of the platform itself, as if we were the eventual customer.
Over the next year we will implement the CMS many times with POCO and C# and custom controllers and actions. Then using the same sample project we have built we will tackle first class methods of doing this in the CMS without the need for custom code.
Project #2 is implementing a help center, the help center can be completely implemented without any custom code
Project #3 is implementing a job board, here we will have to use custom code that should not be merged back with Raytha core; this is an example of building a custom website as if we were an agency building it for a customer
Project #4 will start to explore features we can add add to the core to reduce / remove our custom C# code; these features will be sent back to Raytha core with a pull request