Login
Bogert 1, 5612 LX, Eindhoven,
nl
en

Pages

De functie ‘Pagina’s’ stelt gebruikers in staat om contentpagina’s op uw website te creëren, te beheren en te organiseren. Dit artikel introduceert de functionaliteit en biedt u een handleiding over hoe u uw pagina’s kunt instellen. 

Machtiging 

Om toegang te krijgen tot of de functie Pagina’s te beheren, moeten gebruikers beschikken over de rol ‘Pages’. 

bg-big

oneCORE categorizes pages into 8 types and each type serves different usages and has different settings.


1. Page – to create and manage individual pages containing static content, such as terms and conditions, service information, etc. This page type supports page components.
Here are the settings of a page type “Page”:

1. Name*
This field supports a single language and is for admin use only.
2. Title
Page title is intended for use on the live website and also serves as a fallback for metadata.
3. Page url*
To set up a page URL. For the shops activating LanguageUrls feature, page URL can be set differently in each available language. Read more about How to set up multilingual URL.
4. Page layout*
To select the layout that serves as a master template of how the page will be displayed.
5. Short description
Page description is intended for use on the live website and serves as a fallback for metadata.
6. Image
To select the page image intended for use on the live website and in metadata.
7. Visible for achievement(s)
To restrict the page to be accessible only to logged-in shop users who have specified achievement(s).
8. Forbidden for achievement(s)
To hide the page from all shop users except logged-in shop users who have the specified achievement(s).
Note:

- If there are multiple achievements selected, shop users who have at least one specified achievement can see this page.
- If both are filled, only “Visible for achievement(s)” will be applied.

9. Active*
To activate or deactivate a page. An inactive page will not be accessible and visible on a sitemap and on other features in a system.
10. Indexing (Disable search engine indexing)
If marked, the system will add "noindex" to a page and remove page URL from a sitemap to prevent indexing content by search engines.
11. Metadata (JSON)
This field is not implemented with Page type.

*Required


2. Category – to create and manage pages which are used as category’s layout. One page can be used by multiple categories. This page type supports page components.
Here are the settings of a page type “Category”:

1. Name*
This field supports a single language and is for admin use only.
2. Title
Page title is intended for use on the live website and serves as a fallback for metadata.
3. Page layout*
To select the layout that serves as a master template of how the page will be displayed.
4. Short description
Page description is intended for use on the live website and serves as a fallback for metadata.
5. Image
To select the page image intended for use in metadata. There are 2 options:

- Category image – to use the 1st category image.

- Manual select – to use an image from a manual selection on this page. Options of images are from the media library.

6. Visible for achievement(s)
To restrict the page to be accessible only to logged-in shop users who have specified achievement(s).
7. Forbidden for achievement(s)
To hide the page from all shop users except logged-in shop users who have the specified achievement(s).
Note:

- If there are multiple achievements selected, shop users who have at least one specified achievement can see this page.
- If both are filled, only “Visible for achievement(s)” will be applied.

8. Indexing (Disable search engine indexing)
If marked, the system will add "noindex" to a page and remove page URL (all category URLs using this layout) from a sitemap.
9. Metadata (JSON)
This field is not implemented with Category type.

*Required


3. Product – to create and manage pages which are used as product’s layout. One page can be used by multiple products. This page type supports page components.

Here are the settings of a page type “Product”:

1. Name*
This field supports a single language and is for admin use only.
2. Page layout*
To select the layout that serves as a master template of how the page will be displayed.
3. Image
To select the page image intended for use in metadata. There are 2 options:

- Product image – to use the 1st product image.

- Manual select – to use an image from a manual selection on this page. Options of images are from the media library.

4. Indexing (Disable search engine indexing)
If marked, the system will add "noindex" to a page and remove page URL (all category URLs using this layout) from a sitemap.
5. Metadata (JSON)
This field is not implemented with Product type.

*Required


4. Blog – to create and manage pages which support a hierarchical structure – users can create a parent page and related child pages underneath. The sequence of pages can be easily rearranged by dragging and dropping them into the desired order. This page type supports page components.
Here are the settings of a page type “Blog”:

1. Name*
This field supports a single language and is for admin use only.
2. Title
Page title is intended for use on the live website and also serves as a fallback for metadata.
3. Page url*
To set up a page URL. Blog page has a hierarchical URL – the child page’s URL will automatically include the parent page’s URL as a part of its path. For the shops activating LanguageUrls feature, page URL can be set differently in each available language. Read more about How to set up multilingual URL.
4. Page layout*
To select the layout that serves as a master template of how the page will be displayed.
5. Short description
Page description is intended for use on the live website and serves as a fallback for metadata.
6. Image
To select the page image intended for use on the live website and in metadata.
7. Display product
To select the products related with this page. This function is scheduled for removal in the future.

8. Visible for achievement(s)
To restrict the page to be accessible only to logged-in shop users who have specified achievement(s).
9. Forbidden for achievement(s)
To hide the page from all shop users except logged-in shop users who have the specified achievement(s).
Note:

- If there are multiple achievements selected, shop users who have at least one specified achievement can see this page.
- If both are filled, only “Visible for achievement(s)” will be applied.

