amych, I feel like a total ass, but did you see my question(s) above?

Back to pickles. Why the hell are "sour" and "half-sour" pickles called that when there's nothing sour in the brine? Is this one of those sneaky things like "dry" champagne and a "grande" at Charbucks?

There is a very nice one, but it's tucked inside the visitor's center, up a ramp and in a special room.

Is that where they have the galaxy painted on the ceiling and wall and they play that loud booming "Jesus" voice? Cause that completely cracked my shit up. t GoingToHell

Is that where they have the galaxy painted on the ceiling and wall and they play that loud booming "Jesus" voice?

Strictly speaking, that's not Jesus, that's just a narrator (snerk). And yes, there's the painting. And the inspiring view of temple across the way.

I actually quite like that room, it's darkish and quiet when the narrator doesn't talk, and people don't linger.

I did! Sorry, DJ

My general question is, "Is it normal to have the document divided into a bunch of folders? Would you still call the whole thing a document? What would be the reason for dividing it?"

The thing is, a lot of this will be somewhat dependent on both the business and the particular content system you're using. And by what the meaning of "is" "document" is -- a computer file (document in the MS Word sense)? something that stands in for a real-world document? or something that's presented on the website as one page? and you see how I'm already at risk of way overcomplicating things...

Anyway, it's very common to divide web content up into multiple files, for reasons ranging from update schedules to different people's responsibility to being able to reuse them in multiple contexts. For document-documents (scans of things, official forms, things to be downloaded as pdfs or docs), it's less common and possibly dicey.

So the first thing is that I probably *wouldn't* use the word "document" -- I'd use "file" if we're talking about different chunks of web content, or, you know, "Grandma's will" or "the pdf of our annual report" or whatever if that's what it is. But as to whether and how it's appropriate to split up the content, it depends.

(Also, you're welcome to ping me if that doesn't make sense, since I know you're never too happy posting specifics -- and also because "what is a document" is the kind of thing I can go on for way too long about in a most un-fun way until I start to say "will nobody think of the bitches!?" at my own self.)

Ok - but that's so not fair considering that (I think) bon bon is the only one of youse that is actually WORKING AS A LAWYER.

Only if you limit it to private practice.

Thanks! I think I have a better understanding now. I may be using the phrase in the wrong sense then. I'm talking about something that reflects the entirety of the site and is updated as changes are made or on schedule.

Someone asked for a copy of it, and wanted to know why it had to be pasted from several files into one "document"

You're not using anything wrong! -- it's just one of those terms that means a bunch of things that sometimes contradict each other. Your particular use sounds like what I'd normally call a site index, which makes me think the terminology might be specific to either your system or your site -- but that still doesn't mean it's wrong.

and also because "what is a document" is the kind of thing I can go on for way too long about in a most un-fun way until I start to say "will nobody think of the bitches!?" at my own self.

Amych is me.

Someone asked for a copy of it, and wanted to know why it had to be pasted from several files into one "document"

The biggest challenge for technical publishers, etc is in communicating with the non-techies using language that makes sense to both. I am constantly trying to figure out ways to describe folder stuctures (that comprise one "report") and their relation to xml to colleagues who are used to "reports" being in Accupress binders with indices and tabs.

Valium and Absolut gimlets help with the resulting headache.

And in this case it's a non-techie translating too.

Will email you in a sec, amych.