Steve wrote:
Hi David,
My first suggestion would be not to edit the main.css file as this will be over-written every time you re-export your RLM project.
I tend to make template pages and customise them as I go. Unless there's a need for significant changes, I wouldn't be exporting this page again (or others following the same format

). I've already been significantly chastised for using RLM as my main editor and only using something else to add in the necessary PHP etc code
The edit itself isn't bad. I've got more php code and other stuff that goes into each page anyway, the edit is a simple copy and paste of a block.
But see below - if I can work out how to do it reliably I'll happily make one css file
I would create a custom.css file and put all your changes in there.
Could you explain how to do that? I had to abort another project that relies on CSS for menus because RLM craps all over the CSS. By that I mean RLM sets elements that aren't used in the RLM page, meaning the other CSS doesn't function as it should - the RLM stuff over-rides the custom stuff the page needs to work. Would love to know how to work CSS to what I want takes precedence (manually removing the extra RLM gunk resulted in an even worse mess!)
I would change what you have:
body > .row > [class*='coffee-span-'].header-container {
min-height: 500px;
[snip]
}
to this:
html {
background: url(../images/ddg_background.jpg) no-repeat center center fixed;
[..]
background-size: cover;
}
Now I'm lost

Where would that code go into place? In one of the css files or in the html? And where?
(I'm not a web designer, I just play one in the workplace sometimes!)
As for the centering issue I do not see the issue it looks fine to me.
Thanks. I see it most as I slide things around a bit. I've done the best I can without going to dozens of breakpoints (I can see at least another 5-6 I'd love to have in to have text/image sizes change but that makes the page waaaaaay to big code-wise!

)
As expected, for someone else looking at it (especially someone looking at it from a static page size) it's not an issue
I would include some kind of navigation/menu system on this website as you continue on. You may also want to have more distinction between your content area and your footer. Perhaps a different color background.
The menu bar was completely rejected by the customer. But the code is quick and easy to add in - I can see it coming once we get another page or two in there

(I still have to add something in to the contact page to take people back to the home page). It wasn't the style or anything, just an outright "no menu bar" - but then that was when we were looking at a single static page with no need for one. As things grow, it'll be needed.
As to the distinction, I may yet play with a bit of darkening or lightening the area that has the contact details inside. IIRC that's made of several different blocks though, some with only RH borders and so on. Of course, changing the border size might help as well.
Thanks for your help. Once I am sure where you want the suggested code to do I'll try it out

(the thing I like with the current setup is the displayed image sizes largely to the viewport size without scroll bars)
Take care,
David
david@kiwiscene.kiwi