Unique cache page write-up

[+Rathergohiking]

I enjoy creating a unique cache page write-up for every cache I place. I believe it adds a bit of fun to the overall geocaching experience. Who else does that?

[+briansnat]

Only if there is a reason for it. I may give background information about the area if there is something about it that I want seachers to know. If there is nothing special about the cache other than an nice walk or good view I'll mention that fact, but that is about it.

[+DavidMac]

I used to think that it was expected... but these days there are increasing numbers of copy-and-paste cache descriptions, or sometimes no description at all.

 

It doesn't bother me, though, because I use it as a quality control filter of sorts. If you haven't put at least some thought into your cache description I'll assume that you put just as little effort into the hide itself. If you've done something interesting or given me a "teaser" on the cache page, I just may be inclined to seek it out. For example now you have me wondering just what kind of hairstyle a cache container could have.

[+StarBrand]

I try to write a unique description for each and every cache that I place. Sometimes that means just a few sentences - sometimes a few paragraphs.

[+Opalblade]

Some of mine have something extra on the cache description page and I always have a themed background. My piggy bank cache has info on the origins of the expression "Bringing Home the Bacon". My gingerbread themed cache has the story of the gingerbread man. Etc etc.

[hoosier guy]

I enjoy it when the CO shares some information about why the cache site is special to them or gives some interesting information on the natural or historical significance of the area.

[+The Cache Checkers]

I have been on the hunt for two hides that have interesting cache pages. One I found, one I didn't but plan on going back when it's actually spring outside.

 

GC12BWX

 

and

 

GC1NVXV

[+Taoiseach]

See GC209Y8

 

All of mine are unique! I refuse to even use cut & paste logs (which could be why I'm over 200 logs behind on my logging )

[+WeightMan]

Each of my caches is unique and therefore requires an unique cache page. If they were generic LPCs, then I wouldn't hide them.

[+Vater_Araignee]

I used to think that it was expected... but these days there are increasing numbers of copy-and-paste cache descriptions, or sometimes no description at all.

 

It doesn't bother me, though, because I use it as a quality control filter of sorts. If you haven't put at least some thought into your cache description I'll assume that you put just as little effort into the hide itself. If you've done something interesting or given me a "teaser" on the cache page, I just may be inclined to seek it out. For example now you have me wondering just what kind of hairstyle a cache container could have.

so somebody that exhibits compression skills by making the title the cache description, the hint and a playing with homophones that when spoken express a common phrase that exemplifies the feeling of retrieval from enough people to be pertinent, would get filtered out for putting little thought into it?

 

Weir Dammed micro 2.5/3

I have already given you everything you need to know.

 

Happy hunting,

Vater Araignee

 

P.S. Please put cache in it's correct position when replacing.

 

My other active cache still sticks to my lack of description MO, because I haven't found the right words to keep me from sounding like a total softy concerning the reason for the hide, but if you find it you start to understand its name and why it was placed.

 

Some times the best way to get people to understand is to give a quick flourish and shut up. Wish I would heed my own statement more often.

 

~~~edit~~~

dropped Ts

Edited March 29, 2010 by Vater_Araignee

[Andronicus]

Each of my caches is unique and therefore requires an unique cache page. If they were generic LPCs, then I wouldn't hide them.

I am with you on that. Some hides don't need big writeups, but they are still unique, and deserve a unique page. If they weren't unique, I wouldn't hide them.

[+GeoGeeBee]

I enjoy creating a unique cache page write-up for every cache I place. I believe it adds a bit of fun to the overall geocaching experience. Who else does that?

 

Around here, nearly everybody.

[+bittsen]

I think all of my caches have unique pages. They are all different with only two that are identical hides.

 

I just wish people who hide micro spew would be honest about it. I'd love to see pages that say "Another lame film can in an equally lame hiding spot". Or, "there wasn't a cache here and now there is".

 

That would take care of quite a few.

[+simpjkee]

Of course I write a unique cache page for each of my caches. That's the point right?

[acetech09]

I write unique cache pages, but all following a same general format regarding font size and description length.

See these three of my caches to see how I do it:

 

Cache #1

Cache #2

Cache #3

 

I AM a web programmer, so my cache pages are pretty advanced, but you can get the point.

[+FancoverFive]

I write unique cache pages, but all following a same general format regarding font size and description length.

See these three of my caches to see how I do it:

 

Cache #1

Cache #2

Cache #3

 

I AM a web programmer, so my cache pages are pretty advanced, but you can get the point.

 

You don't need to vary font size/type/colour so often to make it look interesting.

 

Have a look at my cache here. All I used was a blockquote, a few horizontal rules, and spaced-out paragraphs. This results in a clean, easy-to-read page. I'm not saying that mine is the best example of a well-formatted page, but it does the job.

[+Jeep_Dog]

Each of my caches is unique and has a unique description.

 

I don't appreciate cut-n-paste caches, so I don't place them, so no issue in me placing any that would facilitate cut-n-paste descriptions.

[+BBWolf+3Pigs]

Each of my caches have totally unique descriptions with two sets of exceptions:

 

1) Series of "urban" nanos in Newport, RI. Each has the same start and ending paragraphs (the generic stuff like parking). In between is a description of the area, history, etc.

2) A series of "park & grabs" in a state park. They are all unique hides (no guardrails), and to keep things interesting I use the same description for each (so I don;t give anything away). I also specify a size of "?" to not give anything away (they range from micro to small). Each hide is different, with unique hides or containers making them anything but "routine" pg's.

[+Ike 13]

Every hide is unique, every page is unique. When I started hiding caches I wanted somthing more than a description of the container, swag, location, etc that was so common. I wanted to be different. I teach math and all (but one) of my cahces generally describes some mathematical topic/concept. Pretty much every one has something to do with the hide style or location.

[+DavidMac]

so somebody that exhibits compression skills by making the title the cache description, the hint and a playing with homophones that when spoken express a common phrase that exemplifies the feeling of retrieval from enough people to be pertinent, would get filtered out for putting little thought into it?

 

Weir Dammed micro 2.5/3

 

 

In that particular case, this is the first thing I noticed on the cache page, and it piqued my interest:

 

...that, and the high number of DNFs make me think there's more to this cache than meets the eye.

[+EscapeFromFlatland]

My caching, to date, has been in small numbers. My largest number of caches in 1 day was 10.

With small numbers, I see no reason not to write a few sentences when logging online.

Paper log: Unless the logbook is fairly big, I just write my username and date. If its fairly big, then I'll write something additional.

[djhobby]

I always TRY to write something, either informative or witty if I can come up with something. But something I wish everyone would do, is in the short description on the cache page, put all of the pertinent information about the cache, size, type, etc... and THEN in the long description put your neat stories. I like the stories, but sometimes it's a pain to wade through 5 paragraphs looking for the type of container hidden. Usually when a cache is published I'll read the stories immediately, and I appreciate a good yarn, and then when I'm out hunting the thing and I'm having a little trouble finding it, I might remember that the hider put some detailed information about the cache in there somewhere, if only I could find it. I could see Groundspeak and the gizmo manufacturers using that short description field for GPX export someday.

[Clan Riffster]

I am a story teller at heart. I love nothing more than spinning an entertaining yarn.

My cache pages often reflect this.

[+TheWeatherWarrior]

In creating a cache, my page is always full of unique things. Not always so deep, but always something for the cacher that expects more (because I expect more myself).

 

My logs are also unique, as much as I can make them. There are always unique factors, whether it be where I parked, the time of day, the weather, pros and cons of each hunt, and more....always something to add.

 

When I started it was expect to be creative. There was no such thing as TNLN and TYFTC, etc. That was almost an insult to not give more details. But that's what caching was like back in 2002 & 2003.

[+swizzle]

I try to add a little history to my caches. Here's one of my latest. Swiz

 

Fultonville Crossroads Revisited

