Damn 500 Internal Server Error!!!
Before I respond to your comments below, some background...
I started building v2.0 of my website back in the Summer of 2011. (Hey, I'm not a whiz like all of you SitePointers!!)
A few weeks ago, I had just finished testing v2.0. It looks and runs great, and I was planning on taking just a few days to put in live data, and then go live, when I came to this realization...
Over the last year or two, I have come up with TONS of new business ideas and Content. And, technically, while my website would handle most of this new Content, my original v2.0 design really needs to be "super-sized" to handle everything.
And so here I am... Frantically trying to tweak things so I don't have to "down-size" all of the new Sections and Content I came up with, while also not having to completely re-code my website?! :eek:
Two big issues I have come across include:
Issue #1: Going from 5 Sections to maybe 40 Sections. While my code scales, there isn't enough real-estate to accommodate things.
Good news is I have re-done my "Information Architecture", and think that I have combined and whittled down those Sections to maybe 12 which seem to fit from a UI standpoint.
Issue #2: It had always been my plan to just release v2.0 with however many Sections, and each Section consisting of a "Listing of Articles" for said Section. (See screenshot above.)
With so much new Content (i.e. not just Articles), it occurred to me that I really should have a "Landing Page" for each Section.
So, if a user clicks on a Section, and after tha=ey end up on the "Landing Page", if they still wanted to just read Articles, then they could be redirected to my "Listing of <Section> Articles" page and everything would work fine as far as Articles are concerned.
However, if they wanted to listen to a podcast, watch a video, view some statistics, and so on, then they could do that from the comfort of the "Section Landing Page".
Seems simple enough, BUT, it may change things like: Directories, Apache mod_rewrites, and PHP substantially depending on what you advise me to do?!
Yes/No. (This may be Issue #3...)
I have a database designed to handle "Articles" for my website. And my current site is database-driven. However...
a.) I only have five "test" Articles, and so sometimes I lose perspective of how my site might look and work if I had say 100 or 1,000!
b.) I never got around to figuring out how to handle all of the OTHER CONTENT in my website... (Oops!!)
I guess I never planned out that far, but I just assumed my website content would consist of 85% Articles, and 15% static Reference (e.g. Laws by State, Sales Tax by State, Need-to-Know Gov't Contact #'s, Statistics, etc.)
Since I have a decent templating system for my Articles, I was thinking of just changing how my URL and mod_rewrites work somewhat, and somehow utilizing my current code and tables used for Articles for things like mentioned above.
For example, I could type up a listing of "Important IRS Contact Tele #'s", dump them into a new table similar to my Articles table, and use a modified template to display this info.
OR, at the same time, I could just create a static HTML page for now, since most of the 15% of the Content wouldn't change.
Does that answer that question??
If so, all you need to do is have one page that will display whatever data is defined for that section. If the page has articles, links and images, that's what it shows. If it has articles and links, that's what it shows. If it just has articles, that's what it shows.
How do I structure that on the back end??
Approach #1: Create a directory for each Section, and place this "Section template" you are describing in said new directory. (It could be called "index.php" or whatever.)
Approach #2: Create one MONSTER template for all Sections, with complex logic that looks at the Query String to determine which code fires and how the "Section Landing Page" is built.
Cool idea, but too complicated, too late in the game.
Approach #3: Create a "section" directory, and in it keep a uniquely named "Section template" for each Section.
Then use my mod_rewrites to determine which template fires.
RewriteRule ^finance/$ section/index_finance.php [L]
RewriteRule ^legal/$ section/index_legal.php [L]
RewriteRule ^management/$ section/index_management.php [L]
RewriteRule ^small-business/$ section/index_small-business.php [L]
This way I could have completely different "Section Templates" for each Section - which will likely be the case - but have all of the templates reside in one new directory, and not muck up my Web Root with 15-20 new directories...
Approach #4: Maybe something else??
How does that sound?