Friends I am starting to build one site using DotNetNuke. I am completely beginner in the DotNetNuke. I have mock up of site in html and i need to create skin and layout in DotNetNuke as in mock up. I tried to include the files in skin folder of DotNetNuke but it doesn't work.
And i am stuck with this. So, If anyone suggest me how can i change my mock up into the skin of my site in DotNetNuke?
I would start by looking at the Basic DotNetNuke Skinning webinar I recorded last year, it will give you an intro to Skinning for the platform.
http://www.dotnetnuke.com/Resources/Training/Basic-Skinning.aspx
You could also take a look at http://multifunction.codeplex.com for an example skin
Related
I want to convert my site into DNN, I have three CSS files: main.css, slick.css, slick-theme.css and two js files: main.js, slick.min.js. In their particular folders named i.e. css, and js. And one img folder containing all the images.
I think the best solution is to include those files into a dnn skin (theme).
Either you install a minimal skin and you modify it to include them, either you could developp your own dnn skin.
If you developp a skin, the file main.css can be renamed skin.css to be automaticaly loaded by dnn.
I think that main difficulty will remain to create the layouts using dnn skin objects like the menu. You can look at the Xcillion skin to see an example. It uses the DDRMenu which is flexible component to design website menus.
Here are some links to help you:
the official documentation for designers
http://www.dnnsoftware.com/DOCS/designers/index.html
an article with
many links https://www.dnnsoftware.com/wiki/dotnetnuke-skins
2sxc 11.x / DNN 9.x
I have a DNN instance with a portal with lots of Content modules with different Content Types and Templates. I'm going to be making a second portal that is related to the first portal and there is some shared content. Is it possible to allow the first portal to share it's 2SXC content types and templates with the second, new portal? If so, how?
There are a LOT of ways to do this, and unfortunately there is no good guidance document 😟.
Your scenario sounds like what you would need Ghost-types for: one app creates the real type, the other app just has a ghost-reference for the original type. This is a common way to solve this - and yes, it's a very well kept secret 😉.
But I went ahead and created a checklist, just for you 🚀 https://azing.org/2sxc/r/Pj4GMYY5
I am developing a mobile app that uses DNN on the backend. I want to create a Web API that receives a DNN UserID and returns the user's Profile Picture.
Most of the documentation and posts speak to developing Modules and focus on DNN Templates that are available.
All I want to do is add a reference to DNN Library in my Visual Studio Project so that I can access the DNN API. I right click on references yet can't find DNN.
How is this accomplished?
Thanks.
EDIT... I'm developing on the same server that DNN is running on.
It turned out it was a simple matter of pointing to the dll's I wanted to use in the bin subfolder of DotNetNuke.
My company has a enrollment website that is currently in DotNetNuke. I've been directed to "strip out nuke from the site" but from everything I've read it is the opposite that the site is in dnn not the other way around.
Has anyone had to migrate a site from dnn and if so can you point me towards some resources or give some insite to get me started?
The site is dnn 5.04
If you want to strip things down to absolute bare bones (HTML, images, JavaScript), you could use a tool that basically copies down an entire website to your local machine, such as HTTrack.
Download the app, give it your DNN website's URL, and it'll spider the entire website, download each page individually, along with any of its images and scripts. You'll be (theoretically) left with a full website containing all your content pages, which you can edit in a plain text editor.
All the user management, role management, content management, admin only areas, protected content, etc. will not carry over with this method, but that will be the case regardless if you're moving from DNN to a normal static HTML website.
An "enrollment website" sounds more like an application than a static HTML site and if that's the case then just grabbing the rendered HTML isn't going to be the best option as you wouldn't get any of the functionality. My approach would be to first find out why they want it pulled out of DotNetNuke. Perhaps it was poorly implemented and they are blaming DNN when the problem was actually how it was built. DNN may be a good solution and it might be best to convince them to leave it as DNN but improve the implementation.
If you do need to pull an application out of DNN and the enrollment piece was built as a custom module, it should be fairly easy to convert the ascx files of the custom module to normal .net User Controls.
If the Enrollment application was built using a Forms Module of some form, then you will likely need to rebuild it from scratch.
I am new to DOT NET NUKE 6.0 and facing a problem. The scene is that I have created a very simple user control in Visual Studio(by using ASP.NET/C#). Now I just want to add it as module in my DNN portal. Task is simple but I don not know how to do. Any help, video link, site is appreciated. I am working in DNN 6.0
Thanks
There are a bunch of resources on the DotNetNuke.com site. Take a look at the wiki entry at http://www.dotnetnuke.com/Resources/Wiki/Page/module-development.aspx. It has links to a video series that should be helpful to get started.
If you already have a control, you should make sure that it inherits from PortalModuleBase, and use the Extensions module (under Host) to create a new module from the control. DNN will create the record for it, and even create a test page with the module on it for you.