Theme Layout

Layout of the topic

The layout files are very important for your design because any other template file is rendered within the active layout. Layouts are very important for your design because any other layout templates are renders within the current layout. Layouts are very important for your design because any other layout templates are renders within the current layout. Your shop only has one layout activated at a given point in foray. When your on-line users start the ordering procedure, the layout changes.

theme.liquid is the standard layout when your website is visited by your customers.

During the ordering procedure, this becomes the current layout.

Creating a custom layout component unit for designing a theme

Previously, we discussed how theme themes work from the point of view of the Communities Builder. Let's now look at how theme layout parts work from the Developer Console point of view. At this stage, you build a fundamental layout for the theme in the Developer Console and use it in your own Communities Builder to help turn the overall site layout of your lighting team into a single, integrated entity.

Apply an interface to your layout part of the theme and specify its areas. Join a theme object to the layout part of the theme. Try your components in the Community Builders. Click in the Community workspaces on Builders to open the Community Builders. Select Settings | Developers and then select the Developer Console. Click in the developer console.

Rename the components named condensedThemeLayout and click Submit. Do not choose the Lightning Communities page in this case because you are not building a drag-and-drop part. Substitute this part of the components body with this one. In order to appear in this area in the Community Builder, a layout components for the theme must implemented the forceCommunity:themeLayout interfaces. Insert {! v.body} wherever you want the page to page to page change to appear within the theme layout.

In the layout of the theme, the component[] contained in your mark-up is represented as open areas that make up the foundation of your layout. In Community Builder, a user can append drag-and-drop elements to these areas. It uses the SLDS gridsystem to create a layout that adds a tree to the layout. The Community Builder is a designer tool that determines which feature features, such as UI labeling or config property, are displayed in the Community Builder.

Located in the same directory as your . bmp asset, the theme asset explains the Lightning component's design-time behaviors - information that requires powerful viewing to view the asset in a page or application. Build a . dc file for your template. dcmp by selecting dc on the right side of the Developer Console.

In order to give the components a UI tag, substitute the content with this UI tag. Let's quickly test the new layout part of the design to see what its texture looks like on the page. Update the web page in Community Builder. If you click on New Design and call it Home. Choose Theme Layout for the Home Theme layout to use.

Choose Sie Override the default theme layout for this page. In the Theme Layout drop-down list, choose Home. This page will be updated, and now you can see your new layout in operation! Let's take a look at the layout of the page. There is no longer a heading (1) that previously containedavigation, searching, profiles menus and logos.

You have two new areas on the side pane lookup (2) and sidebar footer (3). See how the standard lookup components of the reference appear in the lookup area? They appear there because the query is a specific, named area name. By declaring the find as an attributes name value, your design's user-defined layout uses the template's standard find engineutomatically.

That means that whenever you or other people change the layout of a style sheet, the value of the contents of the find area is preserved (if the new layout contains a find area). This also means that you can replace the lookup components with a user-defined lookup one.

Mehr zum Thema