Skip to content

rules frontend #57

Description

@flrgh

Create a new frontend to replace /rules.html. I don't care if the route is /rules.html or something else--that's easy to change if done right.

Ideally there's a list view:

/frontend/rules

...and a single item view:

/frontend/rules/{id} or /frontend/rules#{id} if you want to just do all the routing client-side

Having a prettier, responsive UI that is uber mobile-friendly is the primary goal. On top of this any additional bells and whistles would be gravy. Here are some ideas:

  • sort & filter capabilities in the list view
  • buttons and forms for common CRUD operations:
    • delete - remove a rule
    • update - add/edit the comment
    • update - extend a rule's TTL for another hour/day/week/month
    • update - generic form that allows making edits to all fields
    • update - edit a rule as raw JSON for easy copy/paste
    • create - same as the generic updates: a form option and a raw JSON option

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions