36 lines
1.1 KiB
Markdown
36 lines
1.1 KiB
Markdown
|
|
|
|
# TODOs
|
|
|
|
|
|
## General
|
|
- [ ] we need the ability to have multiple template directories.
|
|
- [ ] develop a django-css independent theme for the admin.
|
|
- [ ] better 404 handling
|
|
- [ ] better 500 handling
|
|
|
|
|
|
edit functionality:
|
|
- edit-list (which fields can we edit)
|
|
-> unlike in django, we have no access to the model completely, however, we also do not have to care.
|
|
- widgets (how fields are rendered in the edit form)
|
|
-> how would i create widgets? programmatically? in templates?
|
|
-> maybe even both approaches available?
|
|
-> need a list of MVP widgets, and a way to extend them.
|
|
-> widgets should be groupable.
|
|
-> taking a look at djangos solution!
|
|
-> are there any smart json data => form things out there?
|
|
- validation.
|
|
-> client side as well? fomantic has it.
|
|
-> existing solutions?
|
|
-> transparent way to display error messages at the appropriate field (probably adding results into responses)
|
|
-> handling: "required"
|
|
-> handling: "invalid"
|
|
-> example implementation: invalid(max-length)
|
|
|
|
auth:
|
|
- user model.
|
|
- auth middleware.
|
|
- message the user.
|
|
-> messaging system
|