Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Logos / Images

From your application technical admin interface, select “Customize your back office”

Upload the different logos / images:

Name

Usage in Back Office

Usage in Portal

Constraints

On the BO header

Logo in the menu

None

Should be a PNG with transparency

On the FO header

Logo in all pages but

  • sign in

  • register

  • home

  • shared boards

Should be a PNG with transparency

On the BO login page

Logo on the sign in screen

Logo in home

Should be a PNG with transparency

On the FO login page

None

Logo in

  • sign in

  • register

  • shared boards

Should be a JPG of at least 1024x768 pixels, and at most 1920x960

loginBackgroundPreview

Image on the sign in screen

Image in

  • sign in

  • register

Should be a JPG of at least 1024x768 pixels, and at most 1920x960

faviconPreview

Favicon used on the Back end

None

Should be a .ico file

Background of 404 error screen

None

Image in

  • 404 errors

  • register feed back timeout

Should be a JPG of at least 1024x768 pixels, and at most 1920x960

500 error page wallpaper

None

Image in

  • 500 errors

  • register feed back error

Should be a JPG of at least 1024x768 pixels, and at most 1920x960

Portal colors

Within src/assets/_common/bootstrap/_project/global_variables.scss

You should change 2 colors in the portal application:

  • $primary Default value #FDD900, used on Form sign in button, Register sign up button and natural search homepage widget

  • $secondary Default value #00A5C8, used for call to action

Notification emails

You will need to configure email notifications templates.

Boards related

You can customize boards related templates by setting in WXM_CART2 plugin the parameter email.root with a SAN path to your customized templates folder. Example:

/<customer>/emails/boards will instruct the WXM_CART2 plugin to load all templates from SAN’s directory /<customer>/emails/boards.

The plugin will expect following templates to exist (default template can be found in WXM_CART2/res/email):

collaborate.html

The template can be specialized per board type. Create a <type>/collaborate.html

Used to notify a user that he has been added as a collaborator on a cart. Subject of the mail is defined in

WXM_CART2 bundle from key: email.collaborate.subject

Whereas the recipient of the email refers to an existing user for which we know his UI language, only the default locale is loaded, you cannot define different values for different user locales.

Within the template, you cannot reference the bundle.

download-zip.html

The template can be specialized per board type. Create a <type>/download-zip.html

Used to notify a user that a board he owns has been downloaded

WXM_CART2 bundle from key: email.download-zip.subject

Whereas the recipient of the email refers to an existing user for which we know his UI language, only the default locale is loaded, you cannot define different values for different user locales.

Within the template, you cannot reference the bundle.

share.html

The template can be specialized per board type. Create a <type>/share.html

Used to notify an external user that a board has been shared with him

WXM_CART2 bundle from key: email.share.subject

As the recipient is unknown from the system, we cannot determine the locale to use. Only the default locale is loaded.

sharezip.html

zip-available.html

Registration related

Saved search related

  • No labels