Create wysiwyg_landing.txt

[jenbreese]

This is a landing page to link to the created sample content.

READY FOR REVIEW

• (Edit the above to reflect status)

Summary

• A sample of a landing page to show what might be new in a subtheme

Review By (Date)

• When does this need to be reviewed by?

Criticality

• How critical is this PR on a 1-10 scale? Also see Severity Assessment.
• E.g., it affects one site, or every site and product?

Urgency

• How urgent is this? (Normal, High)

Review Tasks

Setup tasks and/or behavior to test

1. Check out this branch
2. Rebuild Cache and import config drush cr ; drush ci
3. Navigate to...
4. Verify...

Site Configuration Sync

• Is there a config:export in this PR that changes the config sync directory?

Front End Validation

• Design is approved by @ user?
• HTML validation: Is the markup using the appropriate semantic tags and passes validation? Or, QA request ticket created?
• Cross-browser testing: Has been performed? Or, QA request ticket created?
• Visual regression testing: Has been performed? Or, QA request ticket created?
• Automated accessibility: Scans performed? Or, QA request ticket created?
• Manual accessibility: Manually tested? Or, QA request ticket created?

Backend / Functional Validation

Code

• Are the naming conventions following our standards?
• Does the code have sufficient inline comments?
• Is there anything in this code that would be hidden or hard to discover through the UI?
• Are there any code smells?
• Are tests provided? eg (unit, behat, or codeception)

Code security

• Are all forms properly sanitized?
• Any obvious security flaws or new areas for attack?

General

• Is there anything included in this PR that is not related to the problem it is trying to solve?
• Is the approach to the problem appropriate?

Affected Projects or Products

• Does this PR impact any particular projects, products, or modules?

Associated Issues and/or People

• JIRA ticket(s)
• Other PRs
• Any other contextual information that might be helpful (e.g., description of a bug that this PR fixes, new functionality that it adds, etc.)
• Anyone who should be notified? (@mention them here)

Resources

• Automated Accessibility Testing: Siteimprove
• Manual Accessibility Testing Script SWS Accessibility Process and Checklist
• HTML Validation for one URL: HTML Validator
• HTML Validation for multiple URLs: Bulk W3C Validator
• Crossbrowser Testing: Browserstack and link to Browserstack Credentials
• Visual Regression Testing: Diffy and link to Diffy Credentials

[cjwest]

Thanks, Jen!

I've tried to include ids with the headings for each example. I'm thinking we can add the anchors in here?

Would you like to give add them? If not I'm happy to do that.

[jenbreese]

Hi @cjwest How is this?

[cjwest]

Those ids will make it easier to link to. Thank you.

In looking at it, I do have another question: Under some headings you have a list with at least one item, under other headings you have an empty list, and under other headings you have no list. For the existing list, I would imagine I simply insert the URL. For the others, what are you expecting?

I guess I'm wondering if it would make more sense to have a list and an example link under each?