[A3] footerJs block

The problem to solve

It would allow adding scripts after the core utils directly within the layout template. Currently A3 boilerplate proposes development workflow with wrong JS order - modules browser JS will end up before the core utils. No matter there is a workaround (defer attribute, dom loaded event), an extra layout block in the default core base layout would simplify the task of simply adding custom browser JS.

Proposed solution

Add {% block footerJs %}{% endblock %} at the very end of template:outerLayoutBase.html, just before the closing body tag. Change the a3-boilerplate implementation to use this new block as a good example usage.

[boutell]

Have you tried putting your javascript files in modules/modulename/ui/public?

When you do that, they should become part of our javascript bundle automatically and go at the end.

I can see that we might need to provide another block that goes after our script tag for other reasons, but let’s talk about this solution first.

On Tue, Mar 2, 2021 at 4:39 AM Miro Yovchev [e-mail] wrote:

I think it’s good to have the option to inject both before and after the core utils. Keeping the extraBody block how it is might be good for BC.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/apostrophecms/apostrophe/issues/2770#issuecomment-788769791, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAH27ILRHOJMMCWXLM7PQLTBSW3TANCNFSM4YMXISAA .

–

THOMAS BOUTELL | CHIEF TECHNOLOGY OFFICER APOSTROPHECMS | apostrophecms.com | he/him/his

[abea]

In A3 there is an {% block afterAposScripts %}{% endblock %} block that is essentially the last thing in the body tag.