Skip to content
This repository has been archived by the owner on Nov 7, 2022. It is now read-only.

How to approach a playbook API #128

Open
pjackson28 opened this issue Apr 30, 2018 · 1 comment
Open

How to approach a playbook API #128

pjackson28 opened this issue Apr 30, 2018 · 1 comment
Labels
question Further information is requested

Comments

@pjackson28
Copy link
Collaborator

With the dataset approach under development (generating views from a JSON dataset using Kramdown and Jekyll/Liquid), the next logical step could be providing an actual API for the playbook.

How should such an API be approached and where should it be hosted? Can an API be provided through GitHub for drafts of the playbook? How can the API be approached to make it as portable as possible (i.e., easily ported to other platforms such as AEM and Drupal)?

What API technologies should be used (e.g., REST, GraphQL)? What methods/requests should be supported through the API?

@pjackson28
Copy link
Collaborator Author

Also, in the future should the playbook (including alternate views) be generated using data retrieved from the API or continue to be generated using the dataset approach (so working from the locally hosted dataset rather than getting all data through the API)?

@pjackson28 pjackson28 added the question Further information is requested label May 16, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant