To override that, you’d need to create a rule in your CSS file that’s even more specific.
The build variables $(ProjectDirectory) and $(OutputDirectory) are available from the Insert Build Variable button in the Build Events tab in the HTML target, so this is adaptable for other targets. If Chrome Dev Tools telsl you a style is set on element.style, that means it’s set inline on the HTML (usually by JavaScript). The /y is very important - with the help of MC support, I discovered that there's a backend "permission" needed in order to override the files of these names, since they are core source files from MC.
Override css style forum skin#
It also copies three images I use in my skin into the output (Skins\Fluid\Stylesheets\Images folder).įor %I in ($(ProjectDirectory)Content\Resources\SideNav-Layout\Styles.css $(ProjectDirectory)Content\Resources\SideNav-Layout\Tablet.css) do xcopy %I "$(OutputDirectory)Skins\Fluid\Stylesheets" /yįor %I in ($(ProjectDirectory)Content\Resources\SideNav-Layout\Image1.png $(ProjectDirectory)Content\Resources\SideNav-Layout\TabletImage1.png $(ProjectDirectory)Content\Resources\SideNav-Layout\Image2.png) do copy %I "$(OutputDirectory)Skins\Fluid\Stylesheets\Images" What is the difference between adding override code in extensions>templates>styles>advanced settings>custom CSS code box (code stored in. This command copies my skin stylesheets (from their locations in my project directory) and replaces the files in the output (Skins\Fluid\Stylesheets directory). I designed my own skin stylesheet, which I use to override the default Styles.css and Tablet.css files in the target's OUTPUT folder (not the original MadCap source Styles.css/Tablet.css - I don't touch that). **this might not be the best way to do this, but it works. I know this is an old thread, but I thought I would add some info about a post-build command that I created to import my own skin styles into my side-nav HTML5 output.
0 kommentar(er)
