Amy (![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
brightknightie) wrote2011-06-26 04:43 pm
brightknightie) wrote2011-06-26 04:43 pm
Entry tags:
Remodeling "Bright Knight" Fansite
With the exception of the recommendations project, the top level of my "Bright Knight" FK fansite has at long last achieved the light of the CSS present, leaving behind the HTML tables-based dark ages. Take a gander and let me know what you think? It appears correctly on my PC in the latest Firefox and IE. I don't know how it looks on a Mac or in other or older browsers. I'm fairly content with the various content index pages, but the homepage itself unfortunately seems simultaneously busy and hollow. Constructive criticism is welcome ("constructive" ideally means "with suggestions for improvement" ~g~).
You may recall that I mentioned, a few months back, creating a template for archiving new stories going forward. These index pages were step two. It will take a fair duration to rework all the site content: every FAQ, timeline, essay, list and tale. The content goes back to '96; the site went online, hand-coded, in '99; then came FrontPage, now Dreamweaver...
I expect that the recommendations project — standing out like the proverbial sore thumb — will be the most challenging to reconfigure. I built it on framesets back in the day; I must find a structural alternative that maintains functionality. I do not yet even know the proper term for the way that GoogleNews keeps its sidebar menu static on the page as you scroll, but I believe that's what I need for the recommendations sans framesets. (Alternatively, Spry tabbed panels? I don't know.)
You may recall that I mentioned, a few months back, creating a template for archiving new stories going forward. These index pages were step two. It will take a fair duration to rework all the site content: every FAQ, timeline, essay, list and tale. The content goes back to '96; the site went online, hand-coded, in '99; then came FrontPage, now Dreamweaver...
I expect that the recommendations project — standing out like the proverbial sore thumb — will be the most challenging to reconfigure. I built it on framesets back in the day; I must find a structural alternative that maintains functionality. I do not yet even know the proper term for the way that GoogleNews keeps its sidebar menu static on the page as you scroll, but I believe that's what I need for the recommendations sans framesets. (Alternatively, Spry tabbed panels? I don't know.)