The next area of the community I'm updating is the profile pages. Since the page elements are all changing, everyone who did custom styling may want to look over your code to be sure it's compatible with everything.

Most of the old page code used inline styling and TABLEs for layout. The new code uses DIVs and classes, including separate ones for light and dark themes. The Blogs section is probably the best to test in the partially-transitioned form, since it uses several examples of what I mentioned. Most changes over the next few days will take on those same styles and classes.

The H1 tags all use element-level styling, so you can override them all without extra classes.

The top-level DIV tags always use the "menu_section" class, which scales parent content to fit anywhere from 240px to 768px. There are a variety of child classes, like "button_div" (for profile page buttons) and "zebra" for zebra-striped rows, which look similar to iOS or Android tables. These DIVs can also take on extra classes on themselves and one sub-elements, like "left", "right", etc.

When I'm finished redesigning the profile pages, I'll write up a more detailed blog, but this should be enough to get you started. Note that the final form will use important (!) styles for header and footer elements to keep them always accessible.