none
DWT does not format table's correctly. It's something simple, I know... RRS feed

  • Question

  • I've read through the forums and seen a few DWT issues. I'm using EW Version 12.0.6211 and running it on a very basic web server, for a very basic website. Yet, the problem is displaying the navigation bar fonts. The fonts fail to stay consistent! (no doubt stupid over ride or something that I hit).

    I make sure I save all files after each change to DWT and associated linked pages in the navigation bar, etc.

    But something went awry and I can't figure it out. The side bar width control I think is part of the problem, though I can't get it to change size (width and height)

    site: www.rapidresponseconsulting.net

    thanks in advance for the help.

    Thursday, November 8, 2012 7:14 PM

Answers

  • Doug, are you actually doing what I told you to do? I don't think that you are, because if you did, your issue would be resolved. Let's step through this ONE step at a time.

    1. Double-click the "style3.css" file in your "styles" folder (in the Folder List) to open it in EW

    2. At the bottom of that file, add the following style definition, exactly as given (copy and paste, if you wish):

    #navigation {
       font-family:"Trebuchet MS", Arial, Verdana, sans-serif;
       font-size: .8em;
       color:black;
    }

    3. Save that CSS file. Now, as you follow the rest of these instructions, you will see each page begin to display the horizontal menu as defined in that style above.

    4. In the index.htm file, in line 12 and again in line 22, delete both definitions of .style2.

    5. In the about-us.htm file, in line 11 and again in line 52, delete both definitions of .style2.

    6. In the brochure.htm file, in line 2 and again in line 12, delete both definitions of .style2.

    7. In the services.htm file, in line 2 and again in line 12, delete both definitions of .style2.

    8. In the client.htm file, in line 11 and again in line 42, delete both definitions of .style2.

    9. In the faq.htm file, in line 11 and again in line 23, delete both definitions of .style2.

    10. In the contact.htm file, in line 11 and again in line 24, delete both definitions of .style2.

    Now, if you have followed these directions exactly, you will be able to click through every page in your site, and all of them will have the same exact font characteristics in the #navigation div, your menu bar. Report back if you have any problems.

    cheers,
    scott


    Please remember to "Mark as Answer" the responses that resolved your issue. It is common courtesy to recognize those who have helped you, and it also makes it easier for visitors to find the resolution later.

    • Marked as answer by Doug Hanchard Friday, November 9, 2012 12:37 AM
    Thursday, November 8, 2012 11:28 PM

