transcom / move.mil Goto Github PK

Thanks for submitting an issue! Below are a few things you can do to help us more quickly address the issue.

Checklist

I have…

• described in detail below both the behavior I expected and the behavior I observed.
• attached screenshots illustrating relevant behavior.

Description: As a frontend developer I need to configure the pro-tip paragraph type to match the move.mil look and feel so that users experience a consistent style.

AC: After entering content into a pro-tip paragraph type, a site visitor needs to see a 1-1 representation of the LIVE move.mil pro-tip callout on the new D8 instance.

Details:

Example Page on LIVE - columned pro-tip
Example Page on LIVE - full pro-tip

Screenshot of Pro-tip on LIVE - columned pro-tip

Screenshot of Pro-tip on LIVE - full pro-tip

I have…

• described in detail below both the behavior I expected and the behavior I observed.
• attached screenshots illustrating relevant behavior.

Expected Behavior

Description: As a frontend developer I need to configure the basic text paragraph type to match the move.mil look and feel so that users experience a consistent style.

AC: After entering content into a basic text paragraph type, a site visitor needs to see a 1-1 representation of the LIVE move.mil display on the new D8 instance.

Screenshots

Screenshot from live move.mil site

Screenshot of same section recreated in local environment:

Checklist

I have…

• described in detail below both the behavior I expected and the behavior I observed.

Expected Behavior

.gitignore our themes asset directory generated by the uswds node module so that we do not have to worry about committing them from our local build

Observed Behavior

these assets were committed in an issue c9ead7b , so those will need to be removed.

The default menus in drupal are not really usable. As a user I should be able to find nested menu links without having to do multiple page loads.

https://www.drupal.org/project/admin_toolbar is pretty standard on any drupal project, and improves the administration interface and allows sub menus to be displayed in the parent.

Would like to have as close to, zero conf local environment for easy developer access.
Will need instructions, docker-compose, .env, and a instructions page.

Moving from npm scripts and a git included assets folder to gulp and assets generated dynamically in both dev and prod. Builds on Issue #30

Thanks for submitting an issue! Below are a few things you can do to help us more quickly address the issue.

Checklist

I have…

• described in detail below both the behavior I expected and the behavior I observed.
• attached screenshots illustrating relevant behavior.

Expected Behavior

As a frontend developer I need to configure the Tutorial Content type Tutorial Slideshow to match the move.mil look and feel so that users experience a consistent style.

note: Carousel should meet WCAG AA compliance for interactions on screen readers and on-key actions

Example tutorial on the LIVE site

Screenshots

I have…

• described in detail below both the behavior I expected and the behavior I observed.
• attached screenshots illustrating relevant behavior.

Expected Behavior

Description: As a frontend developer I need to configure the warning/callout box paragraph type to match the move.mil look and feel so that users experience a consistent style.

AC: After entering content into a warning/information paragraph type, a site visitor needs to see a 1-1 representation of the LIVE move.mil alert/information callout on the new D8 instance.

Note there are three different types of callouts, each with a different color scheme. They might or might not easily inherit uswds defaults, and we will have to determine whether custom markup or other overrides are necessary.

Screenshots

Screenshot from live site:

https://d.pr/i/XYircD

Screenshot from local:

Note: margin around/between the boxes will come later. That's a different matter....this is for the boxes themselves.

Checklist

I have…

• described in detail below both the behavior I expected and the behavior I observed.
• attached screenshots.

Expected Behavior

Using the custom menu module created in #27, theme our menu items to reflect the current live site.

Screenshots

Desktop

Mobile

Thanks for submitting an issue! Below are a few things you can do to help us more quickly address the issue.

Checklist

I have…

• described in detail below both the behavior I expected and the behavior I observed.
• thoroughly outlined below the steps to reproduce this issue, including relevant technical details (e.g. device, operating system, browser, browser version).
• attached screenshots illustrating relevant behavior.

Expected Behavior

Summarize expected behavior.

Observed Behavior

Summarize observed behavior.

Steps to Reproduce

To reproduce this issue…

1. Describe step one.
2. Describe step two.
3. etc. etc. etc.

Screenshots

Attach relevant screenshots here.

Checklist

I have…

• described in detail below both the behavior I expected and the behavior I observed.
• attached screenshots illustrating relevant behavior.

Expected Behavior

Description: As a frontend developer I need to configure the Tutorial Content type Tutorial Step to match the move.mil look and feel so that users experience a consistent style.

AC: After entering content into a Tutorial Step in the Tutorial Content type, a site visitor needs to see a 1-1 representation of the LIVE move.mil text w/ image display on the new D8 instance.

Example tutorial on the LIVE site

Screenshots

Related to https://www.pivotaltracker.com/story/show/156553093

Checklist

I have…

• described in detail below both the behavior I expected and the behavior I observed.
• thoroughly outlined below the steps to reproduce this issue, including relevant technical details (e.g. device, operating system, browser, browser version).
• attached screenshots illustrating relevant behavior.

Expected Behavior

Summarize expected behavior.

Observed Behavior

Live site FAQ's (initial state):

Live site FAQ's (accordion opened):

Steps to Reproduce

To reproduce this issue…

https://www.move.mil/faqs

Screenshots

Attach relevant screenshots here.

Checklist

I have…

• described in detail below both the behavior I expected and the behavior I observed.
• attached screenshots illustrating relevant behavior.

Expected Behavior

Description: As a frontend developer I need to configure the basic text paragraph type to match the move.mil look and feel so that users experience a consistent style.

AC: After entering content into a text w/ image paragraph type, a site visitor needs to see a 1-1 representation of the LIVE move.mil text w/ image display on the new D8 instance.

Screenshots

Example Page on LIVE

Screenshot of LIVE

Thanks for submitting an issue! Below are a few things you can do to help us more quickly address the issue.

Checklist

I have…

• described in detail below both the behavior I expected and the behavior I observed.
• attached screenshots illustrating relevant behavior.

Expected Behavior

Description: As a frontend developer I need to configure the customer service callout paragraph type to match the move.mil look and feel so that users experience a consistent style.

AC: After entering content into the customer service paragraph type, a site visitor needs to see a 1-1 representation of the LIVE move.mil customer service callout on the new D8 instance.

Service-Specific Pages w/Customer Service Info

Screenshots

Desktop

Mobile (note the accordion-ized content)

Mobile accordion-closed

we need to set up an automated test runner for coding standards and unit testing

currently the dev header appears like this

AC:
we would like for it to look like this

this may include work from #17

note* nav is handled in a different issue

Currently we are placing the logo and favicon in our public files - let's update to a custom path of in our codebase.

AC:
logo and icon are not pulling from the public files directory.

Checklist

I have…

• described in detail below both the behavior I expected and the behavior I observed.
• thoroughly outlined below the steps to reproduce this issue, including relevant technical details (e.g. device, operating system, browser, browser version).
• attached screenshots illustrating relevant behavior.

Expected Behavior

Summarize expected behavior.

Observed Behavior

Text in this intro section has custom padding and a blue background.

Example screenshot from live site:

Steps to Reproduce

To reproduce this issue…

1. Describe step one.
2. Describe step two.
3. etc. etc. etc.

Screenshots

We'll want to create a nice contributions.md so that commit pr guidelines are outlined.

Checklist

I have…

• described in detail below both the behavior I expected and the behavior I observed.
• thoroughly outlined below the steps to reproduce this issue, including relevant technical details (e.g. device, operating system, browser, browser version).
• attached screenshots illustrating relevant behavior.

See this issue in Pivotal

Expected Behavior

As a front-end developer, I want to be able to draw upon default styles for each heading type (h1, h2 etc) to match the current move.mil look and feel.

AC: All page titles and section headers using

or lower-level heading elements use primary move.mil blue and include a bottom border, unless overriden in specific instances.

Live Site treatment to migrate

Page title on live site:

h2 section header on live site

Steps to Reproduce

To reproduce this issue…

1. Pull code
2. run npm install, then npm run clean, then npm run build
3. Create a new test page, add some h1, h2 etc elements in a wysiwyg field, and see how they render

Screenshots

• Will add once complete