Hi Ben.

That's pretty simple, it depends on whether you want to refer to a static pure html page or a "real" page in your dnn-portal.

Put one of the following lines into the acsx-file of your skin.

1) For Example you have a html-file called impressum.html:
<a href="<%= Page.ResolveUrl("~/portals/0/junk/impressum.html") %>">Impressum</a>
This will call the html-file in the given folder, here is it the folder JUNK

2) To refer to a real page:
Call your page from e.g. the admin-pages-menu, remember the tabid and then e.g.:
<a href="/Default.aspx?tabid=162">Impressum</a>
So here is it the page with the tabid 162

That's it.

Kai

Thanks for the replies guys.

I want the pages to be proper DNN pages so that the content pane is editable by the end user.  I understand the first solutions, but since the tabid values might change when I roll out to production so I don't necessarily want to hard code those.


Timo,

I'm not following your suggestion completely.   I understand that I can create a page that simply redirects to an external URL or a page within the site (or a file it appears) but I'm not quite certain how I use that in my situation.

These pages are being linked to from a UL in the footer, which is not editable in DNN so how would you use the interface to edit them?

Thanks guys, sorry for my cluelessness!