material-components / material-design-for-wordpress Goto Github PK

Material Design plugin for WordPress

JavaScript 49.51% CSS 15.65% Shell 0.91% Dockerfile 0.05% PHP 33.07% HTML 0.81%

material-design-for-wordpress's Introduction

Material Components: Shared Documentation and Policies

Material Components for Android, iOS, web and Flutter help developers execute Material Design with modular and customizable UI components. Developed by a core team of engineers and UX designers at Google, these components enable a reliable development workflow to build beautiful and functional user experiences.

This repo contains all common documentation for Material Components projects across the different platforms.

Repos

material-design-for-wordpress's People

Contributors

Stargazers

Watchers

Forkers

mulxcode strusovsky sm-125f shreya-spr thelawless1 patelutkarsh ashish168527 naolast liambirt jira-skins isabella232 chadjsdev mrarashel isabelle-c-s-oliveira daniel199604 domains-due stepwayexcellence physicsfamily devopsjohndoe

material-design-for-wordpress's Issues

Patterns/template in Gutenberg

Issue by jwold
Wednesday Mar 18, 2020 at 17:03 GMT
Originally opened as xwp/material-design-wp-plugin#107

Feature description

We also explored a template mode, where we've generated a number of templates, such as groups of blocks (patterns), or potentially pages (contact, about, services, tbd) and those can be added to the page by selecting them as a template. Similar to otter.

The challenge of having the demo page also as the Kitchen Sink is that there would be a difference between the two. On the Kitchen Sink

Todo

Write AC
Prototype design
Review #95 and #376 for additional AC

Explore block patterns to pull in demo content and help users to better explore the capabilities of Material. This could likely be a dozen or so patterns to best showcase the blocks in groupings.

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

Implementation brief

QA testing instructions

Demo

Changelog entry

Can't remove image from card

Issue by emeaguiar
Monday Mar 15, 2021 at 17:36 GMT
Originally opened as xwp/material-design-wp-plugin#564

Bug Description

The button to remove cards doesn't seem to work when clicked

Expected Behaviour

Clicking the X button in cards images should remove the image from card and display the media selector again.

Steps to reproduce

Go to edit post screen
Create a new card collection if needed
Add an image to any card
Hover over the top right corner of any card with an image, wait for the X button to appear
Click the button and confirm the image is NOT removed

Screenshots

Additional context

WordPress version:
Plugin version:
Gutenberg plugin version (if applicable):
PHP version:
OS:
Browser: Firefox
Device: [e.g. iPhone6]

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

Implementation brief

QA testing instructions

Demo

Changelog entry

Explore tonal color palette generation for users choosing colors in Material blocks

Issue by jwold
Monday Aug 10, 2020 at 18:33 GMT
Originally opened as xwp/material-design-wp-plugin#366

Feature description

We have another issue, #357, where we want to dynamically insert recommended colors for users of Material blocks, based on the style they've chosen. This issue explores whether we could add additional color palettes that compliment those colors.

Material docs reference

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

Implementation brief

QA testing instructions

Demo

Changelog entry

Centralize New Tab and Rel controls for InspectorControls

Issue by dugajean
Sunday Mar 15, 2020 at 16:14 GMT
Originally opened as xwp/material-design-wp-plugin#101

The settings to set if a link should go on a new tab and setting the link rel seem to be quite universal across our block. It makes sense to extract this behavior to its own component and make it easily reusable.

Block: Extend curated card collection to support Custom Post Types

Issue by jwold
Tuesday Mar 03, 2020 at 00:21 GMT
Originally opened as xwp/material-design-wp-plugin#66

Feature description

Currently the Curated Card Collection block allows for creating cards based on posts. We'd like to extend that to include cards from pages, and custom post types.

~~Inspiration: Hand-picked Products~~

~~Sorting: Need to think about that and the accessibility. (And filtering)~~

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

When using Curated Card Collection, I am able to filter by:
1. Posts and pages
2. Custom post types
As an editor, I am only able to select one content type at a time
When displaying filtering options, performance should be considered (See how curated block has a search and scrolling list of posts)
Only display the radio buttons for content selection if custom post types are available.
By default make posts and pages selected
~~Add ability to sort chosen cards~~ hold for now JNW
~~Extend recent posts block as well.~~ Hold for now JNW

Implementation brief

QA testing instructions

Demo

Changelog entry

USER JOURNEY MAP: Identify Issues

Issue by jauyong
Thursday Dec 10, 2020 at 19:36 GMT
Originally opened as xwp/material-design-wp-plugin#473

Feature description

Surface issues of friction and frustration as well as ease and validation along the way.

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

Document issues of friction and frustration as well as ease and validation along the way.

Implementation brief

QA testing instructions

Demo

Changelog entry

Add large size option to button

Feature description

As a site editor I want another button variation

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

Follow Material guidelines for sizing: https://material.io/components/buttons-floating-action-button
Add a size section above "variations"
1. Add options: regular, large(add padding)
Only show the size section when button style = text and variation != text
Use primary color by default

Implementation brief

QA testing instructions

Demo

Changelog entry

Block Pattern Setup

Feature description

Boilerplate code to be used for the patterns we will be building.

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

Boilerplate code is setup for building patterns

Implementation brief

QA testing instructions

Demo

Changelog entry

Improve Gallery (grid view) on Mobile

Issue by jauyong
Tuesday Jan 05, 2021 at 16:31 GMT
Originally opened as xwp/material-design-wp-plugin#491

Feature description

As a user, I would like an improved experience for the gallery block on a mobile device.

This came from Yasmine's request regarding to the grid view for the Gallery block on mobile. See slack message here.

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

Conduct quick competitive analysis of similar blocks in the WordPress space to identify the best method for showcasing gallery blocks and giving content creators the best controls to modify the experience. Reviewed by Joshua.
~~The labels do not need to be cut off but break on the word (ie multiple lines)~~ See #497
Allow admins to set number of columns per device (desktop, tablet, mobile). The following are the defaults:
1. desktop = 5 or 6,
2. tablet (768px) = 3 or 4,
3. mobile = 1
On mobile, I should be able to set 1 column

Implementation brief

QA testing instructions

Demo

Changelog entry

Fix Sort Order of Posts on Mobile for Masonry Layout

Issue by jauyong
Monday Feb 22, 2021 at 19:43 GMT
Originally opened as xwp/material-design-wp-plugin#549

Bug Description

Original Ticket: https://wordpress.org/support/topic/sort-order-of-last-posts-on-homepage/

In the masonry layout in the theme, the columns are two divs which hold all the posts and this changes the sort order for mobile

Note: Verify that this does not occur on the card blocks in the plugin

Expected Behaviour

On mobile, the order the posts are displayed in should be "correct" and match the order displayed on larger screen displays.

Steps to reproduce

Go to '...'
Click on '....'
Scroll down to '....'
See error

Screenshots

Additional context

WordPress version:
Plugin version:
Gutenberg plugin version (if applicable):
PHP version:
OS:
Browser: [e.g. chrome, safari]
Device: [e.g. iPhone6]

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

On mobile, the order the posts are displayed in should be "correct" and match the order displayed on larger screen displays.
Verify that this does not occur on the card blocks in the plugin

Implementation brief

QA testing instructions

Demo

Changelog entry

USER JOURNEY MAP: Document Journey

Issue by jauyong
Thursday Dec 10, 2020 at 19:38 GMT
Originally opened as xwp/material-design-wp-plugin#474

Feature description

This journey map encompass the primary critical user journeys for the plugin and theme.

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

Document the journey through the eyes of a specific user form a user group that is less technical who benefits from a solution that requires no real coding skills and wants to be able to customize the look and feel to meet their own style through the Material Design System - even if they do not know about Material Design.

Implementation brief

QA testing instructions

Demo

Changelog entry

[Pattern] Numbers

Feature description

NOTE: This is not actionable yet as we don't have a way to insert icons

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

I am able to add the Numbers Pattern
It should resemble the mockup attached
After adding the pattern it should have all blocks added to the post/page with demo material including:
1. Heading Block
2. Paragraph Block
3. 3 columns including:
  1. Icon Block
  2. Heading Block
  3. Paragraph Block

Implementation brief

QA testing instructions

Demo

Changelog entry

Applying Density

Issue by jwold
Thursday Feb 27, 2020 at 22:24 GMT
Originally opened as xwp/material-design-wp-plugin#56

Feature description - Post MVP

As a site owner I'd like the ability to change density on my site.

For this user story we'll just look at how it is applied globally. We can offer a control within the Customizer to set all components to Default, Comfortable, Compact.

This will need discussion, prototyping, and acceptance criteria.

Initial wireframe:

Concepts: article and demo

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

Implementation brief

QA testing instructions

Demo

Changelog entry

[PLUGIN] Keep Google Icons Up to date

Issue by jauyong
Monday Dec 07, 2020 at 14:17 GMT
Originally opened as xwp/material-design-wp-plugin#461

Feature description

I want access to the latest Google Icons.

Resources: https://developers.google.com/fonts/docs/developer_api
Related to #354
This ticket was split from #383

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

Icons should be able to be auto-updated (interval or auto-detection on when an update is available?)
Add an option to opt-out of auto-updates
A plugin update is not required to receive Icon updates
Performance should be kept in mind (e.g. use caching, not cron job, look at how PWAs work)

Implementation brief

Updates should happen when the Selector comes into focus in the Customizer
An update constitutes checking a transient in the database. If an install has an object cache, core behavior stores transients as cached items and reduces reads on MySQL.
A transient should have a 24h expiry to avoid overloading the Fonts API
If a transient exists, bail and let existing behavior read from local stored JSON file in assets/fonts/icons.codepoints.
If transient does not exist, or is expired, request new list from the Github Repo. https://raw.githubusercontent.com/google/material-design-icons/master/font/MaterialIcons-Regular.codepoints
For consistency and compatibility with npm.grunt, this file should be saved to assets/fonts/icons.codepoint
Subsequentally, the contents of this file needs to be split on linebreaks. PHP file() function does this.
The resulting array can be used to write to assets/fonts/icons.json.
Each line is formatted as name code and should be split again on a space to create a JSON object such as:

{
  "icons": {
    "e577": {
      "name": "360"
    },
    "e84d": {
        "name": "3d_rotation"
    }
}

QA testing instructions

Demo

Changelog entry

Carousel Block

Feature description

As a site editor I want a carousel block to display content

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

The carousel should have "dots" indicating pagination and location in the carousel
The carousel should have next and back buttons to manually scroll through the content
When the user selects "card collections" the only styling option we will include is "Outlined"
By default, pagination of the carousel should go post by post, not entire pages.

Implementation brief

QA testing instructions

Demo

Changelog entry

[Pattern] Hero Section

Feature description

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

base block should be a cover block with a set background color

Implementation brief

QA testing instructions

Demo

Changelog entry

Settings Page

Issue by jauyong
Thursday Feb 04, 2021 at 20:37 GMT
Originally opened as xwp/material-design-wp-plugin#534

Feature description

As a plugin user, I want to be able to manage my settings such as updating fonts and icons

This is a blocker to #460 and #461

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

Add a new settings page under the "Getting Started" tabs
Add option for manual icon update
Add option for manual font update
#537 Add option to delete cache, reset demo content, hard reset theme... @jauyong to create a ticket for this. need to identify what can be reset. This ticket will help users troubleshoot and get back to a stable default state.
Add any settings that affect the backend (ie settings that don't belong in the customizer)
Add API Key field
When the API key is entered and the user refreshes/returns to the page, the key should be hidden (like how passwords are treated) or consider removing the text field altogether. Also look at Github secrets.
Clicking on "activate Google API Key" first brings you down to the input field on the page.

Implementation brief

QA testing instructions

Demo

Changelog entry

Icon buttons should have Material-styled tooltips

Issue by jbingham
Wednesday May 06, 2020 at 16:28 GMT
Originally opened as xwp/material-design-wp-plugin#224

Bug Description

Material Icon Buttons currently show no tooltip when hovering.

Expected Behaviour

When hovering over a button, it's expected that a tooltip will appear. Usually the text is redundant with the button, but sometimes it's actually useful, like if it's an icon button with no text.

Steps to reproduce

Create a new post.
Add a Material Button block to it and set to icon
Preview.
Hover the mouse over of the button.
Note that there's no tooltip.

Screenshots

Additional context

The block editor would need a way to set the tooltip text.

Note that the Material guidelines do include Tooltips. The material-components-web repo does not provide css for them, though that's in the works.

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

When using an icon button, there is a way to set the tooltip display text
On the frontend when hovering over an icon button, the hover tooltip is displayed

Implementation brief

Add a new text field for button block which will show up only when the button is set to icon
The tooltip content can be entered/saved in the new field
Save component will save the tooltip markup

QA testing instructions

Demo

Changelog entry

USER JOURNEY MAP: Document Installation, Setup and Usage

Issue by jauyong
Thursday Dec 10, 2020 at 19:34 GMT
Originally opened as xwp/material-design-wp-plugin#472

Feature description

Screenshot and document (in Miro) your way through the process of downloading and setting up the theme and plugin, on-boarding, publishing a page, editing the global styles and setting up some blocks etc.

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

The entire process is documented/captured

Implementation brief

QA testing instructions

Demo

Changelog entry

Dark theme

Issue by jwold
Wednesday Mar 04, 2020 at 16:06 GMT
Originally opened as xwp/material-design-wp-plugin#76

Feature description

Material offers guidelines for creating dark and light theme UI. This is worth exploring for a future iteration.

https://material.io/design/color/dark-theme.html#

Examples: https://css-tricks.com/dark-modes-with-css/
Offer a dark/light mode toggle
Joshua to mock up what this looks like
Review guidance on applying https://material.io/design/color/dark-theme.html

Conditional:

Theme must be installed

Notes

Surface, and on-surface are two additional colors that the dark mode would need to reveal: https://d.pr/i/Dj7Y1Y
When you turn on dark mode, the surface colors will change to their respective opposites, and no actual user facing controls will be needed.
Border outline looks at on-surface and creates a relevant border as a result
We need to look at how other components are impacted. @ravichdev suggested he could compile a list.

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

Implementation brief

QA testing instructions

Demo

Changelog entry

USER JOURNEY MAP: Document Issues

Issue by jauyong
Thursday Dec 10, 2020 at 19:39 GMT
Originally opened as xwp/material-design-wp-plugin#475

Feature description

Capture and prioritize any issues that are found.

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

Capture and prioritize any issues that are found.

Implementation brief

QA testing instructions

Demo

Changelog entry

Assets directory inconsistency

Issue by dugajean
Wednesday Apr 29, 2020 at 20:27 GMT
Originally opened as xwp/material-design-wp-plugin#203

In the assets/ directory we have the following directories:

css
js
src

This doesn't make much sense, as src contains JS code which when compiled goes to the js folder. So now we have folder right under assets which include JS code.

This isn't the case for css. In this folder, we initially have all the compiled CSS and another inner src/ folder which contains the CSS we code in (assets/css/src).

This whole structure is quite messy and unintuitive to newcomers and should be changed into a more consistent structure.

Proposed solutions:

Have a css and a js folder right under assets; The compiled assets are right there under these folders, but there's also a src folder in each of these folders containing the actual source code. In short: replicate what CSS has to the JS side.
Have a css, a js folder and a dist folder - right under assets; This dist folder contains both compiled JS and CSS. The css and js folder hold their respective source files.

One of these two solutions guarantees consistency and reduces confusion at navigating theses project files.

Input welcome.

Curated Post Block: Improve Post List Display

Issue by jauyong
Thursday Dec 10, 2020 at 19:25 GMT
Originally opened as xwp/material-design-wp-plugin#470

Feature description

As an editor, I want a way to preview posts so that I can add the correct ones to my curated cards collection block.

Improve how posts are displayed when they have no title.

Current state:

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

In situations where Curated Posts (AKA hand-picked posts) show up with no title, show: (no title)
Clicking on the "preview" pill will open the post/page in a new tab
Fix rounded corners: https://d.pr/i/6hC3tF. The pill showing selected posts should encompass the full title

Design to implement:

Implementation brief

QA testing instructions

Demo

Changelog entry

Explore global settings for text fields

Issue by jauyong
Monday Dec 07, 2020 at 14:24 GMT
Originally opened as xwp/material-design-wp-plugin#462

Feature description

Add options in the Customizer for global settings for text field (outlined and filled)

This ticket was split from #362
Note: there was a similar discussion regarding round corners.
Question: What about theme options that cover the same settings?
Note: Design may be needed here.

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

When the Plugin and Theme are both active, "Outlined" vs "Filled" options are displayed in the Customizer's Material Design Options.
1. This sets the block level, contact form and comment form field options.
When the plugin is active but the theme is not, "Outlined" vs "Filled" options are displayed in the Customizer's Material Design Options.
1. This sets the block level and contact form field options. (Not the comment form fields)
When the theme is active but the plugin is not, "Comment field display options" will be used to set the comment form options (this is the current way)
Any text field should follow the guideline set above, unless a user has specifically chosen something at the block level.
Add toggle for text fields: Outlined or filled (should be called "Elevated" mocks were not updated")

Implementation brief

QA testing instructions

Demo

Changelog entry

[Pattern] CTA + Benefits

Feature description

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

Implementation brief

QA testing instructions

Demo

Changelog entry

Research Images for Patterns

Feature description

Dawid to list animations and images used in his patterns so the licensing details can be reviewed.

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

List and link to all animations and images used
Review licensing to determine if we can use these images.

Implementation brief

QA testing instructions

Demo

Changelog entry

Add Aria Labels

Issue by jauyong
Tuesday Dec 08, 2020 at 15:30 GMT
Originally opened as xwp/material-design-wp-plugin#468

Feature description

Placeholder ticket to add Aria Labels for Accessibility.
See comment
https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Techniques/Using_the_aria-label_attribute

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

Implementation brief

QA testing instructions

Demo

Changelog entry

Block: Tab Bar

Issue by jwold
Thursday Feb 13, 2020 at 22:29 GMT
Originally opened as xwp/material-design-wp-plugin#16

Feature description

Adds a Tab Bar block to organize and allow navigation between related groups of content.

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

Description: Tabs make it easy to explore and switch between different views.
Icon: tab-24px.svg from https://material.io/resources/icons/
By default block has two tabs.

Adding the block:

Tabs are labeled: Tab 1, Tab 2 (etc) by default.
Block will show Tab 1 on load.
Moving tabs left and right is done in the block toolbar.
The moving arrows should indicate when a tab has reached the start or end of the list by graying out the appropriate arrow
Width should be normal by default, in the block toolbar that can be changed to wide width and full width
When the number of tabs is greater than the width of the container they should convert to scrolling tabs, and should mimic the web component behavior https://material-components.github.io/material-components-web-catalog/#/component/tabs
The New tab button should always appear, even when scrolling left or right within the scrolling tabs.
Each tab can be removed by a delete icon. That icon should be centered with the label and should appear on hover.
The tab labels can be edited by selecting them and typing in a new label
Within each tab new blocks may be added, we should test the remaining Material blocks, and core paragraph, core image, core headline, core list, to ensure they function as expected.
The Tab Bar block should not be disabled from being added as a child block.
The font, colors, and icon type for this block can be changed from the Customizer

Block settings

An icon can be set as the leading or above icon.
When the icon is set to above, the indicator should be restricted to the width of the label, similar to the web component.
If you enable an icon, the favorite icon should appear by default as an example, allowing you to then change it.
From there you can't actually remove the icon from the icon picker, you can just turn it off by selecting Icon: None. But if you turn it back on it defaults to the last icon you used, or if you didn't use one, defaults to the Favorite icon.
In the icon picker you can search for an icon by its name
When you choose an icon you should see it selected in the icon list (highlighted with a blue background), and it should also appear beside the search input field, that way if you scroll past it you'll still know which icon you had selected.
Icon style should match the icon style set in Customizer. Cannot be changed at the block level.

Prototype:
See staging env, design prototype is outdated.

Figma link

Implementation brief

This issue requires the creation of three blocks: Tab Bar, Tab Menu Item and Tab Content. Tab Bar will serve as the parent or container for both tab menu item and tab content, and tab menu and tab content will need to have a one-to-one relationship using some sort of ID.
Tab Bar
- This block will allow the user to "scaffold" a tab system in their post. They will be presented with 1-2 sample tab menu items and they will see a "+" button to add more of those.
- The use of InnerBlocks will be required here, but limited to Tab Menu Item & Tab Content
- This block has no InspectorControls
- The user can delete the entire tab structure by deleting this block
- Which tab is active needs to be stored in the state at this level
Tab Menu Item
- User will be able to adjust individual Tab Menu Items to set their text/icon or delete them
- Clicking on a Tab Menu Item will show its related Tab Content. This will be made possible by the use of a relation identifier
- Tab Menu Items don't have a limited number and will be default have a horizontal scroll on if they don't fit in the screen
- This block is not visible in the Block context menu
Tab Content
- Needs a relation identifier with the Tab Menu Item
- Requires the use of InnerBlocks, any block should be allowed when editing

QA testing instructions

Note 1: With most of these changes you'll also want to see if the frontend is working, and not just the Gutenberg preview. It's possible there are discrepancies.

Note 2: For now we're just testing with the theme set in the staging env

Add the block and try placing a number of blocks within each tab
See how something with 1 tab functions, 2 tabs, and as much as 20 tabs.
Add icons to tabs
Change icon to leading and above and see if it matches the web component
See if the indicator, icon type, and font change when you update them in the Customizer.
Try moving a tab to the far right and left of the order and see if indicator updates
Change width of block
Delete tabs
Change labels of tabs

Demo

Changelog entry

Evaluate whether any theme JS could be done in CSS or with AMP components

Issue by mattchungxwp
Friday Sep 18, 2020 at 18:43 GMT
Originally opened as xwp/material-design-wp-plugin#401

This pertains to the JS modules listed here: https://github.com/xwp/material-theme-wp/tree/develop/assets/src/front-end/components The context is AMP-compatibility. While there are several things that would need to change to make the theme AMP-compatible, removing the reliance on JS is a big one. I know this isn't easy, so I suggest a tiered approach:

If there are any JS-based features that could be done with CSS transition or animations or in any browser-native way, then we can take care of that now. There may be no cases of this.
If there are any JS-based features that could potentially be made AMP compatible (or have AMP-compatible alternatives wrapped in checks for whether the plugin is active), we should note these and add them as new issues if they are not easily implemented now.
If there are any JS-based features that simply cannot be done in AMP, let's note these in this issue and then we can discuss what to do with them.

Block: Button

Issue by jwold
Thursday Feb 13, 2020 at 21:36 GMT
Originally opened as xwp/material-design-wp-plugin#9

Feature description

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

Adding the button

The block can be added from the block library, and should appear under Material Blocks
The icon should be crop_7_5 from: material.io/resources/icons
The description for the block: Buttons allow users to take actions, and make choices, with a single tap.
Block preview: None
By default the block will be set to Styles: Text, Container: Contained, Icon: None
The editable label should default to saying Button

Editing the button

Editing the label is done by selecting the label and typing into it.
Setting the button link is done by selecting the block and editing the link below the button
The link can be typed as a url, or you can search for an existing post/page on your site and it will find that.

Changing button settings

Setting the link rel and whether it opens in a new tab is done via the block sidebar.
In the block sidebar you can set whether the block is a button or an icon button.
If it's set as a button you can choose between Text, Outlined, Raised, Unelevated as the options. Here's a demo to check against from the actual web component: https://material-components.github.io/material-components-web-catalog/#/component/button

Icons

If button style is Text, you can add an icon at the beginning or end of the button by selecting Leading or Trailing. If you select one of those the button block should add the favorite icon immediately as an example, allowing you to then change it.
From there you can't actually remove the icon from the icon picker, you can just turn it off by selecting Icon: None. But if you turn it back on it defaults to the last icon you used, or if you didn't use one, defaults to the Favorite icon.
In the icon picker you can search for an icon by its name
When you choose an icon you should see it selected in the icon list (highlighted with a blue background), and it should also appear beside the search input field, that way if you scroll past it you'll still know which icon you had selected.
Icon style should match the icon style set in Customizer. Cannot be changed at the block level.

Colors

By default the button block should respect the colors set in the Customizer for the Material Design Style, changing it here will alter only this button instance
The default colors listed should reflect the main colors in the design style chosen, or the custom colors set in the Customizer.
You can also choose a custom color from the Material color palettes by clicking on Color palette.
You can also choose a custom color by selecting Custom Color, which shows a color wheel and allows entering a hex.
You can then clear the color by selecting Clear
~~Color palette borders correspond to darker variation of color~~ (don't believe this is necessary)
Background color only appears if container is outlined, raised, or unelevated
If non accessible colors, display notice warning in sidebar

Rounded Corners

Defaults to whatever is set by the design style chosen in Customizer
If the button is set to Container: Outlined, Container: Raised, Container: Unelevated, then you should be able to change the corner style from 0 to 20 (screenshot from shape scheme tool: https://d.pr/i/Mkg1qN)

Prototype:

Figma link

Styles
Styles.zip

Icon
crop_7_5-24px.svg.zip

Implementation brief

Icon picker:
- Find (or create) a JSON list of all icons
- Loop through this list and dynamically display all icons in a React component
- Handle click event and set state (or attribute) with clicked icon. Add .active class appropriately.
- Include component to the block settings
Color picker:
- @ravichdev
Rest of the settings
- Implement the rest of the settings, such as: buttons style, elevation, etc. These settings will potentially be separate React components so that they may be reused in other blocks.
- These settings directly affect how the button looks in the editor
- Use contentEditable to make the label of the button editable
- Use TextControl component to allow for user to change target URL. Switch to advanced URL picker soon.
- Button style applies a material class for: text, outlined, raised or unelevated
- Icon gets placed in front of the text and behind it. Conditionally show one based on which option was selected.
- Color pickers for background and text are basically inline styles being applied to the outest button container.
- If the style of the button has a background, we'll display a ContrastChecker component, checking the contrast between background and text, displaying a warning appropriately.
- The radius slider is a RangeControl component, which adjusts the inline styles of the outest button container to apply a border-radius
- The "open in new tab" toggle is a ToggleControl which when checked, stores _blank as the attribute value. We then apply this directly on the anchor element.
- The Link rel field is directly affected by the "open in new tab" toggle, having its value set to the appropriate new tab rel. User is able to override this as its a TextControl component.

QA testing instructions

Note 1: With most of these changes you'll also want to see if the frontend is working, and not just the Gutenberg preview. It's possible there are discrepancies.

Note 2: For now we're just testing with the theme set in the staging env, we'll need to come back later and test with the top five themes that we approve.

Add a new button block and see if the suggested defaults all work as expected
See if description and icon match AC
Change the label
Add a link, validate that it works when previewing block on frontend
Change button styles and see if they match the web component: https://material-components.github.io/material-components-web-catalog/#/component/button
See if opening link in new tab works
Change the font in the Customizer, publish it, and see if the button font updates.
Before you change the button color: Change the color in the Customizer, publish it, and see if the button color changes in the block to match Customizer (it should)
After you change the button color in the block, goes to the Customizer and change it, then come back to the block and see if it matches the Customizer (it shouldn't)
The colors shown as available should be the primary and secondary colors from the Customizer, but the primary should always be set by default. Ensure that these two colors match what's set in the Customizer.
See if accessibility notices appear when colors aren't accessible, and verify those notices match with the color tool https://material.io/resources/color/#!/?view.left=0&view.right=0 (screenshot: https://d.pr/i/75qBjI)
Change color from color palette, see if works as expected
Change color by selecting custom color, see if works as expected.
Try clearing color, when you clear it should revert to what is set in Customizer
Try adding leading and trailing icons and see if that matches the material web component
Ensure that the icon collection matches the style set in Customizer, try changing Customizer a few times to ensure that the icon collection updates in Gutenberg
Rounded corners should be changeable and match the shape scheme tool in terms of constraints. Screenshot: https://d.pr/i/Rz76Gc, link: https://material.io/design/shape/about-shape.html#shape-customization-tool

Demo

Video: https://d.pr/v/EJWiyN

Changelog entry

Block: Recent Posts

Issue by jwold
Thursday Feb 13, 2020 at 22:24 GMT
Originally opened as xwp/material-design-wp-plugin#14

Feature description

Displays a list of the most recent posts from your site. The posts are ordered inside of cards, and have styles to change the display order.

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

Adding the block

The block can be added from the block library, and should appear under Material Blocks
The icon should be "description" from: material.io/resources/icons
The description for the block: Display a list of your most recent posts.
Block preview in the block library: None

Previewing the block

The posts will appear as cards, which default to a Masonry style, 3 columns, and text above media
Within the block preview you may not interact with the preview, other than testing the ripple effect.
From the block toolbar you may change the width of the block between Normal Width, Wide Width, and Full Width

Block settings

From the block sidebar you may set the styles between Masonry, List, and Grid
On list mode images should be cropped to square
Columns may be adjusted from 2-4
Content layout may be adjusted between text above media, text over media, text under media. These will adjust the placement of the headline and subtitle in relation to the post image. These variants should be matched in the web component demo. https://material-components.github.io/material-components-web-catalog/#/component/card?type=basic
Number of posts defaults to a max of 12, and can be set as low as 1
The block elevation can be changed from outlined to elevated
The post meta settings can be enabled or disabled: post date, post content, featured image, comments count, post author.
The excerpt is controlled by a slider input, with a default value of 20 words, a min of 10, and a max of 30.
Category defaults to all, but can be changed via a select menu
The fonts, radius, colors, and icon type can be changed from the Customizer

Prototype:

Figma link

Styles
SVGs.zip

Icon
description-24px.svg.zip

Implementation brief

In JavaScript:
- Register a new Gutenberg block called "Recent Posts" under the "material" category
- Implement the block edit property breaking down the rendering of the block into separate components:
  - Inspector Controls for the block custom settings:
    - Block style implemented using the ImageRadioControl component (see #46) which will get an array of styles. Each style will have a src attribute which will be an SVG icon component.
    - Content settings:
      - Columns range as a RangeControl core component only visible when the style attribute value is Masonry or Grid .
      - Number of posts range as a RangeControl core component only visible when the style attribute value is Masonry or Grid.
      - Outlined toggle as a ToggleControl core component.
    - Post meta settings:
      - Post date toggle as a ToggleControl core component.
      - Post content toggle as a ToggleControl core component.
      - Max number of post content words range as a RangeControl core component, only visible when the Post content attribute is selected.
      - Feature image toggle as a ToggleControl core component.
      - Image size select as a SelectControl core component, only visible when the Feature image attribute is selected.
      - Comments count toggle as a ToggleControl core component.
      - Post author toggle as a ToggleControl core component.
    - Filtering settings (Category select) as a QueryControls. This component will have a categories list as a prop. The categories list will be fetch using the useEffect hook.
  - No posts found/ posts loading component as a Placeholder component. It will show a Spinner core component until the recents posts are being successfully fetched. If no posts are found it will show a textual information
  - Posts list component (supporting 3 layout: masonry, grid, list) and 2 single card layouts (vertical, horizontal). For the Masonry style, this component will make use of a Masonry component provided by the react-masonry-css external library. Otherwise it will be a custom component. This component will have a SinglePost custom component as a child called in a loop going through the recent posts array.
  - Augment the Edit rendering using withSelect to fetch the most recents posts.
Implement CCS styles
In PHP, implement a Recent Posts block class which will:
- Register the Recent Posts block, its default settings and callback for rendering
- Implement the backend rendering (See issue #43)
- Add a filter to augment the response of the Posts REST API to add comment counts, post author display name and url only when the endpoint is requested in the Gutenberg editor. This will allow to fetch the extra post information in the Javascript code.

QA testing instructions

Note 1: With most of these changes you'll also want to see if the frontend is working, and not just the Gutenberg preview. It's possible there are discrepancies.

Note 2: For now we're just testing with the theme set in the staging env

Adding the block

Add a new block

Previewing the block

Ensure the ripple effect works as expected
Verify that posts function in all 3 styles and all 3 content layouts with and without images
Test against the card component to validate whether the block overall follows the card guidelines https://material.io/develop/web/components/cards/
Ensure that the 3 styles appear as expected
Ensure that columns work as expected
Ensure that the width options in the block toolbar function correctly
Ensure that each of the post meta settings appear as expected
Test the post orders, may require adding comments to a few posts, and verifying the post publish dates
Test whether the block changes when the font, radius, colors, and icon type are changed in the Customizer

Demo

Changelog entry

Block: Recent Post enhancement

Issue by jwold
Friday May 08, 2020 at 17:51 GMT
Originally opened as xwp/material-design-wp-plugin#235

Feature description

Consider a toggle to switch between content/excerpt when users choose number of words in card content area.

https://d.pr/i/U05osk

Cathi: List mode was not called out specifically, however participants wanted to understand if text was pulled from an excerpt or the start of the content. As I understood it, would there be an option to to work with the “READ MORE” functionality where the content length can be manually set in post editor? or Would you be able to choose between pull from excerpt and pull form content… Does that make sense? It was an insight I thought.

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

Implementation brief

QA testing instructions

Demo

Changelog entry

Update Settings for Card Collections Block

Issue by jauyong
Monday Dec 07, 2020 at 14:36 GMT
Originally opened as xwp/material-design-wp-plugin#465

Feature description

Review Global vs child settings in the block and compare to how we’ve handled it before(list block).
See related ticket #377 #496

~~Note: consider using the in context menu as opposed to the side bar with options~~

Update the more settings side panel based on the mocks.

Design Mocks:

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

Side Panel settings should flow as follows:

Style
1. Masonry
2. List
3. Grid
Card Style
Corner Radius
Card Settings
1. Content Layout
2. Cards Layout
3. Columns
4. Gutter
Content

Implementation brief

QA testing instructions

Demo

Changelog entry

[Pattern] Logos

Feature description

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

Implementation brief

QA testing instructions

Demo

Changelog entry

Improve Plugin Activation Experience

Issue by jauyong
Wednesday Jan 27, 2021 at 18:19 GMT
Originally opened as xwp/material-design-wp-plugin#522

Feature description

Priority: Explore

Miro board link Issue 1

Issue 1: https://docs.google.com/spreadsheets/d/1PWNEY5L9neu1O10p2KGczON8_lWOCiXOUeGRFT3wz1k/edit#gid=0

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

Make it obvious to users which plugin is the Material plugin to be activated.
Test with users when needing both theme and plugin

Implementation brief

QA testing instructions

Demo

Changelog entry

Fix alignment on hand-picked posts

Issue by jwold
Friday Jun 19, 2020 at 19:16 GMT
Originally opened as xwp/material-design-wp-plugin#293

Bug Description

https://d.pr/i/UjwsD5

Spacing between icon and title
Chips cutting off on right
Overall aligned left, container cuts off on right

Expected Behaviour

Steps to reproduce

Go to '...'
Click on '....'
Scroll down to '....'
See error

Screenshots

Additional context

WordPress version:
Plugin version:
Gutenberg plugin version (if applicable):
PHP version:
OS:
Browser: [e.g. chrome, safari]
Device: [e.g. iPhone6]

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

Implementation brief

QA testing instructions

Demo

Changelog entry

USER JOURNEY MAP: Setup Environment

Issue by jauyong
Thursday Dec 10, 2020 at 19:33 GMT
Originally opened as xwp/material-design-wp-plugin#471

Feature description

Set up a fresh playground environment (or remove the plugin and theme from one) so we can install everything from scratch.

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

We have an environment to perform research on

Implementation brief

QA testing instructions

Demo

Changelog entry

Patterns/template in Gutenberg

Issue by jwold
Wednesday Mar 18, 2020 at 17:03 GMT
Originally opened as xwp/material-design-wp-plugin#107

Feature description

The challenge of having the demo page also as the Kitchen Sink is that there would be a difference between the two. On the Kitchen Sink

Todo

Write AC
Prototype design
Review #95 and #376 for additional AC

Explore block patterns to pull in demo content and help users to better explore the capabilities of Material. This could likely be a dozen or so patterns to best showcase the blocks in groupings.

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

Implementation brief

QA testing instructions

Demo

Changelog entry

Image size on homepage

Issue by jauyong
Tuesday Mar 16, 2021 at 14:35 GMT
Originally opened as xwp/material-design-wp-plugin#566

Bug Description

Original Ticket: https://wordpress.org/support/topic/image-size-on-homepage/

Note: this will happen for the plugin and the theme

Expected Behaviour

Steps to reproduce

Go to '...'
Click on '....'
Scroll down to '....'
See error

Screenshots

Additional context

WordPress version:
Plugin version:
Gutenberg plugin version (if applicable):
PHP version:
OS:
Browser: [e.g. chrome, safari]
Device: [e.g. iPhone6]

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

The image in the card layout is being set as a background-image (using css) to maintain the aspect ratio across all cards. Update it to use an img tag so WordPress can use srcset while also maintaining the aspect ratio.

Implementation brief

QA testing instructions

Card header image should use an img element.
Existing card blocks should continue to work in the block editor and frontend.

Demo

Changelog entry

[Pattern] Call to Action

Feature description

Note: how is different from the hero pattern? hero has a bigger head and a background image.

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

I am able to add the Call to Action Pattern
I am able to add the Call to Action + Benefits Pattern
They should resemble the mockups attached
After adding the Call to Action pattern it should have all blocks added to the post/page with demo material including:
1. Heading Block
2. Paragraph Block
3. Button Block
After adding the Call to ACtion + Benefits pattern it should have all blocks from the regular "Call to Action" pattern added to the post/page with demo material and also:
1. 3 Columns
2. Each column should contain 1 basic list item

Implementation brief

QA testing instructions

Demo

Changelog entry

[Pattern] Hero Section + Image

Feature description

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

Image licensing is fair use

Implementation brief

QA testing instructions

Demo

Changelog entry

Ability to Alert Users of New Features

Feature description

As Material, I want a way to alert users of new features or announcements

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

There should be a way to display an announcement or message when new features are released

Implementation brief

QA testing instructions

Demo

Changelog entry

Explore global settings for cards

Issue by jauyong
Monday Dec 07, 2020 at 14:26 GMT
Originally opened as xwp/material-design-wp-plugin#463

Feature description

Add options in the Customizer for global settings for cards (elevated and outlined).

This ticket was split from #362
Note: there was a similar discussion regarding round corners.
Question: What about theme options that cover the same settings?
Note: Design may be needed here.

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

See this miro board for visual breakdown

In the global settings, there should be a radio button option for Elevated
In the global settings, there should be a radio button option for Outlined
In the global settings, there should be a button labeled "reset"
1. Add description copy "Set all existing blocks to 'Inherit from Global'. Note this may change existing settings"
In the global settings, set the copy as:
1. Global styles will be applied to any new static block. This will not affect any local style overrides for supported blocks.
In the block settings, there should be a radio button option for "Inherit from Global Settings"
1. This should be the default for any new blocks
In the block settings, there should be a radio button option for Elevated
In the block settings, there should be a radio button option for Outlined

Implementation brief

There are 2 parts to this, a global control and the block-level control

At the Global level (in the customizer)
we have these options per setting

Default Outlined
Default Elevated

In the block control, we show following settings:

Inherit from Global
Outlined
Elevated

Reset buttons on customizer will update all existing posts and reset its attribute to inherit from global.

QA testing instructions

Demo

Changelog entry

[PLUGIN] Keep Google Fonts Up to date

Issue by jauyong
Monday Dec 07, 2020 at 14:15 GMT
Originally opened as xwp/material-design-wp-plugin#460

Feature description

I want access to the latest Google Fonts.

Resources: https://developers.google.com/fonts/docs/developer_api
Related to #354
This ticket was split from #383

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

Fonts should be auto-updated (interval or auto-detection on when an update is available)
Add an option to opt-out of auto-updates
A plugin update is not required to receive Font updates
Performance should be kept in mind (e.g. use caching, not cron job, look at how PWAs work) (nice to have)

Implementation brief

Updates should happen when the Selector comes into focus in the Customizer
An update constitutes checking a transient in the database. If an install has an object cache, core behavior stores transients as cached items and reduces reads on MySQL.
A transient should have a 24h expiry to avoid overloading the Fonts API
If a transient exists, bail and let existing behavior read from local stored JSON file in assets/fonts/google-fonts.json.
If transient does not exist, or is expired, request new list from the Google Fonts API. https://www.googleapis.com/webfonts/v1/webfonts?key={key}&fields=items(category,variants,family)
Because the JSON payload provided by Google does not match the format currently used, perform a simple transformation and write to the existing file. This is a small transform that moves the family property from the payload to the key. This will allow existing functionality to continue to work with no further compatibility layer.
Write the transformed JSON to assets/fonts/google-fonts.json for future use and npm.

Existing Format

{
	{
      "family": "Roboto",
      "variants": [
        "100",
        "100italic",
        "300",
        "300italic",
        "regular",
        "italic",
        "500",
        "500italic",
        "700",
        "700italic",
        "900",
        "900italic"
      ],
      "category": "sans-serif"
    }
}

Google JSON format

{
    "Roboto": {
        "variants": [
            "100",
            "100italic",
            "300",
            "300italic",
            "regular",
            "italic",
            "500",
            "500italic",
            "700",
            "700italic",
            "900",
            "900italic"
        ],
        "category": "sans-serif"
    }
}

QA testing instructions

Demo

Changelog entry

Update theme to follow plugin's code standards

Feature description

With the merge of the theme into the repo several errors are displayed by the Sniffer, these need to be updated to pass the checks, example:

theme/template-parts/menu-tabs.php:43:25: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/search.php:40:67: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/template-parts/post-nav-links.php:26:18: warning - get_previous_post_link() is highly discouraged due to not being cached; please use wpcom_vip_get_adjacent_post() instead. (WordPressVIPMinimum.Functions.RestrictedFunctions.get_adjacent_post_get_previous_post_link)
theme/template-parts/post-nav-links.php:27:18: warning - get_next_post_link() is highly discouraged due to not being cached; please use wpcom_vip_get_adjacent_post() instead. (WordPressVIPMinimum.Functions.RestrictedFunctions.get_adjacent_post_get_next_post_link)
theme/searchform.php:38:123: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/template-parts/content-none.php:32:94: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/template-parts/content-none.php:41:99: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/template-parts/content-none.php:42:21: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/template-parts/content-none.php:43:32: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/template-parts/content-none.php:44:39: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/template-parts/content-none.php:52:130: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/template-parts/content-none.php:54:125: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/admin.php:51:34: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/admin.php:52:47: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/admin.php:55:35: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/admin.php:88:36: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/admin.php:115:55: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/admin.php:126:25: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/admin.php:138:29: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/admin.php:142:21: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/inc/admin.php:142:35: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/inc/admin.php:142:52: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/inc/admin.php:155:16: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/inc/admin.php:156:9: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/inc/admin.php:157:58: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/admin.php:163:15: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/inc/widgets/class-wp-widget-categories.php:48:97: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/widgets/class-wp-widget-categories.php:63:21: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/inc/widgets/class-wp-widget-categories.php:76:76: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/404.php:36:107: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/404.php:40:187: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/class-menu-drawer-walker.php:38:25: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/inc/class-menu-drawer-walker.php:52:68: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/inc/widgets/class-wp-widget-meta.php:46:91: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/widgets/class-wp-widget-meta.php:60:136: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/widgets/class-wp-widget-meta.php:61:146: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/widgets/class-wp-widget-meta.php:76:68: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/widgets/class-wp-widget-meta.php:77:50: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/template-parts/content.php:49:64: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/template-parts/content.php:84:37: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/template-parts/posts-navigation.php:39:34: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/template-parts/posts-navigation.php:45:37: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/template-parts/posts-navigation.php:51:33: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/template-parts/posts-navigation.php:57:33: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/template-parts/posts-navigation.php:77:64: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/template-parts/posts-navigation.php:92:52: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/template-parts/posts-navigation.php:105:48: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/template-parts/search-archive.php:36:107: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/template-parts/search-archive.php:44:78: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/template-parts/drawer.php:49:17: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/inc/class-menu-walker.php:38:25: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/inc/class-menu-walker.php:52:68: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/template-parts/back-to-top.php:34:94: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/widgets/class-wp-widget-pages.php:44:92: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/widgets/class-wp-widget-pages.php:78:17: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/template-parts/search-header.php:34:63: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/template-parts/search-header.php:35:53: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/template-parts/search-header.php:42:69: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/template-parts/search-header.php:44:185: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/customizer/header-footer.php:47:59: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/customizer/header-footer.php:64:51: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/customizer/header-footer.php:69:66: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/customizer/header-footer.php:74:76: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/customizer/header-footer.php:76:106: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/customizer/header-footer.php:80:60: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/customizer/header-footer.php:83:55: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/customizer/header-footer.php:84:52: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/customizer/header-footer.php:90:60: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/customizer/header-footer.php:91:149: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/customizer/header-footer.php:97:49: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/customizer/header-footer.php:103:54: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/customizer/header-footer.php:109:66: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/customizer/header-footer.php:148:13: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/inc/customizer/header-footer.php:159:13: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/inc/customizer/header-footer.php:170:13: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/inc/customizer/header-footer.php:181:13: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/inc/customizer/header-footer.php:192:13: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/inc/customizer/header-footer.php:242:16: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/inc/customizer/header-footer.php:242:60: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/customizer/header-footer.php:255:13: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/inc/customizer/header-footer.php:257:113: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/template-parts/single-page.php:42:13: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/template-parts/single-page.php:43:121: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/template-parts/single-page.php:57:80: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/template-parts/single-page.php:58:25: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/template-parts/single-page.php:59:39: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/template-parts/single-page.php:60:44: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/template-parts/menu-header.php:51:152: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/comments.php:58:52: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/comments.php:75:37: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/comments.php:91:38: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/comments.php:106:40: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/comments.php:119:36: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/comments.php:153:102: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/comments.php:167:56: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/comments.php:171:131: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/comments.php:179:17: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/comments.php:194:78: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/template-parts/single.php:61:90: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/template-parts/single.php:62:21: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/template-parts/single.php:63:35: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/template-parts/single.php:64:40: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/template-parts/single.php:73:13: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/template-parts/single.php:74:121: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/widgets/class-wp-widget-recent-comments.php:50:106: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/widgets/class-wp-widget-recent-comments.php:74:17: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/inc/widgets/class-wp-widget-recent-comments.php:98:60: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/template-parts/site-title.php:43:84: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/template-parts/site-title.php:60:84: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/customizer/layout.php:47:52: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/customizer/layout.php:101:60: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/customizer/layout.php:104:49: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/customizer/layout.php:105:51: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/customizer/layout.php:110:54: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/customizer/layout.php:113:48: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/customizer/layout.php:114:54: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/customizer/layout.php:119:70: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/customizer/layout.php:125:58: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/customizer/layout.php:131:56: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/customizer/layout.php:137:57: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/customizer/layout.php:143:54: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/customizer/layout.php:149:58: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/customizer/layout.php:155:71: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/customizer/layout.php:159:55: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/customizer/layout.php:160:53: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/widgets/class-wp-widget-recent-posts.php:48:103: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/widgets/class-wp-widget-recent-posts.php:73:17: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/inc/widgets/class-wp-widget-recent-posts.php:97:102: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/customizer/menu.php:51:88: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/customizer/menu.php:68:35: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/customizer/menu.php:69:63: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/functions.php:65:13: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/functions.php:66:49: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/functions.php:67:51: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/functions.php:77:13: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/functions.php:96:13: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/functions.php:134:9: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/functions.php:135:59: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/functions.php:137:65: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/functions.php:146:9: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/functions.php:147:60: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/functions.php:149:66: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/functions.php:166:77: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/functions.php:168:141: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/functions.php:182:120: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/inc/jetpack.php:39:9: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/inc/jetpack.php:52:9: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/inc/jetpack.php:53:34: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/inc/jetpack.php:61:34: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/header.php:45:102: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/template-functions.php:66:24: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/inc/template-functions.php:85:17: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/inc/widgets/class-wp-widget-rss.php:58:51: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/inc/widgets/class-wp-widget-rss.php:79:77: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/widgets/class-wp-widget-rss.php:112:58: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/inc/widgets/class-wp-widget-rss.php:124:64: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/widgets/class-wp-widget-rss.php:129:25: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/inc/widgets/class-wp-widget-rss.php:146:125: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/widgets/class-wp-widget-rss.php:162:50: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/template-tags.php:68:61: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/template-tags.php:139:60: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/template-tags.php:178:94: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/template-tags.php:179:25: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/inc/template-tags.php:180:39: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/inc/template-tags.php:181:44: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/inc/template-tags.php:195:76: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/template-tags.php:238:17: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/inc/template-tags.php:240:25: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/inc/widgets/class-wp-widget-archives.php:44:95: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/widgets/class-wp-widget-archives.php:77:17: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)
theme/inc/widgets/class-wp-widget-archives.php:87:57: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/widgets/class-wp-widget-archives.php:90:58: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/widgets/class-wp-widget-archives.php:93:56: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/widgets/class-wp-widget-archives.php:96:57: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/widgets/class-wp-widget-archives.php:99:57: error - Mismatched text domain. Expected 'material-design' but got 'material-design-google'. (WordPress.WP.I18n.TextDomainMismatch)
theme/inc/widgets/class-wp-widget-archives.php:142:21: error - Short array syntax must be used to define arrays (Generic.Arrays.DisallowLongArraySyntax.Found)

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

Implementation brief

QA testing instructions

Demo

Changelog entry

[Pattern] Features (button)

Feature description

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

I am able to add the Features Pattern
It should resemble the mockup attached
After adding the pattern it should have all blocks added to the post/page with demo material including:
1. Heading Block
2. Paragraph Block
3. 3 columns including:
  1. Icon Block
  2. Heading Block
  3. Paragraph Block
  4. Button Block

Implementation brief

QA testing instructions

Demo

Changelog entry

Saving design styles

Issue by jwold
Monday Apr 13, 2020 at 15:03 GMT
Originally opened as xwp/material-design-wp-plugin#144

Feature description

Explore the best way to handle users saving their own changes from within the Customizer user interface. That way they can style their theme, and save the style as an option alongside the default options.

At the end of this Sprint we'll have a solution ready for development. So this is primarily a design task.

As a user I should be able to give another user my material theming so they can get started from my elements. Long term Material gallery.

[Figma prototype]

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

This is mostly theme styles, but templates could be relevant.
Material doesn't have a way to save Custom theme.
So we must have a backlog item for some kind of Changesets, some capability for saving and editing.
As simple as saving your custom theme, maybe sharing is another issue.
In future they'd like to have a different theming tool, export it, and import into Customizer.

Insight from user research: Some clicked to edit the custom style - were frustrated not clickable. They would like to be able to save their own custom style and rename it to use later.

Implementation brief

QA testing instructions

Demo

Changelog entry

Enable auto updates for plugin and theme

Issue by jwold
Friday Aug 21, 2020 at 16:21 GMT
Originally opened as xwp/material-design-wp-plugin#380

Feature description

There are additional update features available to plugins and themes related to updating (with WP 5.5). We can point to a file now somewhere and have that be updated.

That way, once the plugin/theme are in .org, it will allow for smoother flows with updating to the latest versions.

See #460 #461

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

A user is able to receive auto-updates
A user is able to opt-out of auto-updates

Implementation brief

QA testing instructions

Demo

Changelog entry

Add tooltips to Tab Bar

Issue by jwold
Monday May 25, 2020 at 16:16 GMT
Originally opened as xwp/material-design-wp-plugin#258

Feature description

There are times when the tab bar headings can be set without labels. In this scenario an icon is added without a label. We should ensure that the icon can be given a tooltip.

Acceptance criteria

Handle this however we handle the Icon Button block.

Add a new label input field into the block sidebar.
Allow the new field to be visible regardless of whether there is a heading on the tab or not.

Note: Similar to #224 where we could add a field in the block sidebar settings to add a tooltip.

Implementation brief

QA testing instructions

Demo

Changelog entry

Keep Plugin and Theme Versions the Same

Issue by jauyong
Friday Feb 19, 2021 at 18:20 GMT
Originally opened as xwp/material-design-wp-plugin#543

Feature description

As a support member/troubleshooter, I want the Plugin and Theme to maintain the same version numbers for quick identification of issues.

Do not alter or remove anything below. The following sections will be managed by moderators only.

material-components / material-design-for-wordpress Goto Github PK

material-design-for-wordpress's Introduction

Material Components: Shared Documentation and Policies

Repos

Useful Links

material-design-for-wordpress's People

Contributors

Stargazers

Watchers

Forkers

material-design-for-wordpress's Issues

Feature description

Acceptance criteria

Implementation brief

QA testing instructions

Demo

Changelog entry

Bug Description

Expected Behaviour

Steps to reproduce

Screenshots

Additional context

Acceptance criteria

Implementation brief

QA testing instructions

Demo

Changelog entry

Feature description

Acceptance criteria

Implementation brief

QA testing instructions

Demo

Changelog entry

Feature description

Acceptance criteria

Implementation brief

QA testing instructions

Demo

Changelog entry

Feature description

Acceptance criteria

Implementation brief

QA testing instructions

Demo

Changelog entry

Feature description

Acceptance criteria

Implementation brief

QA testing instructions

Demo

Changelog entry

Feature description

Acceptance criteria

Implementation brief

QA testing instructions

Demo

Changelog entry

Feature description

Acceptance criteria

Implementation brief

QA testing instructions

Demo

Changelog entry

Bug Description

Expected Behaviour

Steps to reproduce

Screenshots

Additional context

Acceptance criteria

Implementation brief

QA testing instructions

Demo

Changelog entry

Feature description

Acceptance criteria

Implementation brief

QA testing instructions

Demo

Changelog entry

Feature description