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; } } }

global setting for includes and images

seshusatya

hi,

I got different sub-branches under "function" branch.

I need to include images,header,footer in all the templates under sub-

branches.So I want to store all these images,header,footer files under main

branch("function") so that I can include where ever it is necessary.

Where can make this settings.

regards,
chakri

Find more posts tagged with

Comments

Adam Stoller

hi,

I got different sub-branches under "function" branch.

I need to include images,header,footer in all the templates under sub-

branches.So I want to store all these images,header,footer files under main

branch("function") so that I can include where ever it is necessary.

Where can make this settings.

regards,
chakri

I think you're talking about using iwproxy - in which case you need to read the TeamSite Administrator's Guide

sureshm

Hi Seshu,
It is always good to store htmls, images etc in the htdocs folder. So better you create a workarea in your main branch(ie, function), and under the function branch create the htdocs folder. And place all your stuff in the htdocs folder.

thanks,
sureshm

Trey

I don't think htdocs would be a good location to store these IMHO, put them in the top level branch you created and then use the iw proxy as mentioned previously. We do this and it works great.

[color=red]One tip: even though we have this in the top level branch on our server we have it stored in a locaiton called "common" that gets deployed independently of the other files on the branch. That way you can refer to "/common" in your proxy config for the sub-branches, so the branch remaps will be much simpler to create. When you deploy, all the branches should be able to see the common location with no special configuration needed on your production web site (this is assuming that the sub-branches will all deploy to the same site in the end). [/color]