Run codegen module BigFont.Maps /IncludeInSolution:true, because this creates a new BigFont.Maps module and adds the project to the Orchard.sln files.
Reload the solution file in Visual Studio, because we need to accept the recent changes.
Add the existing bigfont.maps project to the Visual Studio solution explorer, because it wasn't listed there yet.
Update the module.txt file with relevant descriptions, category, and author, because this will show up in the Orchard Gallery, for instance, if we share the module.
Add a Maps.cs class to the Models folder, because this class will contain the data for the part. It is the Model of the MVC for this content-part.
Build the maps project in preparation for adding a migration class.
Run codegen datamigration Maps, because this newly created class will tell Orchard how to update the database when we later enable the BigFont.Maps module.
Add the BigFont.Maps namespace to the two newly created classes, because we want then to be able to see eachother. Then build the BigFont.Maps project.
Add a MapsHandler.cs file because it will define the behavior of the content-part, such as manipulating data or handling events before rendering the part.
Add a MapDriver.cs because this will associate specific Shapes with specific Contexts in which this part can render.
Add the editor and the display views as chtml files to the Views/Parts and the Views/EditorTemplates/Parts folders.
Add a placement.info file because this tells Orchard where to render this content part on the page.
Build the BigFont.Maps project in preparation for building Orchard.Web and testing the new content-part.