You could still just have one project file with multiple pages. I see a main index file. I see sections as just being groups of pages that may use identical symbols for headers. When you created the pages, did you duplicate or create a new page everytime ? If you duplicated the pages then you may have transfered the class settings as there is only one main css file. If you create new pages and then create a header and add it as a symbol to your library, you can then use that symbol on any groups of pages. Any change to the symbol, will transfer to all pages using that particular symbol.

This will allow you to keep all assets available to your project in one resource location. And you can use common symbols like a footer for instance on all pages. I would investigate the proper use of symbols as they can save you lots of time. Just remember, once you make a change to a symbol, even if it is used in another project I believe, it changes everywhere - right Wayan ?

Just remember, once you make a change to a symbol, even if it is used in another project I believe, it changes everywhere - right Wayan ?

Naaaah
If just a symbol, then only on that project will it change everywhere in that project that it is linked to.
If you want that symbol on another project ~~~ create it as a COMPONENT, ~~~ save it to your resources,, & then load it into your new project,, then save it as a symbol in that new project.

:)Thanks for the clarification Wayan....I remember seeing that in one of your videos.

<Quote: Edward Wrote>Now, the question for me is... do I combine all the images, unique file names and all, into a single image folder and the same for resources all with unique names? This is getting more complicated than I want it to be.<quote />
I'm getting more & more confused as to what one is trying to acomplish and why the more it goes on,,
If I an understanding this right again,,
Create a folder in your resources ~~~ call it "Images"
In that folder create other folders call them whatever is relevant to the images page name that you want the images to be in
place the images you want for that page in that folder,, then when you put the images on the page browse to the folder in your resources,, choose the image boom in it goes.

That was for COMPONENTS
When you load a component to a project,, you should delete it from your components bit (ON THE PROJECT PAGE) not in the library, once you have it placed,, because for some reason, any changes you make to the component without deleting it, get put into the component in the library,, hence if you open the component in a new project it is possible that the component will have the styling from the last project,, which isn't much good really.

I appreciate all the discussion and ideas. It looks like I'll have to get familiar with symbols. I guess my design ideas have me wanting to run when I'm still at the crawling stage. I think I'll just let the design sit idle while I dig up some info on symbols and components. I want to add that there are moments where I'm having fun, with RSD which means some of the struggle with the learning curve is dissipating.

Wayan, you have videos posted? I'll have to check that out.

Michael, humility IS good for the soul, regardless of how many years you've been doing this. I've been using CC HTML Editor for 20 years fyi, but it's a different era now, so it's a struggle for me to get used to the "new tech" too, and some things CAN still be done better just by looking at the code, and thinking that through

Russell,
I can't agree more about humility and about getting up to speed on the new way of web designing. And I am pleased that CoffeeCup has provided this big learning curve for me. I recall when I first started with html and I was told at the time that html is easy to grasp, and my thought was... Yeh, so is brain surgery once you've done it a few times.

Well, it's back to the learning curve for me. Thanks for your thoughts.

Edward Cannell - It sounds like you are starting close to the point I was when I started using RSD. For many years I hand-coded all html, js, css, etc. At first I was slowed down and felt confined by RSD. I must admit, after finally working out a plan to use this product in a way that works for the way that I work, I have come to find RSD very useful.

I got around the limitations of all files created in one folder, and the slowing down part, by using RSD as more of a "template" creator. It has been working very well so far. I create a page, or even just part of a page, in RSD. I layout the framework, create most of the css in RSD. Then I export. Then I move the files that I want to work with to an entirely different location. From there I can hand code the pages to change paths for files in different folders, which is almost necessary with a huge site with hundreds of pages and sections. Then I also edit or add to the content as needed, including adding custom js and css as needed. If I find that I need to tweak the framework or main css, I go back to RSD, make the changes, export, then usually just copy over the styles and framework folders. Sometimes if the changes are major, I will copy over the html or part of the html. This method also helps when there are many pages which are similar layouts but just different content. I can just copy the html to multiple files and edit as needed.

RSD has become a very valuable tool for creating the frameworks and responsive css.

Note - organizing html files into logically named folders also helps for SEO, in comparison to keeping them all at one level.

DebC, yeah, getting accustomed to RSD takes a lot "time" and effort to think of it as a "template" creator, as the title infers as Responsive Site Designer, then use the HTML editor to adjust the navigation links and add additional content, such as live stream videos that can't be properly added in RSD.

I started looking at RSD last week, and have been looking around at methods for a cleaner navigation as it's a missing factor as I have a plethora of pages to migrate from a custom, but crude PHP setup at this time. PAC12 for instance: http://xc2.i4atv.info/ggwplive/pac12/index.php

Like Edward, I need "sections" which are the old folder system, as I have a membership option for most of the feeds through my site that currently has a crude .htaccess/.htpassword setup that I'd also like to make easier to login and stay logged in per session() vs each time the browser window get opened, but that will come in due time, as having a decent, mobile friendly navigation is just as critical for good customer service.