You need any write a custom site  definition for this. Feature Stapling would
be good  enough.

I don't think I can use Feature Stapling for the document library  though. Every
time a new document  library is added to a site, I have to make sure the workflow
is attached. I do not know how to achieve this. I have googled this to death
and get generic answers but not any good  example I can use.

Is there an event you can trap for that (using an Event Receiver)?

From what I have read, the only way I could add an event receiver is any time an
item is added. I'm concerned about the impact that attaching the workflow  on
every item added or changing event would have.

What if you just associate the workflow  with the appropriate content types?
That should take care of any library  that uses them.

create a custom  content type and associate workflow  with it. Use this content
type in your doc library.

Do you know of any where I can see examples of this being done? I'm supposing
this means I will replace my association page with code?

It doesn't need to be a custom  content type.

technet.microsoft.com/en-us/library/cc514190%28office.12%29.aspx

Go to the second section (the one about Site Content Types).

I am not following your post from the beginning but it is certainly doable by
associating workflow  at the content type level. This blog explains how to do it
programmatically, however it can be associated with no code but you have to
google it around.

blog.brianfarnhill.com/.../

Plus, you do no not need to change assoication page.

Can you create a custom  list, attach the SPListItem event receivers to it and
then save the list as a template? Assuming you can code the event receivers to
be dynamic (don't code them to a specific URL) then it seems like this will
work. Then, when you create new lists from that template they will already have
the correct events attached. This isn't a workflow, specifically, but
fundamentally that's really all the workflows are: Windows workflow  Foundation
in event receivers.

We created  a site  with lists that have event receivers attached to them. When we
save the site as a template and create new sites from that template the lists
all still have the event receivers attached and everything works perfectly.

This works for site templates so I wonder if it can work for individual list
templates as well...

The workflow  is already written and in production. The shareholders of the site
decided to have it "hands off" because the governance of enforcing it be added
to every page and document library  was beginning to give them quite a headache.