Skip to content

Implement add-ons to improve developer engagement #211

Closed
@LakshmiLavanyaKasturi

Description

@LakshmiLavanyaKasturi

Big thinking: site arch and UIUX.

API Try-it experience

  • Come up with Redoc tool or any other tool that can integrate with Docusaurus for a try-it experience.
  • UI/UX design on how the API Try-it experience would look like.
  • Design wireframes for high-level docs site vision.
  • Get the wireframe flow from the Hiro docs landing page to the product-specific documentation pages.
  • Check if docusaurus supports multi tiles on the documentation page. Eg: Top level tile would have How-to-articles and the lower level would have how-to-article-1, how-to-article-2 etc.
    Eg: https://developers.facebook.com/support/

Vote-up/down button. (Thumbs up/down)

  • Placement of the button.
  • Decide the text.
  • Thumbs down shows up a text box to enter a reason for thumbs down.
  • Work with UI/UX team to come up with the design for including this feature.
  • brainstorm if the following tools would be sufficient. amplitude, hotjar, Google analytics

Product Changelog

  • Work with Marketing (Elena, Max, Brian) to determine what content will be included in the Product Changelog
  • Decide where to place the link to the Product Changelog. Should it be added to the horizontal tabs at the top of the page? How about in the left navigation pane? Botton of the page?
  • Create Changelog Slack Channel and work with Elena and Max to create Slackbot to ping PMs and Engineering Managers weekly to add any updates.
  • Changelog responsibilities will alternate between Lavanya and Thomas on a monthly basis

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions