When specifying "Additional Head HTML" on the Site Settings and Page Settings, the page content renders prior to the site content.
Global abstracted code/styles should be able to be:
1. Inherited and utilized by page-specified scripts
2. Overridden by page-level directives
Matt,
We have forwarded your question to the dev. We will return to you when we have a reply.
...................................................
Sincerely,
Alan R.
Nicepage Support Team
Please subscribe to our YouTube channel: http://youtube.com/nicepage?sub_confirmation=1
Follow us on Facebook: http://facebook.com/nicepageapp
To clarify my question, is there a Design decision as to why the page head html renders before the site head html?
As a developer, I'm trying to understand how to leverage these as intended.
To clarify my question, is there a Design decision as to why the page head html renders before the site head html? As a developer, I'm trying to understand how to leverage these as intended.Matt,
Unfortunately, we cannot tell.
...................................................
Sincerely,
Alan R.
Nicepage Support Team
Please subscribe to our YouTube channel: http://youtube.com/nicepage?sub_confirmation=1
Follow us on Facebook: http://facebook.com/nicepageapp
I am also using HTML elements, but the point of the HTML Head element is to put global and specialized code into the head tags.
Is there a reason they are rendering in reverse order?
I am also using HTML elements, but the point of the HTML Head element is to put global and specialized code into the head tags. Is there a reason they are rendering in reverse order?Matt,
Try inserting this code in the HTML Element.
...................................................
Sincerely,
Alan R.
Nicepage Support Team
Please subscribe to our YouTube channel: http://youtube.com/nicepage?sub_confirmation=1
Follow us on Facebook: http://facebook.com/nicepageapp
