Hi,

I would usually create a special "SiteSettings" node and create tabs for the header, footer etc etc content that is site wide (some people like to put this content at the home node level but I think this is confusing for editors).

Then in your master template get your siteSettings node by ID (you can find the ID from the Properties tab). Do you have a "master" (site wide) template as per the tutorial https://our.umbraco.org/documentation/Tutorials/Creating-Basic-Site/Creating-Master-Template-Part-1 ?

You can also find this node by razor searching methods but for a site settings node which doesn't change then I'd hardcode it for speed.

@{
Layout = null;
var siteSettingsNode = Umbraco.TypedContent(4053);
}

Then in your footer you can do something like (note mine has a dynamic year)

<footer>
    <span class="copyright">Copyright &copy; @(DateTime.Now.Year.ToString()) @siteSettingsNode.GetPropertyValue<string>("footerCopyright")</span>
</footer>

Hopefully you can see how to use that siteSettingsNodes to output your footer links or other content as required.

HTH

Steve

An easy solution would be to add the dynamic contents in a dictionary. That way a backoffice user will be able to change the contents whenever a change is required.

Depends on how exactly you want the user to be able to adjust the footer and how automated you want it to be. Have you heard of Archetype: https://our.umbraco.org/projects/backoffice-extensions/archetype/

It's pretty great. I use it for most everything in Umbraco, including menus. If I were creating a footer menu that I planned to split into multiple, columns, I'd use an Archetype to define those columns.

Also, I'd have nested Archetype fieldsets that allow me to pick the content nodes to appear within each column. You can do things like create multiple fieldsets so the users has control over how to pick nodes.

For example, you could create a fieldset that allows a user to pick a node to serve as the ancestor node so all descendant nodes will automatically be added to that footer column. You might add a property to this fieldset to allow the user to exclude certain parts of the subtree of those descendants (e.g., maybe there are thousands of products and you don't want them all to show in the footer).

You could create another fieldset that allows the user to explicitly pick content nodes to appear in the footer. The sky is really the limit when it comes to Archetype.

is working on a reply...