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

How to approach a playbook API #128

@pjackson28

Description

@pjackson28

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionFurther information is requested

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions