feat: App Guide component

[JoeRodriguez-136]

Summary

• Update the component to render a multi-page guide panel with placeholder data
• Add a demo page to show the component in context
• Move tests to a different folder

[rslibed]

Is the header content going to be configurable? If so, it seems like this would be text that it can default to

App Guide will need to be translated so I think it'd good to move the string into the t9n files and load the messages through the getMessages util.

Here's how's it's implemented in the other components:
https://github.com/Esri/instant-apps-components/blob/master/packages/instant-apps-components/src/components/instant-apps-social-share/instant-apps-social-share.tsx#L253

[JoeRodriguez-136]

The header of the component (App Guide) will not be configurable, though the title of the content area (in bold below the divider line) will be. The app guide string has been added to the t9n file; I'll wire it up with getMessages.

[kellyhutchins]

Is the text "App Guide" going to appear in the component header? If so then I think it needs to be configurable. I don't think users will always want this text visible?

[JoeRodriguez-136]

@kellyhutchins I'll chat with Design about this. We hadn't talked about that header being configurable or optionally hidden.

[JoeRodriguez-136]

For now I've added a property that will allow the header to be hidden. I've also wired up the translated strings to the header text.

[rslibed]

Looks good! Left some comments. Once addressed, i think it'd be fine to merge to the dev branch

[rslibed]

Just curious, was there a reason to not use ids/class names for css selectors?

[JoeRodriguez-136]

Yep, the couple of factors I considered were that web component styles won't get polluted by outside stylesheets, and the simplicity of the component markup made element selectors seem reasonable.

Per our conversation, as the component evolves and new features are added I will definitely re-evaluate whether this approach needs to change in favor of more specific selectors.

Also, depending on the particulars of the testing framework, I may need to add classes or IDs to support automated testing (more on that in a future PR).

[github-actions]

instant-apps-components

The following PR has been closed and merged. - link to PR

• NPM Version: 1.0.0-beta.260
  -link
• Repo Version: 1.0.0-beta.255
  -link

If you want to publish, your Repo version should be updated and differ from the current version on NPM

To publish instant-apps-components to NPM

If you would like to follow this PR up with a publish, please proceed to the actions tab and manually run the publish.