Open Atrium 2 is a complex distribution with most things already provided for in the Profiles folder, particularly theming.
I am having trouble finding where everything is for the purpose of changing how things look and function.
For example. I want to provide a number of templates for a user to choose from when creating new content. I can find where the original template is and then add new templates in the same location.
However, this leads to a further issue when trying to upgrade the installation - some changes have been made in the /sites/ folder but some have not. eg those templates are in the OA Profile folder somewhere.
Is there a way to make all changes in the /sites/ folder?
Could I add my own sub-theme (ie a copy of the OA theme) in /sites/ that would override the pre-provided theme?
What is the best way to proceed with these problems?
Can anyone explain or point to somewhere that explains the structure of OA?
Is OA in fact amenable to this sort of customisation or should I have used a simpler installation and built it up myself?
I am assuming that changes to permissions, users, roles. views, etc are all stored in the database and that things like templates and css are in the theme folders. Is this correct?
Any help much appreciated.
Colin
Comments
If you want to create new
If you want to create new templates in Open Atrium, this can be done under Open Atrium > Section templates. Clone the default template and you can now change its layout and add more panes to it. After creating your new section, assign it to the content type you want to use it on.
Secondly, in OA, all the installation files for the distribution are found in profiles/openatrium. The rest of files is drupal core. if you installed some new modules besides the ones provided by OA, they will be in the sites/all/modules folder and therefore during the upgrade process this folder should not be overwritten. See the video about upgrading OA on the project information about this.
Rather than copying the OA theme(oa_radix), its better you create your own sub theme that inherits oa_radix so that you don't have to worry about the upgrade process.
All the changes you make in OA reside in the database but they can made available in code by using the features override module that helps you export the changes you made into a module. Read more about the Open Atrium community toolkit to find out how this can be done.