All replies

  • First, thank you for providing a link. Unfortunately, it yields a "connection to the server was reset" error when attempting to load it. Is there a typo somewhere?

    cheers,
    scott


    Please remember to "Mark as Answer" the responses that resolved your issue. It is common courtesy to recognize those who have helped you, and it also makes it easier for visitors to find the resolution later.

    Thursday, November 8, 2012 7:31 PM
  • Can you  please try again to connect to the site.

    thanks

    Thursday, November 8, 2012 8:13 PM
  • Heh, heh... ;-)

    The answer is simple. You're setting your font family and size in each page. Set them once, in your external style sheet (style3.css) and do not override in each page's local embedded CSS, which always overrides same-specificity rules in external style sheets.

    BTW, I notice that you appear to be using the formatting toolbar to style page elements. Don't do that. It leads to the kind of thing you're seeing now, and to anonymous auto-styles such as "style2," "style3," etc. For elements common to all pages, such as your top nav, footer, etc., create the style once, in your external style sheet, and give it an appropriate classname (e.g. .topnavtext, .footertext, etc.). That way, you'll know what it is when you read it (what does "style3" control?), and if you decide to change it in the future, you make the change in one place and it is reflected throughout the site.

    Also, you are defining a font-family as "Trebuchet MS." That is not a font-family, it is a font, and if the visitor doesn't have it (like perhaps on a Mac or Linux machine), the browser will sub whatever IT decides to show. EW offers a number of "Web-safe" font families (google "web-safe fonts") to choose from, and you can also create your own, if you wish.

    cheers,
    scott


    Please remember to "Mark as Answer" the responses that resolved your issue. It is common courtesy to recognize those who have helped you, and it also makes it easier for visitors to find the resolution later.

    • Edited by paladyn Thursday, November 8, 2012 8:50 PM
    Thursday, November 8, 2012 8:29 PM
  • So just clear all the font settings in each page (manually) and let the DWT 'rebuild' the pages?

    Thanks,

    Doug

    Thursday, November 8, 2012 8:56 PM
  • Since the local styling for each page is in an editable region ("doctitle"), changes made there in the DWT do NOT propagate to all attached pages. You will have to visit each page to delete the embedded local styles

    Create a style in your external style sheet (style3.css) like this...

    #navigation {
       font-family:"Trebuchet MS", Arial, Verdana, sans-serif;
       font-size: .8em;
       color:black;
    /* any other styles you need for that div go here */
    }

    That will apply those styles to the "navigation" div in all pages. Now, in each page, delete any styles that apply to that div, which, just looking at your source code, would seem to be ".style2."

    You should also find where you are using "style3," "style4," etc. and move them to the external stylesheet as well, renaming them to reflect what they are used for, otherwise you will end up with similar issues in the future. Some you can simply delete, such as "style3," and "style4," on your home page, which are not used anywhere on that page. Style5 is applied to an h3 element, and in the interest of site uniformity, headings should be defined the same for all page. Move that to the external style sheet and use the proper selector, like so...

    h3 {
       font-family:"Trebuchet MS", Arial, Verdana, sans-serif;
       font-weight: normal;
       font-size: .8em;
    }

    That will apply the same style to all h3 headings in the site. All elements which are styled the same from page to page should be styled once, and once only, in the external style sheet, and should have names reflective of their purpose.

    cheers,
    scott


    Please remember to "Mark as Answer" the responses that resolved your issue. It is common courtesy to recognize those who have helped you, and it also makes it easier for visitors to find the resolution later.

    • Edited by paladyn Thursday, November 8, 2012 9:25 PM
    • Proposed as answer by fcphdJim Thursday, November 8, 2012 11:05 PM
    Thursday, November 8, 2012 9:09 PM
  • I think I follow...

    Most appreciated. Obviously, at one point, I over rode what the DWT template suggested for each CSS style page and wrecked it.

    thanks for helping.

    Thursday, November 8, 2012 9:17 PM
  • If you don't mind, please mark the response(s) which resolved your issue as the answer. That will help others to find the resolution when searching the forum later.Thank you.

    cheers,
    scott


    Please remember to "Mark as Answer" the responses that resolved your issue. It is common courtesy to recognize those who have helped you, and it also makes it easier for visitors to find the resolution later.

    Thursday, November 8, 2012 9:28 PM
  • hrmmm my brain seems to have gone into vapour lock.

    Followed your suggestions but it's not working. Example, faq.htm is not changing.

    the index.htm page is way I want the navigation fonts, but it's not changing to the css style2 version.

    :(

    Thanks for trying to help though!

    Thursday, November 8, 2012 9:46 PM
  • What really frustrates me is that at one time, the navigation fonts were PERFECT...

    and then I went to tinker and ...

    Thursday, November 8, 2012 9:48 PM
  • Think what I should do is start from scratch and repopulate all my data.

    Clearly, I can't get it to work.

    thanks for all the ideas.

    • Marked as answer by Doug Hanchard Thursday, November 8, 2012 10:07 PM
    • Unmarked as answer by Doug Hanchard Friday, November 9, 2012 12:32 AM
    Thursday, November 8, 2012 10:07 PM
  • Doug, are you actually doing what I told you to do? I don't think that you are, because if you did, your issue would be resolved. Let's step through this ONE step at a time.

    1. Double-click the "style3.css" file in your "styles" folder (in the Folder List) to open it in EW

    2. At the bottom of that file, add the following style definition, exactly as given (copy and paste, if you wish):

    #navigation {
       font-family:"Trebuchet MS", Arial, Verdana, sans-serif;
       font-size: .8em;
       color:black;
    }

    3. Save that CSS file. Now, as you follow the rest of these instructions, you will see each page begin to display the horizontal menu as defined in that style above.

    4. In the index.htm file, in line 12 and again in line 22, delete both definitions of .style2.

    5. In the about-us.htm file, in line 11 and again in line 52, delete both definitions of .style2.

    6. In the brochure.htm file, in line 2 and again in line 12, delete both definitions of .style2.

    7. In the services.htm file, in line 2 and again in line 12, delete both definitions of .style2.

    8. In the client.htm file, in line 11 and again in line 42, delete both definitions of .style2.

    9. In the faq.htm file, in line 11 and again in line 23, delete both definitions of .style2.

    10. In the contact.htm file, in line 11 and again in line 24, delete both definitions of .style2.

    Now, if you have followed these directions exactly, you will be able to click through every page in your site, and all of them will have the same exact font characteristics in the #navigation div, your menu bar. Report back if you have any problems.

    cheers,
    scott


    Please remember to "Mark as Answer" the responses that resolved your issue. It is common courtesy to recognize those who have helped you, and it also makes it easier for visitors to find the resolution later.

    • Marked as answer by Doug Hanchard Friday, November 9, 2012 12:37 AM
    Thursday, November 8, 2012 11:28 PM
  • I tried posting earlier, but the forum hung up.

    Doug:

    You should not mark your last post as the Answer, because it isn't the answer. It may be what you want to do, but it is NOT the solution to your problem. Scott has the solution and you should mark HIS post as the Answer (for people who come to this thread later).

    Your problem is not going to be fixed by "repopulating all my data". There's nothing wrong with your data (the content). Your problem--your ONLY problem--is the styles that Scott told you to delete. And he provided a replacement style for the external style sheet. Make your life easier; just do what he says.

    Also, to add on to what he said about the web-safe fonts...Your logo will only be seen in the Magneto font by people who are running Microsoft Office. That font does not exist on Apple computers, Andriod devices, Windows computers without Office, iPads, etc. All of those computers will substitute their own default browser font--Times New Roman or Arial/Helvetica  are most probable. A stylized font like that doesn't really have a fall-back font to use as a font family. If that's what you really use for your logo, you should make it a graphic. 


    How many SEO experts does it take to change a lightbulb lightbulbs buy light bulbs neon lights sex porn.

    Friday, November 9, 2012 12:02 AM
  • Not only  is my capability of using Expressions broken, but so is using the help group and staying within the rules.

    I ran the CSS reports tool and it found a whole pile of things wrong. Just about to go ape, but then, I never was all that patient.

    Scott's step by step did fix the font issue in Style2. Course, now I've done something else wrong (navigation bar height now seems to be mucked up.. good grief, I feel like a elephant too close to a keyboard!)..

    As for font, I do indeed want to keep that font as my logo. Now you really asking me to blow up the webpage with making that whole thing a graphic! I think you guys are just trying to keep a day and night time job around here :)

    Friday, November 9, 2012 12:36 AM
  • Here's what CSS report found wrong in the services.htm page.

    <p class="MsoNormal">

    <span style="line-height:150%;

    mso-bidi-font-family; Arial; color:black" class=style2">

    Friday, November 9, 2012 12:40 AM
  • Still won't work on the web server....

    But navigation table (now, post Scott's instructions) shows correctly in local folder preview for all pages.

    Would the master.dwt file be screwing it up?

    <div id="navigation">
      <ul>
       <li class="style2"><a href="index.htm">Home</a></li>
       <span class="style2">
       <li><a href="about_me/about_us.htm">About</a></li>
       <li><a href="products/brochure.htm">Literature</a></li>
       <li><a href="services/services.htm">Services</a></li>
       <li><a href="client/client.htm">Experience</a></li>
       <li><a href="faq/faq.htm">FAQ</a></li>
       <li><a href="contact/contact.htm">Contact</a></li></span>
      </ul>
     </div>


    Friday, November 9, 2012 12:49 AM
  • I think you guys are just trying to keep a day and night time job around here :)

    Heh, heh... would that t'were. ;-)

    Unfortunately, we don't get a nickel for the time we put in here. We are not MS employees, simply other users of EW, unpaid volunteers who come here to try to help other users. The only reward we get is the recognition "points" next to our names, which accrue when our responses help someone and they are marked as answer.

    Now, please relax and don't go off half-cocked, making changes without understanding what you are doing. That can end up causing far more trouble than it resolves. Here's what we ask—one thing at a time, please describe exactly what you're having a problem with, give us time to analyze your source code and CSS to determine the resolution, and we can give you instructions on how to fix it. Milling about smartly, making changes without understanding the consequences, will only dig you deeper, OK?

    Now, as to your problem with the live site ("Still won't work on the web server...."), if it works locally, have you published the changed files up to the server? Do this—click "Site|Publish Changed Files...", then wait until the publish is complete, then browse to your online site and, if necessary, press Ctrl-F5 to force-refresh your browser display.

    Belay that! I just went to your site, and it appears that you have published already, because the menu now displays in a uniform font size from page to page. Good, now, let's see what else we can fix... ;-)

    cheers,
    scott


    Please remember to "Mark as Answer" the responses that resolved your issue. It is common courtesy to recognize those who have helped you, and it also makes it easier for visitors to find the resolution later.

    • Edited by paladyn Friday, November 9, 2012 1:22 AM
    Friday, November 9, 2012 1:10 AM
  • LOL - you guys are as bad as me volunteering in disaster zones and not getting paid a dime.

    Okay - the files are now uploaded and loading, but as you will see, something is still wrong. The navigation bar now works with correct font, but now floats up and down in services.htm and contact.htm

    Go figure ! :)

    If I have to, how do I offer users, an alternative font(s) for my logo (magneto) and main content (Trebuchet).

    I really don't want to start with paintshop pro, figure out pixel wide and height..cuz you both know what's gonna happen me with making a graphic... LOL :)

    Them damn Apple people :)

    And just when I thought Adobe made sure Mac would have every font on the world loaded on their machines...

    thanks!

    Friday, November 9, 2012 1:20 AM
  • I should note, that I'm using Expressions Web from 2007 (version 12.x.x. blah blah blah) so it's not Expresions 3 or 4 ..I do have SP1 loaded. I just wanted to have a basic site for the 10 clients that I have an other volunteers that often use my site for references for disaster and crisis management.

    All my stuff is Microsoft (Office, Visio, etc.) and thus I wanted to stay in house - thus the use of Expression. While I did want to expand the site, for me, its probably too daunting, as I am finding Expressions clearly needs an expert group! darnit...

    I used to build websites for a living - when it was still html 1, 2 and even as far as 4.0. But as soon as CSS came along, my skills went out the "window"

    Friday, November 9, 2012 1:27 AM
  • BTW, I notice that that 0.8em fontsize is kinda small for your menu bar. If you open up style3.css again, then go to that #navigation style again (line #145, I believe), and change the font-size to 1.2em, like so...

    #navigation {
       font-family:"Trebuchet MS", Arial, Verdana, sans-serif;
       font-size: 1.2em;
       color:black;
    }

    ...then save the CSS file, you will see that all pages now show the menu bar in that new font size. Now, publish that file again, and the online site will update to the new size, as well. That is the very great advantage of keeping all of your styling for common elements in your external style sheet—you only need to make a change in one place to affect all pages uniformly. Much easier than having to touch each page in turn, and it avoids the scenario you had before of inconsistent display from page to page.

    cheers,
    scott


    Please remember to "Mark as Answer" the responses that resolved your issue. It is common courtesy to recognize those who have helped you, and it also makes it easier for visitors to find the resolution later.

    Friday, November 9, 2012 1:30 AM
  • Scott,

    Okay, fixed. I agree, it makes sense to have it a wee bit bigger.

    But the bar still floats if a user clicks on services.htm or contact.htm

    What causes that?

    thanks,

    Doug

    Friday, November 9, 2012 1:39 AM
  • Dunno. Let me take a look at the source code for those pages and I'll see what I can find...

    OK, looking at the markup and CSS, the only difference I can see is that on the Services page you have line-height for .style5 set to 150%. When I set that to 100% (or remove it altogether, which is the same thing), that extra space in the masthead goes away.

    Once again, this is an example where elements which are common to all pages, such as the masthead, should only be styled once, in the external style sheet, where they will be applied uniformly across all pages. Every time you change styling on a page-by-page basis, you run the chance of screwing something up, and if you don't understand HTML and CSS, it can be damned near impossible to find and fix, n'est-ce pas?  ;-)

    cheers,

    scott


    Please remember to "Mark as Answer" the responses that resolved your issue. It is common courtesy to recognize those who have helped you, and it also makes it easier for visitors to find the resolution later.

    • Edited by paladyn Friday, November 9, 2012 2:19 AM
    Friday, November 9, 2012 2:03 AM
  • If I have to, how do I offer users, an alternative font(s) for my logo (magneto) and main content (Trebuchet).

    I really don't want to start with paintshop pro, figure out pixel wide and height..cuz you both know what's gonna happen me with making a graphic... LOL :)

    Since your masthead is fixed in size, you could always just screengrab it and replace it with that, like this

    If you care about SEO (probably not, from your description of the site's rationale) be sure you add a title attribute the same as that h3, and replace the h1 and h3 somewhere in your body copy. Note that the forum software "shrinks to fit" that image above. Yours can be full size to fit the space needed.

    Alternatively, you can use an advanced @font-face technique to see if you can find an equivalent Webfont to the Magneto font you're using, but that may be more than you want to do. If you're not making money off the site, I frankly wouldn't sweat it.  ;-)

    Them damn Apple people :)

    And just when I thought Adobe made sure Mac would have every font on the world loaded on their machines...

    Actually, Apple makes Macs, not Adobe, and the fonts on the two different OSes (Windows and OSX) are determined by Microsoft and Apple. Adobe has nothing to do with it. Just sayin'...  ;-)

    thanks!

    You're welcome. ;-)

    cheers,
    scott


    Please remember to "Mark as Answer" the responses that resolved your issue. It is common courtesy to recognize those who have helped you, and it also makes it easier for visitors to find the resolution later.

    Friday, November 9, 2012 2:44 AM
  • For the fonts: look what Scott gave you: font-family:"Trebuchet MS", Arial, Verdana, sans-serif;

    That tells the visitor's browser to use MS Trebuchet if it has that font installed. If it doesn't, use Arial (a sort of similar-sans-serif font of a similar weight and letter width). Failing that (Apple users), use the similar and common sans-serif Verdana. And for all others, use your default sans-serif font, whatever that is (possibly Helvetica on Apples). You would not mix serif and sans-serif fonts in a font family.

    The problem with Magneto is that there is no fallback font that kind of looks just like Magneto. So you are screwed.

    All you have to do is dust off PaintShop Pro, open masthead_image.jpg, and pop your company name on top of it in Magneto, save it with the same file name and take the text out of your header and upload the changed pages and image file to the server. No changes needed to the CSS at all.

    But...first save a blank copy of that wave photo just in case you need it again, and for the best sharpness of the logo lettering, save the image as a PNG file instead of JPG. If you do that (change masthead_image.jpg to masthead_image.png), you will have to edit the CSS to change the image name and upload that too. Do not put Your global advisor for ICT-S resources in that picture; the font is too small to be as clear as you want it when it is saved as a graphic. The way it is now is better; just leave it as it is, in the code, overlaying yhe background picture.

    Three other considerations:

    1. font sizes of small, x-large, medium, etc., are interpreted differently by different browsers. You have no idea what your visitor is really seeing--it depends on what browser they use. Replace them with real sizes (in ems).

    B. That is the skinniest site I have seen in ages. You are wasting a LOT of screen real estate and, worse, you're shoving a lot of your advertising copy off the bottom of the page--out of site of the visitor unless they work to see it. That's particularly unfortunate on the Experience page, where most of your experience is "below the fold" in newspaper parlance. Making the site wider is a piece of cake, requiring you only to adjust the width once in the style3.css sheet and creating a new, wider masthead graphic. 960px to 980 px is the most common modern width, and it displays well on virtually any monitor.

    III. I have no idea what page I'm on as I move about the site. Each page needs either a large title below the navigation bar or, at least, an indicator in your navigation menu as to what page the visitor is on (reverse highlight, as in the hover would do fine).

    The above is just a road map of little projects that will keep you occupied through the long winter ahead. But before you do anything, make backups of the site, make them often. Because when you screw up--and you will--you can throw away the latest mess and start again.

    Have fun.


    How many SEO experts does it take to change a lightbulb lightbulbs buy light bulbs neon lights sex porn.

    Friday, November 9, 2012 3:00 AM
  • I did eliminate the 150% tag, but it hasn't changed anything, I dunno why. If you click on the contact.htm page, the damned site moves side to side, not up and down... what the heck...

    As for your other ideas, I thought of doing a graphic as suggested earlier, but I feared future challenges. Such as, what if I wanted to increase the width of the site (looks too narrow at the moment), I could do that in the future when I figure out how, but then the graphic would be all screwed up - and thus, I just said to myself - jeez, leave it alone!

    As for Apple and Adobe, it's a long story to way back in the day. I know the company's in question rather well. When Apple became, de'facto the platform for graphics design, Corel Draw had the lions share of the market, and in concert with Adobe, realzing visual tools were going to be one of the big pieces, focused heaviliy on Mac's for fonts, which how Adobe got its start. For years, it was a mortal lock on Adobe fonts and unique typesets and Corel Draw graphics software. And then the roof caved in... (lets not go there...)

    I had just assumed (bad bad bad I know), that if Microsoft had it, hell, Apple / Adobe probably had it the decade before ... :-) like you...just sayin. This is way back in 1979 to '85 before the web.

    I promise to stop now, because I wanted to think about adding a private log-in section for files and ...


    Friday, November 9, 2012 3:09 AM
  • Bill,

    Everyone one of your ideas is solid. My problem is time and frankly, avoiding making any more mistakes :)

    Would you rather have me helping Hurricane Sandy NGO's sort out some of their logistics issues, supporting a few communities or making my  website (possibly) worse. But you have got the right perspective for sure.

    I bet Sandy's aftermath and a few more future disasters are gonna keep me busy this winter (though it would be nice if it was not true).

    And that's another section I want to add to the site, but not much chance anytime soon, since I don't run a PHP server with all the data we currently collect, which I can leverage it easily at the moment elsewhere, but would be nice to run 'locally'.

    Thanks Bill !

    my best,

    Doug

    Friday, November 9, 2012 3:21 AM
  • Bill,

    Just an fyi - I increased to 960. Amazingly, I managed to change graphics and body's and columns to match - without imploding the site. Much better. Thanks

    Friday, November 9, 2012 4:05 AM
  • I have a friend who works with FEMA helping communities with the federal paperwork to pay for the infrastructure repairs, so I appreciate how busy you must be.

    Hurricane Sandy hit us dead on. The weakening eye went right over Philadelphia, but the city proper was spared anything more than a couple hundred downed trees. No power loss, nothing. The suburbs fared much worse than us and, of course, the northern edge of the storm is what did the real damage to upper Jersey and NYC.

    It was a tense few days before, and the day it hit was "interesting" (especially since the peak winds started at night), but we were saved because I had prepared by going to the store and stocking up on eggs and milk and bread. Because, as we all know, only French toast can save us.

    Get everyone taken care of, then come back. We'll be here.


    How many SEO experts does it take to change a lightbulb lightbulbs buy light bulbs neon lights sex porn.

    Friday, November 9, 2012 4:13 AM
  • Well, suit yourself, of course. Here's the thing, though—a template, a DWT, is basically a framework. As long as intend to use it as is, you can pretty much plug in your content and go. However, as soon as you start making changes, you need to start learning.

    For one thing, you need to understand basic site structure, which this issue has made pretty clear you do not. In a templated site, all changes to common areas should be made in the template itself, i.e., the DWT file, and in the external CSS file common to all pages. You are having these issues of inconsistent display from page to page because you have made edits to individual pages which should not have been made there. And you cannot troubleshoot them yourself because you do not understand HTML and CSS enough to be able to analyze the markup and CSS that is the actual page.

    There are many free resources available, listed in the Learning Resources and Reference Sites section of the Forum FAQs and Guidelines - Start Here. Note in particular the free w3schools courses available at http://w3schools.com/html/ and http://w3schools.com/css/. Also, download and view, then work through (using the assets in the accompanying zip file) Cheryl's excellent "Build a Basic Web Site" video tutorial, at http://by-expression.com/post/2009/09/22/Basic-Website-Tutorial.aspx.

    You can ignore this advice, of course, but you will find yourself adrift afloat the mist, digging yourself ever deeper into trouble the more you try to alter the site from the initial template. Your choice, and good luck!

    cheers,
    scott


    Please remember to "Mark as Answer" the responses that resolved your issue. It is common courtesy to recognize those who have helped you, and it also makes it easier for visitors to find the resolution later.

    Friday, November 9, 2012 4:20 AM
  • Scott - Your points are all valid and true. I'm ancient to be sure and that's just a reality that I hate to face. I'm one of those dinosaurs that just wants things 'fixed'. Those links will come in handy - thanks. I just thought it would be 'easier' with Expressions. -would buying 4.0 help? Reality is, I don't know modern html and CSS, but that said that already. oh well, so much for shortcuts like notepad and just tinkering...

    Bill - paperwork is 65% of the battle at the FEMA level. But even the operators in the field are overwhelmed with data and in your face demands of action demands. Housing alone is turning out to be a critical issue, which is being mapped, plotted and distributed as fast as possible. (try dealing with the back log of postal mail that can't be delivered, yet people need it for obvious reasons, like pension cheques) and people are being relocated.

    I will work on the elements you suggest. Working on this website is a stress reliever (what a pile of crap that is! - lol) but with Scott's links and the ideas, it should work out.

    Thanks to both of you. Just this thread alone has improved the look and eliminated a lot of errors.

    Doug

    Friday, November 9, 2012 4:47 AM
  • I just thought it would be 'easier' with Expressions. -would buying 4.0 help?

    Nah, not really. Don't get me wrong, EW4 SP2 has a lot of productivity enhancements for professional developers. But, it still expects the user to bring to the table a certain level of knowledge of HTML and CSS. Frankly, I can work almost as well in EW2 as in EW4, just not quite as productively (output per unit time). You would actually gain more by investing time in those learning resources than money in EW4.

    cheers,
    scott


    Please remember to "Mark as Answer" the responses that resolved your issue. It is common courtesy to recognize those who have helped you, and it also makes it easier for visitors to find the resolution later.

    Friday, November 9, 2012 4:58 AM
  • Yay. The wider site looks much better.

    Now, in all your free time...;-)

    Remove the Justify command from the style sheet. Browsers do a lousy job of adjusting interword spacing like that. It can look awkward. Plus, people read justified text more slowly and--very important to you--they remember less of what they read. Bad for advertising. Because there are no landmarks (the ragged right margin) for our eyes to fix on as we scan back and forth, justified text is hard to read for any length of time (it's okay for a pull quote, but not much more).

    I'd make the left column wider than the right (as it was before); it's a little too symmetrical, and different widths imply a primary and secondary set of information in each.

    See now--isn't this easy?


    How many SEO experts does it take to change a lightbulb lightbulbs buy light bulbs neon lights sex porn.

    Friday, November 9, 2012 5:34 AM
  • I've scanned this thread quickly, so I may have missed some replies, but in reply to:

    "Here's what CSS report found wrong in the services.htm page.

    ...class="MsoNormal" ... mso-bidi-font-family"

    Those are from pasting from Word (or otherwised generated by an Office program), and mean absolutely nothing on the web.  Delete all the references to class="MsoNormal" and "mso-bidi-"  (font-family is correct - assuming you have an actual family, more than one).

    Now as for "If you click on the contact.htm page, the damned site moves side to side, not up and down... what the heck..."

    That's trivial:  Look at the right hand scrollbar.  Contact is short enough it doesn't trigger one.  Voila: the page doesn't leave space for it, so it "moves over".

    And as for "But the bar still floats if a user clicks on services.htm or contact.htm "

    Your published site still has different style5 definitions on the different pages.  Create one style, on the main style shee, not different styles in he individual pages.

    Friday, November 9, 2012 8:21 AM
  • Bill,

    I understand your "justify' comment. I'm old school.  If there are two columns, I like newspaper style borders. When I look at the site on a small and conventional 15" monitor, it makes it easier to read in my opinion. Not all of my users have 16:9 or Wide screen, though I wish it were so. I was also thinking of mobile users, in which I find on small tablets, smart phones, etc, that when an article or content is put into justify, it does make it easier to read. It's for this reason I also split the columns equally, so that when a users reads the material and has to zoom, (say a Blackberry Bold), I find it easier to read the column. Perhaps I'm wrong, but that's why I decided on that format after the width extension of the site.

    Kathy - thanks every much to indicating that Style5 seems to be still all over the site. as I was going through each page, I tried to make sure that all manually entered styles were deleted, using the 'remove style' command. When I run CSS Reports, it shows up 32 errors, most of which are "unused style". I wish EW2 had an 'correct' all feature! :)

    I did as Bill suggested, make a back up copy of my files and have begun to tinker on a test version to see if I can embedd a photo album, to be placed on the index.htm lower right hand corner of the sidebar column, from my Google Plus's website to have enabled a slide show, but that's not something that seems to be possible just yet :) I can link to a public site, but not create an auto slide show.

    Based on what I'm hearing from you folks, this must be created using a style sheet, and not created in the actual index.htm page :)

    Friday, November 9, 2012 9:10 PM
  • Based on what I'm hearing from you folks, this must be created using a style sheet, and not created in the actual index.htm page :)

    No, content is not created in a style sheet; it is styled there. Actually, there are several ways to do what you want to do (add a slideshow). The most straightforward is probably to use an iframe. They're bad for SEO, since the content isn't spidered, but fine for multimedia content, since that isn't indexed anyway. In any case, CSS (i.e., style sheets) are for defining the presentation of content, not for creating/including content. HTML markup is used for creating and structuring content.

    As for your unused styles, that's something that you can simply eliminate completely. Just delete those style declarations; since they're not used, they'll not be missed. If you recall, I pointed out that the classes .style3 and .style4 in index.htm were not used anywhere in the page, and they can simply be deleted in that page's embedded styles in the <head> section, as can any others reported as unused in your CSS report.

    To resolve the individual differences between your pages, you must eliminate those embedded styles which remain. As noted, style5 is define in several pages. Find where that style is used (any element which has "class='style5'" as part of its declaration), and why. If there really is a general rule you want to apply to those elements, give it a meaningful name.

    Let's look at your index.htm file. In your embedded CSS, you have ".style6 {font-size: em.8;}". First of all, that declaration is meaningless, since the unit must follow the quantity in CSS, so it should be ".style6 {font-size: .8em;}". The CSS parser ignores anything that it doesn't understand, so that line is completely ignored. Then, further down, you redefine that style thus: ".style6 {text-align: justify;}". OK, fine, except that, first, the name gives no clue as to what it is for, and second, it is a rule which applies to multiple pages. Therefore, you should rename it and move it to your external style sheet. You could call it "justified," or, given where it is used, call it "columnText." Whatever, you create it in the external style sheet, like so...

    .columnText {
       font-family:"Trebuchet MS", Arial, Verdana, sans-serif;
       font-size: 1.0em;
       color:black;
       text-align: justify;
    }

    Now, wherever in the site you have justified column text, you assign that class. Using our example of the index page, you currently have this...

    <div class="style6">

    which contains your left and right columns. You would change that to

    <div class="columnText ">

    Now you can completely eliminate .style6 from your page-embedded CSS. Furthermore, if you ever decide to modify that text's characteristics—make it smaller, larger, change fonts, whatever—you make the change in one location and it is enforced throughout the site, which promotes site consistency, and prevents the kind of page-to-page differences you're seeing now.

    On that same page, we've already discussed the problem with style2. That is used on all menus, so could be renamed "menuText" and moved to the external style sheet. As mentioned, style3 and style4 are used not at all on that page, and can be deleted whole cloth, while style5 is used for a heading level 3, so should be moved to the external sheet and changed to...

    h3 {
        font-family: "Trebuchet MS";
        font-weight: normal; /* not needed; normal is the default */
        font-size: .8em;
    }

    And that, my friend, completely eliminates any need for any local styles on that page, and your embedded style section can be eliminated altogether, although I would simply empty it and leave the style block there, in case you ever actually do need some page-local styling (like, for example, for a slide show... ;-). Do the same sort of analysis for the other pages in the site, and by the time you're finished, you will find your page-to-page variations have vanished!

    ...make a back up copy of my files and have begun to tinker on a test version to see if I can embedd a photo album...

    Yes, by all means, work on a copy. But, no, "tinker" is not the right approach to modifying a template-based site to include content and structure not included in the original template. If you don't know what you're doing, and pardon me, Doug, but you don't, you can easily bollox things up even worse than you have done so far. For example, unless you want that slide show to appear on all pages, you need to plan ahead and create an editable region in the appropriate location, so that you have a place to work on the page where you want the slideshow to go. You must do this in the template file, then let the change propagate to attached files, else you cannot make the desired changes to the target file.

    There are other issues to take into account, as well, but the point I'm trying to make is that learning HTML and CSS is not amenable to a "tinkering" approach, at least, not on an existing, live site which is structured and driven by a template, and for which all changes must take into account that overall imposed structure. You really, really want to take some time to work with those resources I described earlier before attempting to ring structural changes on your site's pages. Seriously...

    cheers,
    scott


    Please remember to "Mark as Answer" the responses that resolved your issue. It is common courtesy to recognize those who have helped you, and it also makes it easier for visitors to find the resolution later.

    Friday, November 9, 2012 10:33 PM
  • Scott,

    You are becoming dangerous. As are the rest of you. Essentially you want me to become, you know, actually somewhat good at using EW. As if I don't have enough hobbies as it is. :-)

    I get the content of your recommendations. And I sort of knew some of that already. Perhaps I wasn't quite stating it correctly as you have illustrated. Yes, I understand that content is not built within a style sheet or layout sheet. But the presentation of all your pages can be powered by such techniques, in this case, in the world of CSS with style sheets, templates and layout stuff.

    How I wish software engineers would go back to basics of html 2 - LOL. But that's silly I realize. CSS offers some incredible power for small websites such as mine. There are limitations I'm sure, but for me, I don't see any that come to mind. You are correct in the assumption that I want to make sure that if I do add slideshow, that it does not post across all the different content pages. Thus, yes, it has to have its own template for the areas it should be visibile and not. I agree, planning (like anything in the tech world) requires advanced planning (design architecture in a sense) before changes can or should be made. I'm just an old man trying to make something simple and, yes, get away with it, though I shouldn't... bolloxing it up would be an understatement :)

    As a side note, it's interesting to see how Microsoft (and others) have designed Expressions as an application to help 'solve' some of the complex areas of building a website. Some of it is straight forward logic, while other components do seem to require a leap of faith. Examples are the syllabus and how each set of elements can be put together with specific rules and specifications. Just look at the browser wars and intepertations as all of you have pointed out, are not always compatible or equal. And for some of us (like old men such as myself), the transition to modern application development is just 'harder' than what it used to be. Thus the rules have changed and our interpertation of them is not difficult, though truthfully, that it is - we just sometimes tend to ignore such rules (and we wonder why the world is messed up...)

    Let me give you one small example of inteperation of how this has unfolded. When we create a file of content, say a word document and save it, we have options, such as the native extention or other format, such as PDF or even plain text. What we know then, is that the file is now capable of being read in other formats other than what it was created in (MS Word) and off the file goes to someone else to be read in their appropriate application. That's something that's easy to comprehend.

    But then we want to go create a CSS template or Style - and save that. What comes immediately to mind (even though it's dead WRONG) is that such files being saved are going to mess up the original and not be able to be found again. The instructions and help guides within Expression do not explicity explain what actually occurs or how the saved files are reusuable, where to find, organize and use them over and over again or modify them,etc.. Perhaps this small example is not a good illustration, but I hope it gives you an idea of some of the gaps in the concepts of what are sometimes considered complex, but are not. Let's put this into further context. When a user opens up Expressions, a plethora of windows open up with options user can choose various tools and settings.You get your website's folders, below that (by default) Tag properties, and across to the other side, there's your toolbox, manage styles, CSS styles, Selected preview, etc. And then there's your main ribbon bar(s) above. Holy cannolis, it's harder to navigate than a 1970's knobs and dials Boeing B-707 (which I can fly) and that's saying something! ..and you want me to save a style. Great!!! but where am I gonna find it later, manipulate it, modify it and .. it's not 'intiutive' so to speak.

    Now, before you go onto "get with the program" or "well, that's why you need to take some courses", etc., all I am trying to illustrate, is that for some, the more options available, the more challenging the application becomes to navigate, comprehend and use with confident for an ol guy like me. I'm willing to learn, providing it doesn't take 2 years to accomplish. I'm one of those guys that expected my Jet Pack 5 years ago because I thought technology and evolution of next generation stuff would be here by now. Make things simple to create, not more complex! :) Saving a style or layout or template is cool, but there is that fear factor - am I gonna screw up how "I" use EW the next time around.

    Given all that, I think I've done pretty good for an ol salt. With the help of you good folks, it has made it a great experience to immerse myself back into the world of building a simple and small website. It's not straight forward anymore, but I can see how EW can be an amazingly powerful tool and EW 3 and 4 probably have some of those "jet pack" capabilities, for those that understand them and do this for a living everyday.

    Thanks for the great comments and ideas. The 'net is a cool place and always will be. This is one of many examples why.

    Doug

    Friday, November 9, 2012 11:15 PM
  • Get in line, Doug. You'll get your jet pack after I get the hover car they promised me in the '60s, and not a minute before!

    Yes, the Help in EW doesn't cover the basic concepts of website development; it only covers how to do things in EW. And that's probably appropriate for a Help file. Just work through the links Scott pointed you to and Cheryl's video. That should allow you to take the training wheels off is very short order. 


    How many SEO experts does it take to change a lightbulb lightbulbs buy light bulbs neon lights sex porn.

    Saturday, November 10, 2012 12:09 AM
  • BTW, you've got some very basic issues you should deal with immediately, and they don't take overmuch skill to resolve. For example, your page titles. The home page is OK, as is the About page, although I would spell out RRC, instead of abbreviating it. However, your Literature page's title proclaims it to be "RRC Services," while your Experience page is apparently "RRC Client Services." Even better, your FAQ page proudly declares that it is the "Rapid Response Consultine Home Page," being simultaneously misspelled and misidentified.

    Visit the site, then watch the browser's title bar as you click through the pages. Little things like that don't seem major, but they're kinda sloppy and they go straight to your site's credibility. Might want to look into correcting them. Just sayin'... ;-)

    cheers,
    scott


    Please remember to "Mark as Answer" the responses that resolved your issue. It is common courtesy to recognize those who have helped you, and it also makes it easier for visitors to find the resolution later.

    • Edited by paladyn Saturday, November 10, 2012 3:59 AM
    Saturday, November 10, 2012 3:44 AM
  • Take Verdana out of the list. Its x/y ratio is so much greater than any of the others it will likely screw things up if substituted for Trebuchet MS"

    I'd suggest:

    font-family:"Trebuchet MS", Tahoma, Helvetica, , sans-serif;

    Arial is almost always the default sans-serif font. Tahoma will be on any computer with MS Office on it (Mac or PC) or Windows, and Helvetica is generally considered to be a more attractive font than Arial and is a Mac system font.


    Free Expression Web Tutorials
    For an Expression Web forum with without the posting issues try expressionwebforum.com

    Saturday, November 10, 2012 4:29 AM
  • Doug,

    Justify may look good on your monitor with your settings but in my experience on the web it is something that doesn't flow well cross platform.

    The whole concept here is separation of content from presentation. Use stylesheets to set the presentation and HTML for the content.


    Free Expression Web Tutorials
    For an Expression Web forum with without the posting issues try expressionwebforum.com


    Saturday, November 10, 2012 4:32 AM
  • This is a tough crowd ! Feel like I am before a review board! lol :)

    Some fixes now done - thank you all. I'm still sticking to my guns on justify, especially after looking at the site on a tablet (Samsung running andriod with Chrome on a 7" tablet and my BB Bold) and smart phone. And the titles are fixed.

    I've also updated the font selection. The navigation bar no longer floats up and down, though I don't know what I did that fixed it. There's still some extra style sheets floating around, but they are listed in the uneditible area in each page.

    I'm gonna leave the idea of a new style / template for a iframe slideshow for now, too complicated for me, as I have other work to (sigh) to get back to, which will help New Jersey and New York.

    thanks to everyone for their help, it's great stuff! Though I feel I've flunked a few exams, it's been worth it :)

    Doug


    Saturday, November 10, 2012 6:32 AM
  • In the tough crowd category:  I've got to argue with you about the text justification.  Your site is hugely jarring to my eyes with all those changes in spacing between words.  Heachache-making when there's a lot of text on the page.  If you want a nice sharp column edge, you don't need to do it with the words.  You could do it with a thin border line, for example.
    Saturday, November 10, 2012 3:42 PM
  • Well, you can stick to your guns; it's your site.

    But--it doesn't matter what you like. What matters is what makes your visitors stay and read and comprehend (and then use your services). And all research indicates that justified text effects readability and reader comprehension. It hurts your advertising efforts, which is what your website really is.

    The exception to the justification rule is for very narrow print columns (that the eye doesn't have to scan side to side--like newspapers). Further, print justification is always done in combination with auto-hyphenation, which the web can't do. That minimizes (but doesn't eliminate) the distraction of oddly spaced words. And in print, unlike the web, the user can't change the size of the text (zoom, text-only). Many users will come to your site with the text (but not the whole page) zoomed to any number of sizes (usually larger on high-res interfaces). You have no control over that.

    There is a reason that nobody uses justified text. Look at any major site on the web--NPR, CNN, NBCNews, Philly.com, New York Times, PCMag, PCWorld, Huffington Post, etc.; they are all ragged right. That's not an accident.

    A few links about this are here... http://blog.newmediadevelopment.net/2010/02/justifying-nonjustified-text.html . And the excellent www.alistapart.com has numerous articles on web typography (and all things web).

    And quick--before anyone notices--it's role-play, not roll play.  


    How many SEO experts does it take to change a lightbulb lightbulbs buy light bulbs neon lights sex porn.


    • Edited by Bill Pearson Saturday, November 10, 2012 6:03 PM
    Saturday, November 10, 2012 5:29 PM
  • I suspect that folks uisng 7" android tables will not be the majority of folks visiting your website. If you want to give that demographic a justified display go with media queries. Yep, that's right, you'd really need to learn stuff to do that. Alternatively design for the majority of your site visitors (you can check your website stats to determine what that is if you want.) Which will most likely be folks using a regular browser on a mainstream operating system typically Windows but in a few cases Macs. Either of which will have more in common with each other than with a 7" android tablet.

    I'm with Kathy that justify looking at your site in a real web browser (Firefox on Win 7 in this case) is not attractive and is harder to read with the big gaps between words in some of the lines. There is a good reason you don't see much justified text on the screen. Many things that work really well in print such as serif body type (Times New Roman after all came from typeface) due to the typically low resolution of a computer screen. Macs started out as 72ppi per inch, Windows at 96ppi but now with some of the really high resolution screens you can end up with 178-238ppi per inch which is why pixels should be avoided for sizing text for the web.


    Free Expression Web Tutorials
    For an Expression Web forum with without the posting issues try expressionwebforum.com

    Saturday, November 10, 2012 8:01 PM
  • This is a tough crowd ! Feel like I am before a review board! lol :)

    Well, you have to remember that we are a group of experienced, professional developers. It is simply our nature to take note of issues with a site which are not congruent with what are considered consensus best practices in the industry. If you want bad/no advice, you need to find a forum populated by know-nothing tyros who neither recognize nor care about issues with your site. You won't find many of those here. Or, at least, none who actually take the time and effort to contribute.

    The navigation bar no longer floats up and down, though I don't know what I did that fixed it.

    As I mentioned in an earlier post, as you eliminate the page-by-page styling, you will find that variations between pages vanish. I haven't done an in-depth analysis today, but my guess is that you got rid of an in-page style that was causing the shift. I have looked at the source of a couple of pages, and you still have a sizable amount of junk classes.

    I also note that you have changed the <title> elements as suggested. Well, except for one—the "Experience" page still says that it is "Rapid Response Consulting Client Services." Oh, and looking just now, I noted that, while you changed the <title> element, you did not change the associated "description" meta. Since the description meta is often displayed by Google just below your page's title in the results page listing, you might want to attend to that. The description meta can, and should, be longer than the title, providing more information to the searcher than the short title can, and if well-written, may induce the searcher to click that result instead of another. Just sayin'...

    There's still some extra style sheets floating around, but they are listed in the uneditible area in each page.

    Not sure what you mean by this. All of your pages reference "styles3.css," which is one of the three style sheets provided with every EW template (along with "layout.css"), and that is the only external style sheet being referenced. If you mean that there are still embedded style blocks in each page, then yes, there are, and I provided detailed instructions in a previous post about how to move those to "style3.css" and remove them from the individual pages.

    To get access to them to remove them, simply edit them in the DWT file, where there is no such thing as a non-editable region. Delete them there, and they will be deleted throughout, once you save the DWT and let the changes propagate to the attached pages. If you first make the changes to add "columnText" and "h3" definitions to "style3.css," save it, then change "<div class="style6">" to "<div class="columnText">, then save the DWT, the eliminated "style2" through "style6" will never even be noticed.

    To finish the job, create a class in "style3.css," like so...

    .companyName {
       font-family:Magneto; /* if you insist on having no fallback */
    }

    Then, in your source code (of the DWT) edit "<h1 class="style1">Rapid Response Consulting</h1>" to read "<h1 class="companyName">Rapid Response Consulting</h1>." Now you can delete the "style1" definition in the DWT, save it and let the changes propagate to all pages, and you will have NO local styling applied in any page, and you should have zero page-to-page variance in display.

    <edit>
    Whups, spoke too soon. Looking at the "About" page, you have a local ".style8," which is used only to style a non-breaking space in an empty paragraph(?!). You also have a ".style11" and a ".style17," which are not used anywhere. All three can safely be deleted from the source of that page (they're in an editable region); no other action required. Likewise, on the "Experience" page, you have a local ".style2," which has already been dealt with in ".menuText," and a ".style6," replaced by ".columnText," and a ".style7" and a ".style10," neither of which are used anywhere, so all four of them can be simply deleted from the source of that page (they're in an editable region); no other action required. And, finally, in the "Contact" page, you have local ".style2" and ".style5," both od which have been accounted for, and both of which can safely be deleted from the source of that page (they're in an editable region); no other action required. Once that has been done, there will be no local styling on any page, and as long as you make future changes to common areas only in "style3.css," you will never again see inconsistencies between your pages. This is not rocket science; it is attention to detail, and considering the consequences of actions before you take them.
    </edit>

    It's a pity that you are so obdurate about that justified text. As has been pointed out, the issue is not whether you like the text justified that way, but how your visitors feel about it. Justified text, besides the other things already mentioned, tends to create whitespace "rivers" which run at angles through the text, making it subtly "odd" in appearance and difficult to read. This is, after all, your "face" on the Web; it is difficult to understand why you would voluntarily apply acne scars to it.

    cheers,
    scott


    Please remember to "Mark as Answer" the responses that resolved your issue. It is common courtesy to recognize those who have helped you, and it also makes it easier for visitors to find the resolution later.

    • Edited by paladyn Sunday, November 11, 2012 1:42 AM
    Saturday, November 10, 2012 9:11 PM
  • It's 2:44 AM and I'm just about out of computer fuel  :)

    I've just finished some Metadata collections for FEMA to be used in New York. 

    Here's what I've learned, Expressions is complex, but Census Data is even tougher. 

    Okay, you guys win, the justify style is gone :)

    Scott,

    I have to say, I am not putting these styles you keep finding in manually... all I'm doing is creating content and then adding stuff and -  yeah, that's where it goes wrong. Because I'm used to adding stuff like bold or italics or whatever in the specific content and keep moving along. But as you point out, it adds yet one more layer of style all over the site. 

    So I will try to clean  it all up next weekend, though I may wind up actually going to New York to help clean up a disaster of a different kind...

    At least my site works...for now. yes there's some minor glitches and errors and omissions. I promise to fix those later. Right now, I'm burning the candle at both ends. 

    cheers and thanks!

    Sunday, November 11, 2012 7:49 AM
  • What are you settings in Tools > Page Editor Options > CSS. Take a look at Tina's ebook on setting up EW. I get em and strong using the format toolbar buttons not auto styles. If you have commonly used styles give them a name you will recognize and click on the style in the Apply Styles list instead of on the toolbars. That will prevent the auto creation of styles and give you a consistent look.

    Free Expression Web Tutorials
    For an Expression Web forum with without the posting issues try expressionwebforum.com

    Sunday, November 11, 2012 4:26 PM
  • Cheryl's little tidbit has helped. The layout of EW2 takes some getting used to. And after watching Cheryl's 1st video (all the time I could allot for the moment), some instructions are starting to fall into place on how each component of EW is structured - and why. But it is a lot to learn all at once - in a crash course sort of way.

    I also like that you can just 'reset' the tool windows back to default in nothing flat.

    One question I do have. I'd like to set the 'outside' color of what surrounds the website (the medium blue it is now) to one of the colors inside the mast head graphic. How do I change that color, in the layout.css or dwt...

    thanks,

    Doug

    Tuesday, November 13, 2012 7:15 AM
  • "How do I change that color, in the layout.css or dwt."

    You find what style applies that color, and change it (if you want to change the style for all uses of it) or override it on the page (if you only want to change it for the current page).

    EW has tools that make it easy to find where a specific style is coming from for an element.  Look into the "CSS Properties" panel.  Select an element on your page (use the tags "breadcrumb" to make sure you have the proper thing selected), and that panel will tell you all the styles applied, and where they are defined.

    Tuesday, November 13, 2012 6:35 PM
  • I get that part.

    But the problem is, what is the 'definition' of the space outside the website's formatted size?

    I can't find that definition in any of the layouts. What word is used for its description (default mode of EW)?

    thanks,

    Doug

    Tuesday, November 13, 2012 6:44 PM
  • One thing you could look at is the page properties tab where you will find the page background color can be changed. Assuming you have a container where your content is andyou have set the color then the area outside (behind) the container can be set in page properties.

     
    Tuesday, November 13, 2012 7:34 PM
  • One question I do have. I'd like to set the 'outside' color of what surrounds the website (the medium blue it is now) to one of the colors inside the mast head graphic. How do I change that color, in the layout.css or dwt...

    thanks,

    Doug

    That color is set in your body style, in line #4 of "style3.css," like so...

    body {
        background-color#336699;
        font-family"Trebuchet MS",Tahoma,Helvetica,sans-serif;
        font-sizesmall;

    }

    Change the background-color property to whatever you wish. Since that CSS file is referenced by all of your pages, it will change the color for all pages. If you wish to change it for only one page, create a page-local embedded style for that page, like so...

    <style type="text/css">
    body {
        background-color:#ffff00;
    }
    </style>

    Make sure that the style block follows your link statement referencing the external stylesheet, or it will be overridden.

    cheers,
    scott


    Please remember to "Mark as Answer" the responses that resolved your issue. It is common courtesy to recognize those who have helped you, and it also makes it easier for visitors to find the resolution later.

    Tuesday, November 13, 2012 8:02 PM
  • Do I dare ask how I can embed RSS with customization?

    After reviewing some of Expressions help sections on embedding, there are couple of things I should review before I attempt it.

    1) Create a separate CSS style for use on a page (or new content page).

    For this I was planning to call it fema.css

    2) ensure that RSS feed is its own folder of the webpage (so I created it; /RSS with attached rss file)

    3) Then I want to be able to modifiy  the contents of the rss feed in how they look. Which EW does a nice job of displaying, in this case a table with the associated columns and rows. EW also allows you to create how many  'stories' are shown at any one time. In this case, I would like to have the top 5.

    Then the tricky part, I want to modify one of the columns to be hidden (which EW allows you to suppress), but use the data inside it to be a "link" to another column which is defined at description shown here;


    Location
    link description Date
    Agency
    <xsl-value-of node-walk="54" select="title">Rhode Island Hurricane Sandy</xsl-value-of> <xsl-value-of node-walk="56" select="link">http://www.fema.gov/disaster/4089</xsl-value-of> <xsl-value-of node-walk="58" select="description">Major Disaster Declaration number 4089 on Nov 03, 2012</xsl-value-of> <xsl-value-of node-walk="60" select="pubDate">Sat, 03 Nov 2012 11:11:00 EST</xsl-value-of> <xsl-value-of node-walk="62" select="dc:creator">FEMA</xsl-value-of>
    <xsl-value-of node-walk="54" select="title">Utah Severe Storm and Flooding</xsl-value-of> <xsl-value-of node-walk="56" select="link">http://www.fema.gov/disaster/4088</xsl-value-of> <xsl-value-of node-walk="58" select="description">Major Disaster Declaration number 4088 on Nov 03, 2012</xsl-value-of> <xsl-value-of node-walk="60" select="pubDate">Sat, 03 Nov 2012 10:11:00 EST</xsl-value-of> <xsl-value-of node-walk="62" select="dc:creator">FEMA</xsl-value-of>
    <xsl-value-of node-walk="54" select="title">Connecticut Hurricane Sandy</xsl-value-of> <xsl-value-of node-walk="56" select="link">http://www.fema.gov/disaster/4087</xsl-value-of> <xsl-value-of node-walk="58" select="description">Major Disaster Declaration number 4087 on Oct 30, 2012</xsl-value-of> <xsl-value-of node-walk="60" select="pubDate">Tue, 30 Oct 2012 18:10:00 EST</xsl-value-of> <xsl-value-of node-walk="62" select="dc:creator">FEMA</xsl-value-of>
    <xsl-value-of node-walk="54" select="title">New York Hurricane Sandy</xsl-value-of> <xsl-value-of node-walk="56" select="link">http://www.fema.gov/disaster/4085</xsl-value-of> <xsl-value-of node-walk="58" select="description">Major Disaster Declaration number 4085 on Oct 30, 2012</xsl-value-of> <xsl-value-of node-walk="60" select="pubDate">Tue, 30 Oct 2012 04:10:00 EST</xsl-value-of> <xsl-value-of node-walk="62" select="dc:creator">FEMA</xsl-value-of>
    <xsl-value-of node-walk="54" select="title">New Jersey Hurricane Sandy</xsl-value-of> <xsl-value-of node-walk="56" select="link">http://www.fema.gov/disaster/4086</xsl-value-of> <xsl-value-of node-walk="58" select="description">Major Disaster Declaration number 4086 on Oct 30, 2012</xsl-value-of> <xsl-value-of node-walk="60" select="pubDate">Tue, 30 Oct 2012 04:10:00 EST</xsl-value-of> <xsl-value-of node-walk="62" select="dc:creator">FEMA</xsl-value-of>

    What I want to do is "hide" the Link Column, but HREF - hyperlink it's content address to description part so when a user clicks on the event, it opens up a new window and takes the user to the appropriate page on FEMA's website.

    Is what I'm describing possible?

    thanks!

    Doug

    Tuesday, November 13, 2012 8:50 PM
  • If you would like a consultation to fulfill this request, please submit complete specifications and requirements, a timeline and milestones requirements, your proposed budget, and a copyright indemnity statement to protect the developer who may undertake the contract.

    This is quite a bit more than what we generally undertake here in this forum, and I am as close to certain as I can be that you do not have the skills necessary to do this yourself.

    cheers,
    scott


    Please remember to "Mark as Answer" the responses that resolved your issue. It is common courtesy to recognize those who have helped you, and it also makes it easier for visitors to find the resolution later.

    Tuesday, November 13, 2012 9:00 PM
  • First you aren't actually clear what you want and second it should be in its own. If this is an RSS you are trying to consume and display the easiest thing is to use one of the services or libraries like Google's Ajax feed http://www.javascriptkit.com/dhtmltutors/googleajaxfeed.shtml or http://itde.vccs.edu/rss2js/build.php

    Free Expression Web Tutorials
    For an Expression Web forum with without the posting issues try expressionwebforum.com

    Tuesday, November 13, 2012 10:06 PM
  • Yeah, those would work, although the second, by its own statement, is "likely to go away." In either event, the developer would have to understand enough (about both HTML/CSS and javascript) to implement them, and neither, even the Google API solution that may not be subject to just "go away," permits the kind of customization that the OP is asking for in his post.

    That could, of course, be done by examining the generated source of the rendered page using the WDT, then writing the appropriate CSS based upon the source of the rendered page. That presupposes the ability to read and understand the generated source, and to write the necessary CSS without the help of EW's visual tools, since the page does not exist as rendered in the EW interface.

    I will agree, however, that since this has absolutely nothing to do with the topic of this thread, that it should be moved to its own thread.

    cheers,
    scott


    Please remember to "Mark as Answer" the responses that resolved your issue. It is common courtesy to recognize those who have helped you, and it also makes it easier for visitors to find the resolution later.

    Wednesday, November 14, 2012 3:47 AM
  • Thanks for the tips. The Federal Emergency Management Agency's RSS feed is pretty straight forward.

    It's simplistic in its feed, 5 tables of content as shown. All I wanted to do was 'hide' the url portion, use it's content as a link / href to the next table's contents (description), which a user can then click and be sent (in a new browser window) to FEMA's site.

    The content is public domain (as all U.S. Government generated and published data is, by law).

    The actual RSS feed is authored by FEMA, not Google.

    It looks like I've offended by putting this extra request in this thread, sorry about that. Consider this thread completed and mission accomplished. Many thanks to those that assisted me getting around Expression Web 2.0 and giving me some links to follow to learn, adapt new ideas and get sound feedback on my site.

    Great work by volunteers!

    Doug

    RRC

    Wednesday, November 14, 2012 4:19 AM
  • No offense taken, Doug; it's just that the topic of this thread has been addressed already, and this is, in fact, a completely new topic, unrelated to the original. For the benefit of those who come after, and who may look for information on this subject, it is better that it be moved to a thread of its own. That is standard advice that we give almost any time a topic divergence such as this occurs.

    What you want to do can be done. It is not trivial, and it does require more than a passing familiarity with HTML page structure, as established by source order, and as presented by applied CSS. It also requires a degree of familiarity with professional developer's tools, such as the Web Developer Toolbar (the "WDT" mentioned earlier), Firebug, and others, to be able to view the page source after it is generated, when the javascript has run and the feed has been incorporated, in order to analyze the structure of the rendered page, to determine which elements present themselves for modification using CSS.

    As stated, this is not a trivial task, and it does not actually fall within the scope of the purpose of this forum. We are here to answer specific questions, using the short message format, not to provide generalized tutorials about extensive processes such as this. If you take our advice, given earlier, to learn about HTML and CSS using the resources listed, and install and put in some practice with the developer's tools described, then you will be able to handle it yourself. Without that knowledge and practice, you will be unable to make the necessary changes, regardless of what we tell you here. Like I said, no offense given, or taken. Just the truth of the matter... ;-)

    cheers,
    scott


    Please remember to "Mark as Answer" the responses that resolved your issue. It is common courtesy to recognize those who have helped you, and it also makes it easier for visitors to find the resolution later.

    Wednesday, November 14, 2012 9:12 PM