I uploaded the new Bay Community site yesterday and I think I got most of the bugs out of it. Here’s some background on it:

1. We just picked up Fellowship One. I needed to design our site to work with that. There’s several ways you can integrate. I chose using <iframe> tags. Otherwise, every time you’d click a Fellowship One piece, it’d open a pop-up window… which would probably cause epilepsy or something like that. Another option would be to show and hide <div> layers, but the iframes were a simpler solution and it still worked with my layout. You can see the Fellowship One integration on the Ministries, Fusion and Contact pages.
2. There isn’t many, if any, <table> tags on the site. I used <div> tags for layout pretty much exclusively. The reason for this is I’ve found them to be more agreeable with mobile browsers and I have more specific control with CSS (Cascading Style Sheets).
3. Streamlined and Cohesive. We took away each ministries custom designed page in favor of every page looking the same. The purpose for this was that anyone coming to iconyouth.com or findafusion.com would know that they are on a Bay Community site. It’s a more cohesive branding of our church’s web presence.
4. The whole site, not including flash files, is made up of only 25 images. The rest is CSS.
5. In the previous site, we used Wimpy Player as a podcast player. It was a Flash MP3 Player that was populated by our podcast xml file. For some reason, Wimpy Player doesn’t want to work anymore. I figured out how to create a replacement in Flash. You can see this by going to our Media page and clicking “Listen Now.”
6. Another thing I figured out was the “Quick Links” at the top. It’s a jQuery slide toggle.