I'm Bluffing

Let me start of with a general clarification for those of you who have little to no experience with SXA. With Sitecore Experience Accelerator, data sources can still be stored in multiple places. And by default, your page's datasources will be stored either under a site-wide data folder node or the data folder located underneath your actual page. Meaning that everything related and uniquely linked to a page is simply nested underneath that page and those blocks of content that allow further re-use are found on a higher data-repository level. When adding a new component you are presented with the following option to select or create a new piece of associated content: However, from time to time some unexpected behavior might pop up. Sitecore, by default, will use the Sitecore GUID as reference point for the datasource location in your presentation properties. However, with SXA, the relative path of your datasource is used instead SXA chose this approach to make the ...

General setup   After setting up your SXA project, one of the next things you typically want to do is follow a myriad of guides to help finalize your setup. One of these is to set up Security based on the SXA sites. In order to do this, a number of the powershell scripts exist that are offered by the SXA product out of the box to help you set up the Tenant as well as the Site Security. You can find all relevant information her: https://doc.sitecore.net/sitecore_experience_accelerator/setting_up_and_configuring/setting_up/set_up_security_for_a_tenant_and_a_site After you do this, I did however notice a problem... We created a number of editors that had the 'Site author' and 'Site designer' roles. However, the created users were not able to do all necessary actions immediately. This user is now indeed able to log in and see and edit that SXA site. First issue But when we performed the following test: Create a new page (Page type) > go into th...