I think /dashboard/slug/ should always be read-only. It can provide a link to /dashboard/?edit=slug(visible only to users with the right permissions) that provides the edit interface.
This will also help deal with the problem that the new Markdown and HTML widgets encourage dashboard SQL queries long enough that they might run into query string length restrictions. Those widgets are mainly intended to work with saved dashboards, where the edit would take place entirely via POST requests with much less restrictive size limits.
The widget custom templates will need to get better at handling the read-only case - maybe I could refactor them to use inheritance from a base template to help support this.
I think
/dashboard/slug/
should always be read-only. It can provide a link to/dashboard/?edit=slug
(visible only to users with the right permissions) that provides the edit interface.This will also help deal with the problem that the new Markdown and HTML widgets encourage dashboard SQL queries long enough that they might run into query string length restrictions. Those widgets are mainly intended to work with saved dashboards, where the edit would take place entirely via POST requests with much less restrictive size limits.