-
Notifications
You must be signed in to change notification settings - Fork 1
2sxc
-
The "Accu" folder in the 2sxc/Content directory is a separate GitHub shared project. So you should NOT be creating, editing, or moving anything to that folder as it will get overwritten or deleted when Accu gets updated.
-
In 2sxc/Content we don't edit the original files of the 2sxc Content App. When we make a new View that is custom to the client, we create that in
2sxc/Content/[ABBV]/
. -
In 2sxc/{any 2sxc app}, we don't modify the original files. And we do not use the client ABBV folder. Instead we copy/paste any file we need to customize in-place, and rename following the BEM pattern, usually leading with the client ABBV, e.g.
..2sxc/Swiper/_MARS__Swiper--basic.cshtml
(original was just..2sxc/Swiper/_Swiper.cshtml
).
For module (or page) specific CSS that does not belong in the Theme, AccuTheme supports compiling *.scss files in the src/styles/Modules
folder to the theme's /dist folder. There are multiple examples of this in the CUAM2020 project.
-
name your source file well and include a comment so its obvious where its used (e.g.
2sxc-Content-Links.scss
) -
there are samples in src/styles/Modules (Carousel.scss and LazyYouTube.scss) that demonstrate the mandatory and optional imports (functions, variables, etc)
-
AccuTheme.ThemeCssPath() will provide the path to the /dist folder:
2023:
<link rel="stylesheet" href="@(AccuTheme.ThemeCssPath)/2sxc-Content-Links.css" data-enableoptimizations="true" />
2022:
<link rel="stylesheet" href="@(AccuTheme.SkinCssPath)/2sxc-Content-Links.css" data-enableoptimizations="true" />