You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reviewing what projects out there use the extra_footer_actions block in Wagtail templates – wagtail-content-import is the only one. This is in use to display the "import" actions dropdown. here’s a screenshot from the package’s initial design, way back:
I’d like to eventually deprecate extra_footer_actions in Wagtail, as it seems the same results could be achieved in a much more space-efficient way. We’re trying hard to make the footer actions smaller, so we have less of the form blocked by a sticky component.
For this specific package’s use case – it feels like those import actions are unlikely to be used so often that they need to be immediately accessible. They could be moved to the main actions dropdown, or even to the listings’ dropdowns next to "add child page" to make first-time imports faster. Or we can come up with a new design that’s more space-efficient.
The text was updated successfully, but these errors were encountered:
Reviewing what projects out there use the
extra_footer_actions
block in Wagtail templates –wagtail-content-import
is the only one. This is in use to display the "import" actions dropdown. here’s a screenshot from the package’s initial design, way back:I’d like to eventually deprecate
extra_footer_actions
in Wagtail, as it seems the same results could be achieved in a much more space-efficient way. We’re trying hard to make the footer actions smaller, so we have less of the form blocked by a sticky component.For this specific package’s use case – it feels like those import actions are unlikely to be used so often that they need to be immediately accessible. They could be moved to the main actions dropdown, or even to the listings’ dropdowns next to "add child page" to make first-time imports faster. Or we can come up with a new design that’s more space-efficient.
The text was updated successfully, but these errors were encountered: