Great Video Mansour
Glad you liked it
Building Sticky/Fixed Navigation With Responsive Site Designer
I ran into a situation where I needed to provide an alternate version of a page that has a lot of inbound and outbound links, and I didn't want to edit within the original project file. My first thought was to build a new project file containing the desired page with alterations, stick it in a sub-folder and link to it. The large number of inbound links to the page name from the original project pages quickly made that an unhappy task, I would have to find and edit each one to point to the new relative URL and then maybe undo that later.
Then I starting thinking about what actually makes a project file unique - and so I tried the following, and it seems to be working. CAVEAT: to do this, be careful that you do NOT have two different resources (pictures or include files) that have the same name. This might also have some potential to help circumvent the 75 page limit in effect, albeit not in fact.
I built a new project file - created my alternate page, got it looking the way I wanted it, then exported the project. I went into the newly exported css folder and renamed the main.css file to custom.css - (any unique name would do), then renamed the default named index.html to the page name I desired, and edited the coffee cup created header link to main.css to point to custom.css.
I dropped the 'new page' into the 'website home' folder of the hosting server, copied the custom.css into the css folder there, (all of the graphics in this project were being reused from the first project so I didn't need to update the images folder (the folder I put all of my image resources into).
This would also seem to be a potential solution for situations where I have a page or two that have conflicting break point requirements, compared to the rest of the site. Might also be a solution to main.css bloat when the class 'count' starts getting out of control.
TO RECAP: the obvious gotchas are a collision between identical page names or different resources with the same name. I just gave this a shot and it seems to be working without a hitch. Please enlighten me if I am missing some factor that makes doing this a problem or a bad idea in general.
If your using php pages in RSD name your pages in RSD mypagename.php. RSD will automatically place the .html on the end. Now point your links to mypagename.php.html. This way you can preview and work with the pages within RSD. After export use the HTML Editor to do a find replace of the .php.html to only .php. It doesn't allow actual php code to be previewed but at least you can make sure the html of the pages looks correct.
It's easy to overlook something you're not looking for.
This is a site I built for my work.(RSD)
This is a site I built for use in my job.(HTML Editor)
This is my personal site used for testing and as an easy way to share photos.(RLM imported to RSD)
Work with PHP pages within RSD
If your using php pages in RSD name your pages in RSD mypagename.php. RSD will automatically place the .html on the end. Now point your links to mypagename.php.html.
This could/should be so much easier, if only ... yep, let's post some feature requests.
Have something to add? We’d love to hear it!
You must have an account to participate. Please Sign In Here, then join the conversation.