thinking strategically: Should I use exclusively folders?

[NewKidOnTheBlock]

My website really just has 16 pages (will be 17), and I don't think I'll add any (at least not many!) pages to this website (it's a very niche topic and I couldnt even think of more categories that make sense).

So what Im wondering is this:

Should I use a folder for every page (and then call every page index.shtml - Im using SSI, btw).

I'm hoping that that way people will be inclined to link to the path they see in their browser or in the source code (www website com/folder1/). And if I ever change technology and want(have?) to call my pages .html or .php, I won't have any issues because all (or at least the vast majority) of links will be pointing to the folders.

One reason, why I'm asking this is because I made the decision not to use a CMS for this site (Ive thought about it a ton), but after the semester (in 3 months) I want to still be able to switch in case I feel like I should. Or maybe if I want to switch in 5 years who knows ;). Just want to keep that option...

To be honest, I don't know a lot about CMS's....but I'm wondering if having people link at .shtml files might be a problem, as a CMS I might use later on might name pages automatically .php or .html or something (I have no idea).

What do you guys think of this idea? Do people (in a non-tech niche) really link to the file path, they see in the browser/source code?

Doesn't it matter at all, because I could keep the whole page names including the .shtml in any CMS, anyway?

If some people link to www website com/folder1 and others link to www website com/folder1/ would that be any kind of problem?

Thanks!!

[jimbeetle]

Let's do first things first. For a site with less than 20 pages I think a CMS would be overkill as there really isn't that much content to manage. Unless you want to use it as a learning experience, but then you should start the site with a CMS from the git go.

As for putting each page as an index in its own folder, sure, sounds good. You could also keep the pages at root and use an .htaccess rewrite to make the pages appear extensionless. But again, if the site is not going to expand, simpler is better.

As for the way folks link, I assume its from what appears in the browser address bar; can't think offhand why anyone would refer to the source.

The one thing you have to keep in mind:

example.com/folder1 <<refers to a page
example.com/folder1/ <<refers to a folder

You would definitely need something to add the trailing slash for any incorrect request.

[NewKidOnTheBlock]

I'm glad someone finally tells me what I want to hear! That I don't need a CMS ;). I've really been doubting my sanity, because everybody's been telling me "you better start with a CMS right away!" and it didn't make sense to me why I'd need one so bad (despite my telling them about the structure of the site).

As for putting each page as an index in its own folder, sure, sounds good. You could also keep the pages at root and use an .htaccess rewrite to make the pages appear extensionless. But again, if the site is not going to expand, simpler is better.


I assume the folder-idea I'm doing right now would be the simpler way of doing it? (I've never done an .htaccess rewrite and am not exactly sure how complicated it is) Having all files in the main folder would be pretty simple, too, if I'd only have to add a line or two of code into the .htaccess file, but I assume that's a bit more complicated than that and I should go with the folder-idea instead (if I don't plan on adding dozens or hundreds of pages)?

I mean..you never know maybe I'll add 4 or 5 pages along the way! But because of the nature of the site (it's a very niche topic) I can't see myself growing the site in categories/pages (sure can see it grow in content per page though ;)).

You would definitely need something to add the trailing slash for any incorrect request.

What do you mean by this? What can I do to add the trailing slash for any incorrect request?

thanks for the help!

[beu]

Technically, it's best to use url.com/folder/ but you might consider a redirect for marketing.

for example:
cnn.com/ireport

[NewKidOnTheBlock]

By "marketing" do you mean if I was to make a TV spot that shows the URL, because people wouldn't normally remember cnn.com/ireport/ but would probably just (want to) remember cnn.com/ireport ?

Saw a tv spot like that yesterday, which made me think about this! ;)