Hi,

I have replicated the steps outlined in the following Episerver Forms Customization Documentation.

I have 3 questions regarding the implementation:

1- Custom CSS Path In the following code, I believe the data-f-resource attribute should point to my custom CSS file. My understanding is that the second part of the href should be the actual path to my custom CSS.

Below code is from Step 3 in the above forms documentation to copy FormContainerBlock.cshtml from \\modules_protected\\EPiServer.Forms\\EPiServer.Forms.zip\\Views\\ElementBlocks\\Components\\FormContainerBlock

<link rel="stylesheet" type="text/css" data-f-resource="EPiServerForms.css" 
href='@EPiServer.Shell.Paths.ToClientResource(typeof(FormsModule), "ClientResources/ViewMode/EPiServerForms.css")' />

However, since I’m working with custom CSS, I need to know how to modify the href part specifically @EPiServer.Shell.Paths.ToClientResource(typeof(FormsModule) to correctly point to my custom CSS file.

2- Future Updates to Episerver Forms (NuGet Packages) If there are any future updates to the Episerver Forms NuGet package, how can I ensure that my custom form will stay in sync with these updates? Is there anything I need to be mindful of or any precautions I should take to ensure my customizations remain intact after updates?

3- Is Customizing Episerver Forms Advisable? Lastly, I wanted to ask whether it's advisable to customize Episerver Forms in this way. Are there any risks of messing things up, especially with future updates or compatibility issues? Should I be considering a different approach for maintaining my custom forms without risking problems down the line?

I would appreciate any insights on this.