There is no need to use MasterPages in this case.
The easiest way to add a class to the final page page body element (from a function) is to add that attribute class to the function output body element. Below Razor function is an example:
Other ways to dynamically manage the body element:
Make a C1 Function that has return type XAttribute and attach it as a child to your <body> open in your template. If C1 gets an XAttribute from a function it will stick it on the parent element.
Example C# Function code:
Example from a template where html is wrapped by a funtion call:
The easiest way to add a class to the final page page body element (from a function) is to add that attribute class to the function output body element. Below Razor function is an example:
@inherits RazorFunction
@functions {
public override string FunctionDescription
{
get { return "Add a class name to the page body, if not already defined"; }
}
[FunctionParameter(Label = "Class name", Help = "Help text here...", DefaultValue = "classy")]
public string Class { get; set; }
}
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
</head>
<body class="@Class">
</body>
</html>Other ways to dynamically manage the body element:
Make a C1 Function that has return type XAttribute and attach it as a child to your <body> open in your template. If C1 gets an XAttribute from a function it will stick it on the parent element.
Example C# Function code:
using System;
using System.Xml.Linq;
namespace Sample
{
public static class InlineMethodFunction
{
public static XAttribute ClassAttribute()
{
return new XAttribute("csharp", "value");
}
}
}Example from a template where html is wrapped by a funtion call:
<!DOCTYPE html>
<f:function name="Composite.Web.BundlingAndMinification" xmlns:f="http://www.composite.net/ns/function/1.0">
<f:param name="Page">
<html xmlns="http://www.w3.org/1999/xhtml" class="no-js" lang="@Lang">
<head>
<title>@CurrentPageNode.Title</title>
...........