Originally Posted by dresden_phoenix
And what is up with...
I said in my OP...
am not including your include of includes..lol
Why is that so funny?
I always use PHP and "includes" for things like my page layout, header, footer, and so on.
You've lost me.
you are taking me too literally. I was tryingto make an example between the oft mistaken talk of "content" ( the EXACT info) and "content type" ( the General Gist of the info's CLASSIFICATION ) .
By definition, a "hard-coded" and "static" HTML would not have any associations with XML, database or "Content-Type" classifications.
Regardless, the answer is, "No, I am not including type-o's, nor am I changing any "classifications" because there wouldn't be any.
(If I could easily "classify" things, then I would stick them in my database and use my existing templates, and I wouldn't have created this thread. That is the point ---> How to best handle these "odd" pages?!)
So I was implying this, but could have been clearer...
If you have a page whose content type is so well defined it doesn't need to be generated from a DB... I MAY suggest, as long as you remember how you coded the HTML, that you could even use the PHP to bring in CSS updates (that way the look and feel of your SITE.. ultimately we are talking sites.. remains the same even if you make a site wide change ).
Everything in my website is a .php file. And for these odd-ball pages I am talking about, they technically are not "hard-coded HTML", but rather a PHP file with - here is that funny term you like - a PHP Include to bring in the Header, Footer, and possibly other things. That way all pages on my site look like they came from some fancy CMS system, but with less overhead. The main "body" could also be an Include, or it could be in the main PHP file itself.
Regardless or Includes or not, the WEB-PAGE is "static" - in this context - because it is not being "dynamically" generated from code or query. (That is how I have *always* heard people use the terms "static" versus "dynamic" web-pages...)
My PHP Includes would prevent that from happening.
The evil is if you find yourself coding a BUNCH of static HTML pages, because it probably means you are repeating yourself or missing a pattern
that could be automated. Which is all that I was trying to say.
I just feel out-of-sorts working with standalone webpages. And, based on another couple of threads I have going, others make it sound like it is equally "evil" to create directories to represent "Sections". (see Question about Directories & Indexes.)
While all of my Member Profile features (e.g. Create an Account, Log-In, Send PM, Add a Friend) work awesome, I can see that I neglected really thinking about how to handle all of the Content that I now have...
My website is all done, and now that I look more deeply at all of my Content - including a lot of new and disparate Content - I feel like I'm in a haze when it comes to finding a home for everything?!
Do I suck it up, and stick everything in my database?
Do I call everything an "Article", and maybe add more fields to the table to distinguish between traditional articles like "Postage Metes Can Save You Money" and something that could be considered a pseudo-article like "How to Request S-Corp Status" or "Important Contact Info for Small-Businesses"?
Do I risk having code-redundancy by keeping "Articles" as "Articles" and "Other Content" as "Other Content"?
Do I hard-code certain pages that are simple and won't likely change, like "Top 20 Venture Capitalists Firms"?
Do I create a new directory called "other_content" to hold all of these standalone, hard-coded pages we are discussing?
And many more questions...
That is a new one to me...
I am coining the phase content-type ( tho I think i may need a new phrase)...
the reason being many client FREAK when asked to provide content before I start work.. not understanding that I dont actually need a proofed manuscript of their site's text .. just a guide to their specific intent. something like:
<mission statement, multiple Ps>
<single p intro>
<rand# *products : name, price, multiple or single p description, availability, link to catalog>
<3 * articles : title ,singe or multiple p>