advice on posting a report

[kvb]

I'm working on posting a report for a build.

I've got a write up with a bit of a story/ explanation (2 pages), my sources, the effects features. This is plenty big.
+ plus +
Schematics
Build pics
sound clips

This all adds up to a huge post

If I post something I wrote I would hope people actually read it. Should I include the story part?

no matter what I do It's going to be big and a bit hard to read.

So, I could post bit and pieces, like teasers here and there (in one thread - just not all at the same time).
Or I could attach links to my gallery - But this makes more work for viewers and I want comments/ feedback to stay in one thread.

Advice? Thoughts?
Thanks

[oskar]

Big isn't really a problem as long as there is a schemo there to fast forward to for the restless young ones. I really would like to here the whole story myself.     

[frequencycentral]

Yup, throw as much as you have into one thread. Add to it as more 'findings' come up. There is no such thing as too much information. People will filter what they don't need.

[stm]

Sounds like a PDF document containing everything could be a good alternative.  Remember that you can attach any type of file to a PDF document, including audio samples.