Defining Features in onet.xml sharepoint

To define which features should be used with your Site definition you need to specify site-scoped and web-scoped features separately. In the below example we have added site-scoped features (the basic Web Part feature and three-state workflow that comes with SharePoint) that enables basic functionalities and in the web-scoped section, first reference is to a custom project list feature containing the list definition. and next two features are SharePoint standard elements that contain several list templates, such as custom list or calendar and the mobility redirect feature.
The configuration is
<Configuration ID=”0″ Name=”Production” CustomMasterUrl=”_catalogs/masterpage/custom.master” MasterUrl=”_catalogs/custom.master”>
<Lists>
<List FeatureId ….
</List>
</Lists>
<Modules>
<Module Name=”Default” />
<Module Name=”Reports” />
</Modules>
<SiteFeatures>
<!– BasicWebParts Feature –>
<Feature ID=”023BSES71-1U5D-4B2H-R340-BE5123EBDA57″ />
<!– Three-state Workflow Feature –>
<Feature ID=”FGE5D250-621E-4743-95SA-87B472322DC7″ />
</SiteFeatures>
<WebFeatures>
<!– Custom ProjectList Feature –>
<Feature ID=”7346F624-0SE1-4H6D-H2A2-80HS744FD8BC” />
<!– TeamCollab Feature –>
<Feature ID=”00BFEA71-4EA5-48D4-A4AD-7SD5C011ABE5″ />
<!– MobilityRedirect –>
<Feature ID=”F41CC622-37E5-4943-B6A8-74UJDB3FD8A4″ />
</WebFeatures>
</Configuration>