Skip to content

Storing markdown documents #20

Description

@begedin

On the ember side, there's the editor research I'm doing.

However, I'm not completely what to integrate that into on the API side.

What object/structure do we want to have? How do we call it? A "document"? Are there any links to it?

The simplest thing I can think of is simply a document entity with properties along the lines of team, author and content, but I could see us needing something more complex extremely quickly. Stuff like revisions, editors, access rights, etc.

Any ideas/suggestions?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions