Skip to content
This repository has been archived by the owner on Apr 22, 2023. It is now read-only.

Create data contract for how API documentation will be consumed #158

Closed
keywordnew opened this issue Mar 28, 2019 · 2 comments
Closed

Create data contract for how API documentation will be consumed #158

keywordnew opened this issue Mar 28, 2019 · 2 comments
Labels
wr-agenda Agenda items for the website redesign group

Comments

@keywordnew
Copy link
Contributor

keywordnew commented Mar 28, 2019

We need a spike to find answers on:

  • how we want to tackle API docs
  • how to consume localized API docs.

This issue is a stake in the ground to kick things off. We may need a dedicated meeting to get this going. It could even need to be recurring until the spike is complete.

Questions to resolve now:

  • Should this meeting have its own time found using a Doodle or can we have it start at the end of an existing Node.js meeting?
  • What should be on the agenda?

Within the scope of this are:

@amiller-gh @LaRuaNa @zeke @sagirk @inidaname @ahmadawais @MaedahBatool @obensource

@inidaname
Copy link
Contributor

My opinion

  • Should this meeting have it own time: Yes it will give it the much need attention and speed to answer the questions raised
  • What should be the agenda: I feel kicking off the first meeting will create a road map for this plus the agenda could be prioritise around the scope mentioned.

Within the scope of this are:
#76 Consuming localized docs from nodejs-i18n module
#4 Create an i18n spin out meeting to talk shop
#169 Navigation / Section Proposal

@amiller-gh
Copy link
Member

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
wr-agenda Agenda items for the website redesign group
Projects
None yet
Development

No branches or pull requests

3 participants