If you don’t know ContentTypeBindings, take a short look at: http://msdn.microsoft.com/en-us/library/aa543598.aspx
“Content type binding enables you to provision a content type on a list defined in the onet.xml schema.”
So we can assign content types to newly created lists. That’s cool 
The ContentTypeBinding feature can, of coarse, contain multiple content types which are bound to multiple lists. Like this:
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
<ContentTypeBinding
ContentTypeId="0x0100yourGuid"
ListUrl="Pages" />
<ContentTypeBinding
ContentTypeId="0x0100anotherGuid"
ListUrl="Pages" />
<ContentTypeBinding
ContentTypeId="0x0100yetAnotherGuid"
ListUrl="Lists/YourList" />
</Elements>There is however, a limitation! Do not configure more then one ContentTypeBinding feature for a newly created page! You will get a save conflict Exception, when you provision a new web.
If you are curious how the feature gets referenced, take a look at this page: Understanding Onet.xml files
<Configurations>
...
<Configuration ID="0" Name="Default">
<Lists>
...
</Lists>
<Modules>
<Module Name="Default" />
</Modules>
<SiteFeatures>
...
</SiteFeatures>
<WebFeatures>
<!-- a ContentTypeBinding feature -->
<Feature ID="6BB8BC13-987F-4668-9A63-E42F1CC03C44" />
<!-- do NOT add another ContentTypeBinding feature! -->
<Feature ID="CFAF8323-0CC5-4426-A33D-5B6A0AD72F96" />
</WebFeatures>
</Configuration>
...
</Configurations>