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
Often the content team needs to place links on reporting examples and in Record articles. It would be nice to have the internal and external button features available on those two page templates.
Use Case
Doing this would make the links stand out more.
Completion Criteria
Add the internal button and external buttons to these templates in Wagtail:
bmathesonFEC
changed the title
Wagtail wish list: Add internal and external buttons to Record and reporting example templates
Wagtail wish list: Add internal and external link buttons to Record and reporting example templates
Oct 3, 2019
@johnnyporkchops is including this work in his ticket on the example template #3149 . Leaving ticket open for Record page update.
johnnyporkchops
changed the title
Wagtail wish list: Add internal and external link buttons to Record and reporting example templates
Wagtail wish list: Add internal and external link buttons to Record and Example page templates
Nov 7, 2019
Summary
Often the content team needs to place links on reporting examples and in Record articles. It would be nice to have the internal and external button features available on those two page templates.
Use Case
Doing this would make the links stand out more.
Completion Criteria
Add the internal button and external buttons to these templates in Wagtail:
Here's a screenshot from a different Wagtail template (Resource page) that has these options:
![image](https://user-images.githubusercontent.com/24437369/64344321-39adbf00-cfbc-11e9-9110-36a62b331583.png)
When opened in Wagtail, here's what they look like:
![image](https://user-images.githubusercontent.com/24437369/64344579-b93b8e00-cfbc-11e9-928f-0f9546aa6703.png)
Here's what they look like when rendered (both buttons look the same):
![image](https://user-images.githubusercontent.com/24437369/64344419-64981300-cfbc-11e9-880c-f915aac5f3d7.png)
The text was updated successfully, but these errors were encountered: