Hi,

You can create a new block class like this-

 public class SocialMediaBlock: BlockData
    {
[CultureSpecific]
[Display(
   Name = "Social Media property 1",
   GroupName = SystemTabNames.Content,
   Order = 100)]
public virtual bool SocialMediaPropertyOne{ get; set; }

[CultureSpecific] 
[Display(
   Name = "Social Media property 2",
   GroupName = SystemTabNames.Content,
   Order = 101)]
public virtual bool SocialMediaPropertyTwo{ get; set; }
}

Then create new a new property on the actual page-

  [Display(Name = "Social Media Section", Description = "Social Media Section", Order = 55, GroupName = SystemTabNames.Content)]
        public virtual SocialMediaBlock socialMedia{ get; set; }

Thanks Ravindra!

Is there any way to do this without making it a Block?  The settings are not intended to be used like a block, but instead just organized

It will render like this -

Social media heading

PropertyOne

PropertyTwo

So don't worry you don't need to create a new block it will show you all the property on the page.

Please try once and let me know if you have any issue

Ravindra,

I added this and it looks great! My one concern is that I did not want the Content Authors to see this and try to use is as a normal block.

I added AvailableInEditMode = False to the definition to hide it from the block options that show up and this seems to be a perfect fit!

Thanks for your help!

I am glad that it helped. Always happy to help the community.

Ravindra,

Not sure if you are attending the Ascend Conference next week, but if so maybe we can meet up!

I think Ravindra's solution should be preferred, but if you only want headings in-between normal properties, you could follow my blog post:
https://www.gulla.net/episerver-help-texts-improved/

Just drop the CSS border, and use only Name (not Description) in:

[Display(Name = "My custom heading!")]
[UIHint("HelpText")]
public virtual string MyCustomHeading { get; set; }

Great post Thomas. Seems like you did lots of finding for that. Goodone.