I need to add some custom CSS and jQuery that we're going to use within our content sections using the HTML editor module for multiple portals - it's a real simple expand/collapse list.

I added the script and stylesheet files to the corresponding Resources/Shared/ directories, then added script and style tags to the Default.aspx page to reference these files.

It seems this isn't the best solution, in the event that we update our DNN version and our Default.aspx page is overwritten. Is there a better approach? I can't rely on our content editors to include <style /> and <script /> tags at the beginning of each content section - some just use the WYSIWYG editor and never edit the HTML. <br /> <br /> Thanks

Typically, you would add custom CSS via the portal.css file. It is the Stylesheet can can also be edited from the Site Settings page.

If it is more appropriate, you can add the styles to the skin.css file appropriate for your skin.

The easiest way to load additional css files is via the 40Fingers Style Helper Skin Object, or a module like WillStrohl.inject. You can find both by googling or using the new More Extensions section of the Extensions page under the Host menu.

You can add scripts and load jquery files this way, too. You can even add the scripts and links for jquery files into skin files.

All of these ways are superior to editing default.aspx. IMHO, that should NEVER be done, or done very carefully and only in rare circumstances. Instead, use the various extension points that DotNetNuke provides, and that are guaranteed to survive updates.

One interesting example of this is one of the custom container modules provided with the Dark Knight skin. It's the container that includes the jquery to load and create the image rotator that's used on the Getting Started page. I'm not sure I would ever recommend doing something that way, but is does show the flexibility of the framework.