10. Active
To activate or deactivate a page. An inactive page will not be accessible and visible on a sitemap and on other features in a system.
11. Indexing (Disable search engine indexing)
If marked, the system will add "noindex" to a page and remove page URL from a sitemap to prevent indexing content by search engines.
12. Metadata (JSON)
This field is not implemented with Page type.

*Required


5. Account – to create and manage a page on Account Connect which support a hierarchical structure – users can create a parent page and related child pages underneath. The sequence of pages can be easily rearranged by dragging and dropping them into the desired order. This page type supports page components. 

Here are the settings of a page type “Account"

1. Name*
This field supports a single language and is for admin use only.
2. Title
Page title is intended for use on the live website.
3. Page url*
To set up a page URL. Account V2 page has a hierarchical URL – the child page’s URL will automatically include the parent page’s URL as a part of its path.
4. Page layout*
To select the layout that serves as a master template of how the page will be displayed.
5. Icon
To select the page icon which will appear on an Account functionality V2 menu.

6. Accessible

To configure the visibility of the page whether to share for everyone or within a family only.

7. Visible for achievement(s)
To restrict the page to be visible only to shop users who have specified achievement(s).
8. Forbidden for achievement(s)
To hide the page from all shop users except those who have the specified achievement(s).

Note:

- If there are multiple achievements selected, shop users who have at least one specified achievement can see this page.

- If both are filled, only “Visible for achievement(s)” will be applied.

9. Active
To activate or deactivate a page. An inactive page will not be accessible and visible on other features in a system.
10. Metadata (JSON)
This field is to enter JSON data which connects a page with data from outsource. To manage this field, users a required to have “PageMetadataBlob” role.

*Required


6. Orderflow – to manage content on orderflow. This page type does not support page components. Orderflow pages are configured from the system as follows:

- OrderflowShippingMethodDescription: A content will appear on shipment selection step.

- OrderIsPendingDescription: A content will appear when order is pending due to an unsuccessful payment.

- OrderIsProcessingDescription: A content will appear on confirmation step when order is in processing status.


7. System – to manage the system pages, including Not found, Shopping cart, Wishlist and Reviews. This page type supports page components.

1. Name*
This field supports a single language and is for admin use only.
2. Title
Page title is intended for use on the live website and serves as a fallback for metadata.
3. Short description
Page description is intended for use on the live website and serves as a fallback for metadata.

*Required

bg-big

Metadata

De paginatypen Pagina, Categorie, Product, Blog en Systeem hebben een metadata-invoerveld dat dient als primaire bron voor de metadata van de pagina.



Hieronder vindt u de metadata-instellingen: 

  1. Titel
    Dit veld is gekoppeld aan de meta-tagstitle en og:title. 
  2. Beschrijving
    Dit veld is gekoppeld aan de meta-tagsdescription en og:description. 

Als de metadatavelden niet zijn ingevuld, gebruikt het systeem andere standaardinformatie zoals beschreven in dit artikel Standard Key Tags for SEO and Social Media in oneCORE. 

Shortcodes 

Om specifieke gegevens van producten, categorieën enz. dynamisch weer te geven in metadata, kunt u de beschikbare shortcodes gebruiken. Het systeem vervangt elke shortcode automatisch door de bijbehorende werkelijke waarde bij het renderen. Elk paginatype is geïntegreerd met verschillende shortcodes, zoals hieronder beschreven: 


  1. Pagina, Blogen Systeem 
  • #page_title# voor de titel van elke pagina. 
  • #page_description# voor de beschrijving van elke pagina. 
  • #company_name# voor de bedrijfsnaam. 
  1. Categorie
  • #category_title# voor de titel van elke categorie. 
  • #category_short_description# voor de korte beschrijving van elke categorie. 
  • #category_metatitle# voor de metatitel van elke categorie. 
  • #category_metadescription# voor de metabeschrijving van elke categorie. 
  • #page_title# voor de titel van elke pagina. 
  • #page_description# voor de beschrijving van elke pagina. 
  • #company_name# voor de bedrijfsnaam. 
  1. Product
  • #product_title# voor de titel van elk product. 
  • #product_short_description# voor de korte beschrijving van elk product. 
  • #product_metatitle# voor de metatitel van elk product. 
  • #product_metadescription# voor de metabeschrijving van elk product. 
  • #category_title# voor de titel van de categorie van elk product. Als een product aan meerdere categorieën is gekoppeld, wordt de eerste categorie in de categorielijst van het product gebruikt. 
  • #category_short_description# voor de korte beschrijving van de categorie van elk product. Als een product aan meerdere categorieën is gekoppeld, wordt de eerste categorie in de categorielijst van het product gebruikt. 
  • #company_name# voor de bedrijfsnaam. 

Opmerking: 
Wanneer een shortcode wordt gebruikt maar de bijbehorende waarde leeg is, wordt bij het renderen geen data weergegeven. 

 

Enthousiast? Doe de quickscan


Zie direct of jouw maakbedrijf en ons platform een perfecte match zijn.

Boek een demo