[PAGES-397] UI to Refresh page editor Created: 17/Dec/15 Updated: 13/Jan/23 Resolved: 13/Jan/23 |
|
| Status: | Closed |
| Project: | Magnolia pages module |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major |
| Reporter: | Christopher Zimmermann | Assignee: | Adrian Brooks |
| Resolution: | Done | Votes: | 0 |
| Labels: | quickwin | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: | |||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Date of First Response: | |||||||||
| Epic Link: | AuthorX improvements | ||||||||
| Sprint: | AuthX 25, AuthX 26 | ||||||||
| Story Points: | 3 | ||||||||
| Team: | |||||||||
| Work Started: | |||||||||
| Description |
|
A common task for developers and authors is to refresh the page editor (and the page preview) to reflect the current configuration, content, or resources. Typical developer workflow is to modify templates, and then to refresh the page editor to see how their changes reflect the page. They might perform this operation 50 times in an hour. The current workarounds are
All of these workarounds are less efficient than a simple refresh would be because they involve an additional action on the server (ie rendering/refreshing the tree again.) Perhaps this could simply be implemented as an action in the action bar. Or maybe it makes sense to use a different GUI element. Extra credit:
|
| Comments |
| Comment by Christopher Zimmermann [ 17/Dec/15 ] |
|
tomwespi Thanks for the motivation for this ticket. |
| Comment by Christopher Zimmermann [ 19/Dec/22 ] |
|
Note: this ticket is specifically about the rendered page in the Page Editor. Update: This is only relevant for Freemarker development. When doing a headless "Visual SPA Editor" project then the developer will typically be running a "dev server" for the frontend which will do this automatic refreshing of the page. Note: For freemarker development, it is currenlty possible to use a frontend CLI tool with a "watcher" to trigger a URL to update.. We could consider just documenting how to set this up. Here is one such tool - but maybe we would want to use something else. Would be good to do some small research: https://browsersync.io/ |