Serviceware Portal — Custom CSS

Guide and starter kit for customising the look of the Serviceware Portal with an uploaded custom.css file.

Beta function, no official support. Everything documented here was tested in a running Portal.

What is in this repository

Path	What it is
starter-kit/	The starter kit, unpacked. Browse and copy single rules from here.
starter-kit/README.md	Short how-to: upload, remove, try a rule without uploading, what to avoid, what to do if the Portal becomes unusable.
starter-kit/custom.css	Template with ready-made, tested rules. Everything is commented out — switch on what you need.
starter-kit/reset.css	Empty file. Upload it to switch a custom design off in seconds.
starter-kit/ai-context.md	Paste into an AI assistant before asking it to write Portal CSS. Stops it inventing element names the Portal does not have.
docs/portal-custom-css-guide.docx	The full guide, for handing to customers.
docs/portal-custom-css-ai-context.md	Same AI context file, kept next to the guide.
dist/portal-custom-css-starter-kit.zip	The starter kit as one download for customers.

Quick start

1. Download dist/portal-custom-css-starter-kit.zip, or copy the files out of starter-kit/.
2. Edit custom.css — uncomment the rules you want.
3. Portal: Administration → Configuration → Global configuration, card Advanced styling → Browse files → Save changes.
4. Reload with Ctrl + F5. If nothing changed, press Ctrl + F5 again — the browser caches stylesheets.

Limits: a real .css file, max 2 MB, one file for the whole Portal, always stored as custom.css. It does not apply to the login screen.

Emergency: the Portal is unusable

1. Upload reset.css, or use Clear file, then reload.
2. If the configuration page itself cannot be used: F12 → Elements → delete the <link id="customCssLink" ...> line near the top. The Portal is normal for as long as the window stays open — long enough to remove the file properly.
3. If that does not help, contact Serviceware Support and say a custom CSS file has to be removed.

After a Portal update

Element names can change with a new Portal version. Open the Portal after every update and check the parts you styled. Keep the previous version of your file so you can go back with one upload.

Keeping the zip in sync

dist/portal-custom-css-starter-kit.zip is built from starter-kit/. After changing anything under starter-kit/, rebuild it:

cd starter-kit && zip -r ../dist/portal-custom-css-starter-kit.zip . -x '.*'

The zip must unpack into a portal-custom-css-starter-kit/ folder, so build it from a copy of that name if you repackage by hand.

Source

Maintained alongside the Portal frontend (azdops.serviceware.net/sw/Platform/Portal/_git/SSP_Portal, docs/).