nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

GUI / Customization

kennethl

Hi Folks,

Just wondering if there are ways to customize the contentcentre interface and make it more intuitive and less technical looking.

The end-users using this for CMS for the current project I am working on are expected to have zero knowledge regarding Teamsite and I foresee steep learning curves for simple tasks even.

One thing I can think of for now is an external website with URLs point to specific DCRs to make navigation much less of a hassle for non-Teamsite literate folk.

Do you guys have any other ideas / if there is any way to improve the overall user experience and usability of Teamsite?

Regards,

KennethL

Find more posts tagged with

Comments

Garth McMillan

You can alter it quite significantly. Look at the UI customization guide for information.

Depending on how much you want to change it you can:

Alter the CSS
Alter the UI config files
Alter the JS/JSP files that generate the interface.

Migrateduser

There are two interfaces in TeamSite. Standard and Professional. If you're not using Standard then you should look into it. It was made to be more user friendly and more of an interface for Authors. That being said. We only using the Professional interface because it offers more functionality compared to Standard.

kennethl

Thanks for the info guys,

What I'm looking at is changing the pre-login splash image (Interwoven Teamsite ContentCentre) and the ContentCentre logo on the top-left post-login screens to for example, a company logo with system name.

I was told that changing that is possible but changing that will affect all CMS projects using the same server (I have several projects running on a single TS server).

Is it possible to change these images so that it is only reflected for a particular project/store/folder and shown only to these users who have access to that?

Cheers, KennethL

Garth McMillan

Yes, as far as I'm aware they are set globally.

You could probably change the logo on a per-user situation for users that are logged in to TeamSite (either via JSP or JS), but you need to be aware that TeamSite (at least in version 6.7.2) uses frames so the header/banner doesn't reload as you move through the interface.

The initial TeamSite login screen is a single page presented to all users - I don't think there would be a suitable way to customise that for different people - as TeamSite doesn't know who they are at that point.

If you really want to customise it I guess it would have to be via JSP outside the realms of TeamSite.

kennethl

Thanks Zaarin for your reply, I am using TS version 6.7.2 and for DCTs and workflow steps they open for editing via pop-up windows current, so in a single session where a user makes a content edit / DCR edit, there can be as many as 5 popup windows including workflow steps that open.

Just wondering if there is a way to have these in-frame and within the content centre browser itself which I always thought should/would be the default way to display such things.

Garth McMillan

You would be modifying a huge amount of code to remove the popups (JavaScript and JSP code + plus associated files). I don't consider that to be practical, due to the time required, and you would lose your ability to upgrade/patch TeamSite.

Unfortunately I think we just have to deal with TeamSite's million popup windows.

As far as easier customisation goes, CSS is the easiest. Pretty much all sections of TeamSite have a custom.css (empty by default) which overwrites the base TeamSite CSS. /TeamSite/local/config/lib/content_center/customer_src/web/base/styles/custom.css is referenced by pretty much all pages. Each section of TeamSite also has a custom.css as well, if you want to have the styles applied to only a section of the interface - for instance data capture forms.

The next easiest would be to add/reference some JavaScript from /TeamSite/local/config/lib/content_center/customer_src/web/base/util/headers.inl (which is inserted at the head of pretty much every window) to do some more extreme manipulation (add/remove things etc.)

Finally you can alter the code that builds each section of the interface (usually JS or JSP). There's often a lot of nested includes and referenced files that you need to work through for this and the same files may be used in other parts of the TeamSite interface, even though it's not apparent at first, so you need to be careful.

Just remember that any modifications to files under /TeamSite/local/config/lib/content_center/customer_src/ require you to run "make_toolkit.ipl" before they will be shown in TeamSite (running this command brings down TeamSite for a couple of minutes). If you want to test on live files you can edit the files directly in the relevant folder under the /TeamSite/httpd/ folder (make_toolkit copies the relevant files to the httpd folder, and builds/resets the code/server if necessary).

juanrod

Hi Zaarin, currently I am trying to add some JavaScript code to the Component Properties window.

I have not found the directory you have mentioned before "/TeamSite/local/config/lib/content_center/customer_src/web/base/util/headers.inl".

I am working with TeamSite version 7.3 in Linux and in my installation the directory ../base just have these two folders: help and styles.

Can you explain me how can I add the javascript code?

Thanks in advance!

jagadesh

Hi Zaarin, currently I am trying to add some JavaScript code to the Component Properties window.

I have not found the directory you have mentioned before "/TeamSite/local/config/lib/content_center/customer_src/web/base/util/headers.inl".

I am working with TeamSite version 7.3 in Linux and in my installation the directory ../base just have these two folders: help and styles.

Can you explain me how can I add the javascript code?

Thanks in advance!

In 7.x version it will be found under Application Container ie under iw-cc.war.
/iw-home/Application Container/server/default/deploy/iw-cc.war/base/util/headers.inl
Please refer the customization change and build process in the 7.x manual.

Adam Stoller

In 7.x version it will be found under Application Container ie under iw-cc.war.
/iw-home/Application Container/server/default/deploy/iw-cc.war/base/util/headers.inl
Please refer the customization change and build process in the 7.x manual.

Files should not be changed directly in the ApplicationContainer directory - instead, create the correct directory structure in customer_src or livesite_customer_src and then run make_toolkit or build.sh (respectively) to push the customization into place within the ApplicationContainer directory.

jagadesh

In 7.x version it will be found under Application Container ie under iw-cc.war.
/iw-home/Application Container/server/default/deploy/iw-cc.war/base/util/headers.inl
Please refer the customization change and build process in the 7.x manual.
Files should not be changed directly in the ApplicationContainer directory - instead, create the correct directory structure in customer_src or livesite_customer_src and then run make_toolkit or build.sh (respectively) to push the customization into place within the ApplicationContainer directory.

Even i have told in the same intention

Garth McMillan

I've just gotten a couple of private messages about this, so I'll just write it out very clearly here for the benefit of everyone, expanding on what ghoti said:

TeamSite uses files from within the "ApplicationContainer" folder. You don't want to edit these files directly, you want to overwrite them with your custom versions from "customer_src".

Take a copy of the files you want from the "ApplicationContainer" folder and create them in the "customer_src" folder (create the folders if needed).

eg. \Interwoven\ApplicationContainer\server\default\deploy\iw-cc.war\base\util\headers.inl to \Interwoven\TeamSite\local\config\lib\content_center\customer_src\web\base\util\headers.inl
Make any changes to the files in the "customer_src" folder, then run "make_toolkit.ipl". "make_toolkit.ipl" will overwrite the "headers.inl" file in "ApplicationContainer" with your customised version.
If you wish to go back to the original file, delete your customised file in "customer_src" and run "make_toolkit.ipl" again. TeamSite will restore the default file.

You can do this to overwrite pretty much any file you want.

Adam Stoller

[QUOTE=Zaarin][...]

Step 3 may not always be sufficient, sometimes you have to run install_webapps.ipl to refresh the content in the expanded war file (in ApplicationContainer) from the vendor-supplied war file from whence it came.