Edited April 1, 2010 by swizzle

[+The VanDucks]

I'm all in favor of unique cache description pages; that's what makes me want to look for a cache! I especially enjoy funny names for caches, especially when you find the cache and then say "oh, so that's what the name means!"

 

Just a plea, though, for conciseness. An explanation or a bit of background are fine in your cache description, but edit for brevity! Too many cache pages run on and on, until most cachers will probably stop reading. (Even though you may feel that your short story is extremely clever, I will probably not enjoy reading it as much as you do.) If the description is some multi-paragraph history text you cut and pasted out of Widipedia, delete the unnecessary parts.

 

Think of your cache description as an advertisement: You have a "product", your cache, to "sell" to a "consumer", the geocacher, who has limited time and many other caches to choose from. What can you put on your description page that makes me want to rush right out and look for YOUR cache?

[+Taoiseach]

Just a plea, though, for conciseness. An explanation or a bit of background are fine in your cache description, but edit for brevity! Too many cache pages run on and on, until most cachers will probably stop reading. (Even though you may feel that your short story is extremely clever, I will probably not enjoy reading it as much as you do.) If the description is some multi-paragraph history text you cut and pasted out of Widipedia, delete the unnecessary parts.

 

For the record, I wrote my 5000 word cache page. The similarity to the Wikipedia entries is because I copy and pasted into Wikipedia, as my pieces were often better than the Wikipedia article was!

[+swizzle]

I'm all in favor of unique cache description pages; that's what makes me want to look for a cache! I especially enjoy funny names for caches, especially when you find the cache and then say "oh, so that's what the name means!"

 

Just a plea, though, for conciseness. An explanation or a bit of background are fine in your cache description, but edit for brevity! Too many cache pages run on and on, until most cachers will probably stop reading. (Even though you may feel that your short story is extremely clever, I will probably not enjoy reading it as much as you do.) If the description is some multi-paragraph history text you cut and pasted out of Widipedia, delete the unnecessary parts.

 

Think of your cache description as an advertisement: You have a "product", your cache, to "sell" to a "consumer", the geocacher, who has limited time and many other caches to choose from. What can you put on your description page that makes me want to rush right out and look for YOUR cache?

 

When I write out an extended description its not meant for the numbers folks. There will always be people out there that are interested in what me and others write as far as extended, historical text. If you're just a numbers freek then get the coords, check the clue, maybe read a log or two and go. If you avoid my cache because the discription is too long then that's your choice and gives me an extra day before I need to add a new log. Just my opinion of course. Swiz

[GOF and Bacall]

I'm all in favor of unique cache description pages; that's what makes me want to look for a cache! I especially enjoy funny names for caches, especially when you find the cache and then say "oh, so that's what the name means!"

 

Just a plea, though, for conciseness. An explanation or a bit of background are fine in your cache description, but edit for brevity! Too many cache pages run on and on, until most cachers will probably stop reading. (Even though you may feel that your short story is extremely clever, I will probably not enjoy reading it as much as you do.) If the description is some multi-paragraph history text you cut and pasted out of Widipedia, delete the unnecessary parts.

 

Think of your cache description as an advertisement: You have a "product", your cache, to "sell" to a "consumer", the geocacher, who has limited time and many other caches to choose from. What can you put on your description page that makes me want to rush right out and look for YOUR cache?

 

When I write out an extended description its not meant for the numbers folks. There will always be people out there that are interested in what me and others write as far as extended, historical text. If you're just a numbers freek then get the coords, check the clue, maybe read a log or two and go. If you avoid my cache because the discription is too long then that's your choice and gives me an extra day before I need to add a new log. Just my opinion of course. Swiz

 

I don't hide my caches for mass appeal and I don't write the cache pages that way either. I use as many or as few words as it takes. Sometimes they are longer than other times. Odd colors (colours for those of you who prefer it that way) and fonts are not what makes a page interesting to me. I want to know what you have to say and don't really care what color you say it in.