User Story:
As a (technical) user, I would like an example of using the Enterprise APIs (Structured Contents) to generate user friendly knowledge panels / knowledge cards, including the embedded app and a walkthrough of the code behind it.

Objective (O2.KR1):
Documentation and content for Enterprise products is expanded to reduce the barrier to use for, and to enable further outreach efforts towards a broader range of organization reusers.

Context
This is building on the dogfooding use case of creating knowledge panels using Structured Contents endpoint: https://phabricator.wikimedia.org/T344890
Draft doc can be found in Drive "Blog post: Knowledge Panel with WME".

Acceptance criteria
Document that guides a potential user on how they would integrate Structured Contents API into their system to create knowledge cards or derivatives.

Things to consider:

• Which constraints has the team identified while scoping the work?
  • Main constraint here is time, we want to have some result within a sprint.
• How is the team considering impact and metrics?
  • It's not a high-impact ticket. Mainly in terms of metrics we are trying to attract new clients, increase website visits and although it's not yet objectively measured by us, simplify the onboarding process.
• Which potential risks has the team identified? How might they be mitigated?
  • Main risk is allocation of engineering resources from day-to-day engineering work. We are going to mitigate it by carefully choosing who we assign it to.`
• What data or evidence are we using to inform the scope?
  • We are basing our scoping decisions on the previously published posts.
• To what extent is there a need for cross-functional collaboration at this stage?
  • This will be a close collaboration between product, engineering and marketing.
• How are we communicating the rationale and decision-making around the experiments to other stakeholders on the team and outside of the team?
  • Mainly through Slack, meetings, Phab, and the post itself.
• Where are we documenting the scoping process and the lessons learned?
  • There is a document that holds the initial outline that was created by engineering. Lessons learned will be reflected in the same document.