The Dot Net Nuke(DNN) is ideal for creating, deploying and managing interactive websites of all kinds.
- 1. ABOUT MEVinothKumar Pitchaimani System Engg @ Epro
TechnologyVinoths Contact:[email protected]:
thevino
2. Agenda About DNN How DNN works DNN Architecture DNN Features
Modules & Skins Working with DotNetNuke 3. About DNNDotNetNuke
is Open Source runs on Microsoft .NET Technology ...has advanced
web content management features makes web application development
efficient is highly extensible 4. About DNNDifferent DNN
Versions:1. DotNetNuke 3.x 4.2 supports .Net framework 1.12.
DotNetNuke 4.4 4.6 supports .Net framework 2.03. DotNetNuke 4.09
5.1 supports .Net framework 3.54. DotNetNuke 6.2(current) supports
.Net framework 4DNN Supports:1. Web 2.0 Concepts2. Ajax3.
Sliverlight 5. DNN WorkflowHow does DNN Work? 6. DNN Architecture-
3-tier architecture model with a core framework providingsupport to
the extensible modular structure. Presentation Layer Business Layer
Data Access Layer- DotNetNuke can be extended using 3rd-party
modules andproviders that add additional functionality. 7. DNN
Architecture 8. DNN Architecture- DNN 6.2 generation requires IIS
7.5 ASP.NET v3.5 SQL Server 2008- DNN 5.x generation requires IIS 6
ASP.NET v2.0 to v4 and SQL Server 2005 9. DNN FeaturesSome of the
DNN feature listed below: Easy to Install Easy to Use Powerful
Feature-rich Localized Flexible and Extensible 10. Modules &
Skins 11. Modules Written in .NET code (usually C# or VB.NET) Third
party modules can purchased for out of the boxsolutions Core
modules are included in DNN for basic functionality Modules allows
to extend DNN by adding third-partymodules or through in-house
development of customfunctionality Reusability 12. Modules The DNN
framework provides basic functionality such assecurity, user
administration and content management,while modules are used to
tailor the web site for specificdeployment needs Automatically
installed 13. Skins Written in HTML, CSS Makes DNN flexible to any
design Cross-browser compatible Multiple skins per portal Each page
can have unique skin Skins can be assigned at the host or site
level Reusable like Modules 14. Skins Separation between design and
content Skins consist of basic HTML files with placeholders(tokens)
for content, menus and other functionality Skins, can be
automatically installed through theadministration pages 15. Working
with DNN Once DNN is installed we can start working with the DNN.
16. Working with DNN Login with credentials to start working with
the DNN 17. Working with DNN Once logged in, youll see the Home
page again, but withmore administrative features. 18. Working with
DNN Its now time to setup the DNN users for the client. Selectthe
Users tab from the Common Task Panel You should then see the
following screen: 19. Working with DNN Select Add New User (bottom
left-center) to bring up thescreen below 20. Working with DNN Then
the below screen will appears 21. Working with DNN After adding
this new user, you will be taken back the UserAccounts page. 22.
Working with DNN Once you have done this, you can proceed to
editing theSite configuration by clicking the Site button in
thebelow screen. User will be redirected to the below Site Settings
Page 23. Working with DNN The Title, Description, and Keywords
fields will beadded during the content adding process of
thedevelopment, which will be provided by the copy writingteam. 24.
Dreamweaver File StructureLocal File Structure We now will setup
our local machine to reflect the filestructure from the server that
we need. In Dreamweaver, we will connect to the server throughour
remote view and then find the folder named after ourdomain name.
25. Dreamweaver File Structure 26. Dreamweaver File Structure 27.
Dreamweaver File Structure 28. Working with DNN Open the folder
where you have installed the DNN:Portals> _default. From there,
we will need to open theContainers and Skins folders Select the
Site settings button in the below screen. Then the below page will
appears in the Site settings>Appearance tab : 29. DNN Site
Settings Select the drop down menu to change the proper skin forthe
site. Site skins are typically named just that, siteSkin.Once you
have selected the skin for the site, scroll downslightly further
and select the Update link to apply yourchanges. 30. Changing Our
Skin Now we can see the skin applied to the site and can thuspull
the Cascading Stylesheet (CSS) to represent theinformation . Now we
can start changing the width of the structuralelements (such as the
shell, header, or content divs), thefont-family being used
throughout the site, the position ofsome elements such as content
and any inner-content,navigation, and others. The siteSkin.ascx
file may have to be modified dependingon the screenshot and your
chosen template to begin with. Now our page will look like this 31.
Sample siteskin.ascx fileSupporting js FilesSlideshow supp. files
FF filesAdmin Menu code 32. Sample siteskin.ascx fileHeader section
Slideshow Section Menu Callouts 33. Sample siteskin.ascx file
Content Pane CodeFooter Part 34. Sample skin.css fileStandard
layout structure Slideshow CodeCallouts Area 35. Sample skin.css
fileContent Code Navigation Code 36. Sample skin.css fileFooter
part 37. Pages 38. Pages We can add pages using the Pages tab from
the Admin Menu 39. Adding New Page 40. Navigation Admin Navigation
Code: This code should be placed ontop of the template design. 41.
Navigation Verti. Navigation Code: 42. Navigation Hori. Navigation
Code: 43. Content PaneContent Pane Code:
We can place this code to the template in where we want
todisplay the content. 44. Module DemoHow to Install a Module 45.
Adding custom third party module Login with Host credentials 46.
Adding custom third party module Module are extracted and installed
automatically. Installation Successful message appears at the end.
47. Sample Web Site
