Skip to main content
Participant
July 15, 2022
Answered

Change CSS folder

  • July 15, 2022
  • 5 replies
  • 1288 views

Hello,

 

Me and my colleague are creating 2 different pages but using the same CCS template file. So any changes that are saved by the other user is replicated on each others pages.

Example if i change a button to green and on my colleagues page he has the same button red if I then save my changes his button will turn green. How can we use the CSS template and not effect each others work.

 

Thanks 

This topic has been closed for replies.
Correct answer Adam252620424e5k

Hello, Thanks for all your inputs..
we shortly after I posted figured to change the file in the link tag. Although we had already saved CSS style file in different locations, we had done this after the fact and was still impacting eachothers work. 

 

All working as intended. 

 

Thanks 

5 replies

BenPleysier
Community Expert
Community Expert
July 15, 2022

Use CSS classes carefully. If a button is red then give it a class of red. If you then want to change it to green, give it a class of green. That way it will not affect the red buttons as in

.button.red {
    background: red;
}

 

You could also give the BODY-tag an ID of say `index`. That way `index` can be used as part of the selector as in 

#index .button {
    background: red;
}

 

Wappler is the DMXzone-made Dreamweaver replacement and includes the best of their powerful extensions, as well as much more!
Adam252620424e5kAuthorCorrect answer
Participant
July 18, 2022

Hello, Thanks for all your inputs..
we shortly after I posted figured to change the file in the link tag. Although we had already saved CSS style file in different locations, we had done this after the fact and was still impacting eachothers work. 

 

All working as intended. 

 

Thanks 

Nancy OShea
Community Expert
Community Expert
July 15, 2022

Use File check-in/out feature so you're not messing with the same files at the same time.

https://helpx.adobe.com/dreamweaver/using/checking-checking-out-files.html

 

Or as @osgood_ said, use separate stylesheets.  

 

My guess is that you each want to do your own thing.  If that's the workflow, you should have one global stylesheet for sitewide styles, and use embeded styles in the document <head> tag for page specific styles.

 

Hope that helps.

 

Nancy O'Shea— Product User & Community Expert
B i r n o u
Legend
July 15, 2022

I agree but checkin / checkout, is really messay... you need to always acquire the file to place any modification, but as far as I understand from @Adam252620424e5k , each developers need to change the content for its own page. So CI / CO wont work for that case.

Nancy OShea
Community Expert
Community Expert
July 15, 2022
quote

I agree but checkin / checkout, is really messay... you need to always acquire the file to place any modification, but as far as I understand from @Adam252620424e5k , each developers need to change the content for its own page. So CI / CO wont work for that case.


By @B i r n o u

========

Check-in/Check-out is not messy.  It's a prudent precaution for collaborative work enviroments with sitewide CSS files, scripts and other common assets to prevent one user from stepping on another user's work.  

 

It goes without saying that all such logistics should be supervised by the project manager in charge.

 

 

Nancy O'Shea— Product User & Community Expert
B i r n o u
Legend
July 15, 2022

an mix of both solutions listed above,  will be to add beside the CSS template page, a new blank CSS file to each pages.

Each one of you will write on the blank page the needed modifications without affecting the olter page.

None of you will modify the template CSS page.

 

Page A

 |__ template.css

 |__ pageA.css

 

 

Page B

 |__ template.css

 |__ pageB.css

Community Expert
July 15, 2022

You can also use GIT and fork one work to develop an alternative solution whithout affecting the previous repository.

Each branch can then be merged together if needed

 

start using GIT in DW https://helpx.adobe.com/dreamweaver/using/git-support.html

then this tutorial is not perfect but enought clear to start with forking… https://www.toolsqa.com/git/git-fork/

Legend
July 15, 2022

Make separate copies of the css file, save them as different names, a and b. Link a.css to your page and b.css to your colleagues page. 

 

You can't share the same css files which is linked to both your pages, make a change in that css file and not have it affect both of your pages as its linked to both pages.