Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...Large document menu navigationLarge document menu navigation
Previous
 
Next
New Post
9/19/2006 2:05 PM
 

Anyone have any suggestions for either in the box or out of the box CSS, skin mods or tweaking on best structure to put 100's of pages inside of DNN 4.x?

Currently it is being handled by DNS, and then a single navigation menu broken down into groupings

  • a.corp.com
    • 1 (Category - an unclickable value in the nav menu, aka a header)
      • pagea11.asp
      • pagea12.asp
      • ..
      • pagea19.asp
    • 2 (Category - an unclickable value in the nav menu, aka a header)
      • pagea21.asp
      • pagea22.asp
      • ..
      • pagea29.asp
  • b.corp.com
    • 1 (Category - an unclickable value in the nav menu, aka a header)
      • pageb11.asp
      • pageb12.asp
      • ..
      • pageb19.asp
    • 2 (Category - an unclickable value in the nav menu, aka a header)
      • pageb21.asp
      • pageb22.asp
      • ..
      • pageb29.asp

First, I understand that I could set up multiple child portals and keep using the a.corp.com and b.corp.com domains. For PR, I wanted to put all the content together if possible.

Secondly, is there a recommended way to create the category headers in the navigation menus? Create a Page 1 and Page 2, to have no content on them seems odd. Is that the only way to achieve a seperator or grouping category in the navigation?

Thanks for any pointers or suggestions!

 

 
New Post
9/19/2006 5:06 PM
 

This really isn't the forum to put a post like this since although it's got some menu related elements, you're really after a solution that allows you to provide replicatable content between portals.

DNN handles this by way of child portals - eg.. multi site instances on a single code base.

I'm working on a project at the moment where we are doing exactly that and there are are many links and documents to be imported into the new site.

Rather than work with the hundreds of html modules required to put them in, I'd be working with the http://www.ventrian.com articles module and using the http://www.inventua.com shadow option - which will allow you share content between portals. I will let you know though that some modules do not always share too well, but I think the articles module is fine.

And example of the shadow module can be seen on http://www.ninasfreeskins.com as you browse through the different portals - they are linked at bottom of page through a portal sharing skinobject, but the content is for the main part, exactly the same content shared throughtout the portals.

The articles module is interesting as you can use it to add content in, one area, and use the copy function on other pages if you wish to put it on other pages. 

At the moment, I'm using the articles module on http://www.catalooksupport.com where the 300 page manual has been put online.  What I've done here is put the chapters of the manual on a page of their own, as the one thing you can't really do is put multiple versions of the module on the same page for editing.

I think I know what you are trying to do, and there are only suggestions, but what I feel is that you have content you want to share between portals, and looking for an efficient way to do it.

We spend a fair bit of time manipulating information, cleaning it, reformatting and placing into this type of solution to migrate content to DNN.  While it initially takes some time to setup it's really very easy to manage in the long term.

Once finished (later today or tomorrow) I will provide links on a new site my guys are working on (just one of many I'm trying to get finished) where we speakers and sessions and I've customised the articles module for them, and thought of how to connect the speakers bio to the sessions, and the speaker sessions back to the bio. It removes the need to have so many modules placed in the page, allows for overall custom formatting using the templates which is very cool.

I think DotNetNuke is specifically designed to handle what you are trying to achieve, but to streamline the processes and understand how the modules work to your advantage.

I hope this gives you some idea.

Nina Meiers


Nina Meiers My Little Website
If it's on DNN, I fix, build, deploy, support,skin, host, design, consult, implement, integrate and done since 2003.
Who am I? Just a city chic, having a crack at organic berry farming.. and creating awesome websites.
 
New Post
9/19/2006 9:24 PM
 
nina wrote

This really isn't the forum to put a post like this since although it's got some menu related elements, you're really after a solution that allows you to provide replicatable content between portals.

I've heard that before in another forum, hence my posting it here where they suggested I skin the menu :)

Actually, all of the content is unique under the current websites. In that manner I can go with sub portals, and deal with a smaller subset of content in the modules. In current .aspx/.asp html code on pages that I am using, i am under the scenario of:
a.corp.com
b.corp.com

To increase PR and aggregate the content under the parent site, I want to move it under:

www.corp.com
www.corp.com/a
www.corp.com/b

So today, I have seperated out the bulk of the menu items (each menu item being an <A> to a single page) by groupings under titles, and the seperate sites.

I can see doing that with child portals. But, and here is the but, my goal is to collapse all the content under a single site, not keep it spread out across all the sites.

The child portal scenario seems wrong to get around a navigation problem, especially since editors are the same group not seperate per site domain.

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...Large document menu navigationLarge document menu navigation


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out