Replies: 1 comment 2 replies
-
You're probably only looking at templates in terms of the animal_view service call, where a template is used to output one record. If you use any of the service calls that are prefixed with html_ (eg: html_adoptable_animals, html_adopted_animals) they use the template to construct a full page. The body section is repeated for each record that is to be output. You can make the active code editor go full screen by pressing F11 or CTRL+SHIFT+F |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Why does ASM divide the publishing templates into three physically separated sections (Head/Body/Footer) instead of just using html elements for each section?
Due to the small size of the windows when they are divided this way (and with no way to expand or full screen like in other parts of ASM) they are harder to read and see what is going on. This setup also makes it harder to cut & paste (three separate cut & pastes to get code out and then you have to be careful to put things back in right places once they are edited). Moreover, the and tags are still present in all of the example templates, so it doesn't even appear to replace the need for that in practice.
I've never seen an HTML editor physically separate these elements like this and it certainly adds an inconvenience factor; so I am just curious what problem having it this way solves?
Beta Was this translation helpful? Give feedback.
All reactions