Discussions
Join us for complimentary one-day events around the world and step into a future fueled by AI and limitless potential. Explore new breakthroughs, sharpen your skills, and connect with experts who are shaping what’s next. Experience bold keynotes, interactive learning, and connections that span the global NetSuite community. Discover what's next at SuiteConnect Tour 2026.
We’re excited to announce that the 2025 Community Recap is now available! This special recap highlights the amazing contributions and achievements of our members over the year and celebrates the collective success of our community.
Check your personalized recap to see the impact you made in 2025 and how your efforts helped shape our community’s growth and success.
View Your 2025 Community Recap
Thank you to everyone for your passion, collaboration, and support. Here’s to building an even stronger community together in the year ahead!
order of <head> add-ons
Is it just me? Or does anyone else think it's ass-backwards to have a template's "add to <head>" block come first, before the theme's "add to <head>" block when the page is rendered?
I mean... really?
If I want to override a site-wide CSS rule in a particular class of pages, I don't see a way to do it, except by putting the <link> or <style> element in the <body>, which violates the HTML spec.
If I want to include, say, the jQuery lib and use it in a particular way on a particular class of pages, I have to include jQuery in the template. I can put <script> elements in the <body>, I suppose, and in that way keep the jQuery include in the theme's <head>. But that's just kind of messy.