Skip to content
This repository was archived by the owner on Apr 23, 2019. It is now read-only.
This repository was archived by the owner on Apr 23, 2019. It is now read-only.

Change nav and request structure a bit #2

@jayrbolton

Description

@jayrbolton

Our API will soon be very large. I propose we restructure nav and options ajax

  • at top level, list each resource
  • 2nd level: list available methods as headers, and below each header list the available sub-paths for each method (including the root)
  • 2nd level is collapsed by default. They both get fully expanded when you click a resource. When you click a resource, the ajax request for that resource is made to load all its methods. The first api page for that resource could be immediately shown (usually get /)

example:

  • nonprofits
    • get
    • /
    • /profile
    • /metrics
    • update
    • /
    • /verification
  • supporters
    • get
    • /
    • update
    • /

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