Introduction To Umbraco

Editor's Notes

• #2: Introduce myselfAsk for a quick show of hands who is using a CMS and which ones they are using
• #5: Manual install good for local machines or if you have access to the SQL serverVery clunky with Web Platform Installer
• #7: DBs = MySQL, SQL Server and VistaDBThe newly created DB user must be the dbOwner of the database
• #8: DEMO:1. Show them the created DB2. Show them where to find web deploy in IIS 73. Setup thru IIS deploy. Show them the wizard. Make note that they have to have SQL name in correct caps and that the SQL server must be set to (local). Also set the Application Pool framework to .NET 4.0. 4. Show them the completed site
• #12: DEMO:1. Show how to access site2. Show how to log in with username created3. Give a tour of the site and what each of the areas do
• #15: Talk about difference between saving and publishingDEMO:1. Create a Document Type and it will also create a template2. Create a new content page with that document type. Only Name is editable.3. On new document type create a new tab called Content.4. Create a new property under this tab called BodyText with Richtext Editor.5. Return to Content page and show new tab with the editor.
• #16: HTML is the template languageEverything in template is wrapped in <asp:Content></asp:Content> elementTalk about inheriting templates into a master templateRecursive items (recursive="true") in master template so that they show on all pages
• #17: - DEMO: 1. Add Summary property as textbox multiple to generic properties in Document Type. 2. Add Summary as a Umbraco page field in template. 3. Go to content page to edit this new field.
• #19: DEMO:1. Create a new stylesheet called Style2. Add the following CSS line - body{background:red}3. Change the master page stylesheet in two areas4. Show a content page
• #21: DEMO:1. Show the project used to create the custom user control2. Right-click the Solution file and set the CMS solution to not build in the properties3. Hide the App_Data/TEMP folder in the project files so they don’t get added to TFS4. Show the post build events
• #22: - Talk about how this is the same as adding an XSLT macro
• #23: Create a Login page and add the Login macro to it.
• #24: The query string only works when debug mode is true in the Web.Config. Set to false when releasing to production.Can delete the DLLs and refresh the page to invoke the query stringThe query string is also good to check for bottlenecks on page load
• #27: DEMO (Users):1. Create a new media library called UKEditor2. Create a new user called ukeditor; set password, the start nodes and sections3. Change user permissions – unclick Publish and click Send To Publish3. The administrator can then approve the changes once they are happy with itDEMO (Members):1. Create a Member Type called PowerUser2. Create a new tab called Details to store member properties3. Create a new property under Details called City4. Create a new member for that type called Demo5. Create a member group called PowerUsers and add the user to that groupDEMO (Role-based protection):1. Create a login template with <asp:Login ID="Login" runat="server" />2. Allow new template on document type3. Create a new Login page with new template.4. Create a forbidden page.5. Create a private page and click Public Access. Set the appropriate pages.6. Hide the login and forbidden pages from navigation.7. Browse to private page and get re-directed back to Login page
• #28: - Talk about Colin’s upcoming Metro Toronto .NET User Group presentation on Web Deploy