As a Marketer, I want to have my home (default) page created as a content page so that I can benefit from latest page fragment features and the creation flexibility it provides

• Type: Story
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: Master
• Component/s: Page Templates
• Labels:
  • 7.3-ce-ga3
  • d_20_03
  • fc_20_03
  • fc_20_04
  • pt-app-security-review
  • pt-upgrade-review
• Epic/Theme:
  • Convert_to_Content_Pages
• Git Pull Request: https://github.com/jkappler/liferay-portal/pull/721
• QA Test Name:
  • LocalFile.ToggleControls#HideAndShowExistingInvisiblePortlet
  • LocalFile.ToggleControls#ToggleControlsOnlyAffectCurrentInstance
  • LocalFile.WidgetPages#EditSitePage
  • LocalFile.XSS#ValidateXSSVulnerabilities
• QA Test Score: 18

Business Value / Motive

When starting a new site a default home page is created. Today this is by default created as a page based on a default widget template. But as we are moving toward being fragment oriented we need the default home page to be created with the default content page. The user will then be able to benefit from the new features introduced with the fragments capabilities.

 Acceptance Criteria

Given the "Home" page /web/guest is set as a content page

When a new liferay instance is initiated

Then users can modify the Home page layout using fragments

 

Test Scenarios

Test Scenarios	Test Strategy	Kind of test	Is it covered by FrontEnd ? (JS-Unit)	Is it covered by BackEnd ? (unit or integration)
The Home page is a content page in the default site	Smoke	Manual	No	No
The Home page is a content page in the new virtual instance	Smoke	Manual	No	No
The Home page is a widget page in the default site when upgrade from 7.2	Sanity	Manual	No	No
The Welcome page is a widget page in the default site when upgrade from 7.1	Sanity	Manual	No	No
The Welcome page is a widget page in the default site when upgrade from 7.0	Sanity	Manual	No	No