Skip to content

API documentation needs #1

Description

@volkerblum

In the HybriD3 documentation, we should document the API in three separate points:

  1. Point out that HybriD3 is historically optimized for in-browser usage and therefore no completely high-powered API but please work with us for specific needs

  2. Working hands-on examples for different uses of the API -> Xiaochen example of two properties in same query, what else?

  3. Point to MatD3 software documentation for origin of API and more systematic documentation in terms of writeup and code.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions