You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 7, 2022. It is now read-only.
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?
The text was updated successfully, but these errors were encountered:
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)?
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?
The text was updated successfully, but these errors were encountered: