Hi Dmitry CSS customizations will be sufficient for the following changes.
1. Change the color theme of the store. 2. Change Company logo on header. 3. Re arrangement of the page layout. ( some what difficult to achieve ) 4. Hide unwanted page components. But it will not help if the customer want to change the page content and layout. Eg. 1. Change the footer content and links. 2. Include an additional banner. Regards Jo On Tue, Feb 25, 2014 at 12:10 AM, Dmitry Sotnikov <[email protected]> wrote: > This makes sense to me. > > Need to make sure that this CSS customization is sufficient for complete > rebranding including for example company logo, etc. > > Dmitry > > > On Mon, Feb 24, 2014 at 2:07 AM, Joseph Fonseka <[email protected]> wrote: > >> >> Hi All >> >> In an APIM multi-tenanted deployment there might be a requirement for the >> tenants to customize the store look and feel. We are hoping to support this >> by providing tenants to upload custom themes. >> >> Custom themes can be supported in two levels. >> >> 1. CSS based customizations. >> - In the first level users are allowed to customize and upload the >> style sheets with the supported resources ( images and fonts ). >> >> 2. Template base customizations. >> - In the second level user will be able to upload a custom caramel >> theme with modified templates , CSS , and JavaScript. To implement this we >> need to ensure Template files will be executed within a sandbox environment >> for security reasons. >> >> Initially we decided to support CSS based theming. >> >> *Implementation*. >> 1. Tenant user will be given and interface to upload the custom >> themes. >> 2. The application would accept a zip file containing CSS , images >> and font files. >> 3. Uploaded themes will be stored in directories having the tenant >> name, within the application. >> >> Ex : >> Tenants >> -- / Tenant1 >> -- / -- / Theme >> -- / Tenant2 >> -- / -- / Theme >> >> 4. When the store is loading If a tenant has a custom theme it would >> replace / override the default theme. >> >> *Design Decisions* >> 1. We decided to store custom themes in a directory considering they >> will get synced by dep sync in a clustered setup. >> 2. If we are storing them in the registry we need to implement >> caching when serving those resources. >> >> Please let us know your thoughts. >> >> Thanks >> Jo >> >> >> >> >> >> -- >> *Joseph Fonseka* >> WSO2 Inc.; http://wso2.com >> lean.enterprise.middleware >> >> mobile: +94 772 512 430 >> skype: jpfonseka >> >> * <http://lk.linkedin.com/in/rumeshbandara>* >> >> > > > -- > Dmitry Sotnikov > VP of Cloud; WSO2, Inc.; http://wso2.com/ > email: [email protected]; cell: +1.949.303.9653; Skype: DSotnikov > Lean . Enterprise . Middleware > > <http://wso2.com/events/> > -- -- *Joseph Fonseka* WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: +94 772 512 430 skype: jpfonseka * <http://lk.linkedin.com/in/rumeshbandara>*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
