Skip to content

separate docs into "how it's used" and "how it's built" #37

@jowens

Description

@jowens
  • if it's not too much work, I'd suggest separating the documentation on how to use from how it's built. A potential gridwise user should be able to find what they need w/o considering the builtins strategy or the possibility of future evolution of the Buffer class..

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions