/* Start of CMSMS style sheet 'base' */
#pageWrapper
{
	margin: 0;
	width: auto;
	min-width: 500px;
}
#outerColumnContainer
{
	z-index: 1;
	border-color: #fff;	/* set default color to white. set the real
				   color inside colors.css */
	border-style: solid;
	border-width: 0 15em;	/* sets the width of the borders used to create
				   the left and right columns' background 
				   color. */
}
#innerColumnContainer
{
	z-index: 2;
	width: 100%;
}
* html #innerColumnContainer
{
	position: relative;	/* fix a render bug in IE under certain
				   conditions */
}
#contentColumn
{
	margin: 0 -1px;		/* without this, boxes stop floating next to 
				   each other */
	width: 100%;
}
#leftColumn, #rightColumn, #contentColumn
{
	float: left;
	position: relative;	/* IE has a display/render bug with non-floated 
				   block elements inside floated block elements. 
				   setting position:relative on the floating
				   element seems to resolve this. */
	z-index: 10;
	overflow: visible;	/* fix for IE italics bug */
}
#rightColumn
{
	float: right;		/* floating this right allows for the right
				   column block to appear before the content
				   column in the flow of the document. doing
				   this allows for any easy 3 column layout
				   in NN4.

				   There is certainly a lot, in terms of layout
				   'theory' about how the flow of the document
				   should be. I won't get into it here. */
	width: 15em;
	margin: 0 -15em 0 1px;	/* same as in the #leftColumn selector up 
				   above. */
}
#leftColumn
{
	width: 15em;
	margin: 0 1px 0 -15em;	/* like in the #contentColumn selector, without
				   the 1px margin on the opposite side of the 
				   box, boxes stop floating next to each 
				   other */
}
#footer
{
	position: relative;
}
#masthead h1
{
	display: inline;	/* personal preference to keep the header 
				   inline. you could just as easily change 
				   padding and margins to 0. */
 
}
.clear
{
	clear: both;
	padding-bottom: 1px;	/* for Gecko-based browsers */
	margin-bottom: -1px;	/* for Gecko-based browsers */
}
.hide, #oldBrowserNotice, .ieSixCharDupBug
{
	/* hide elements that CSS-targeted browsers shouldn't show */
	display: none !important;
}
#contentColumn
{
	border-width: 0;	/* reset value from that in the version 4 
				   stylesheet. this isn't in borders.css because
				   were you to create a print.css and not 
				   include borders.css, then the v4 border would
				   still remain when you print. */
}
/*
	The below block of CSS is invalid, and will invalidate this stylesheet.
	So it is up to you to decide how you want to handle this. The below CSS
	is a fix for IE/Win to help it better handle text that is wider than 
	the available area. It does not handle this as expected, and forces the
	floated elements to start stacking. This is a very undesirable thing.
	Until a CSS-compliant way is devised, this CSS block will have to do.

	So, do you live with invalid CSS? This comes down to a sort of markup
	morals issue. Some people live and die by w3 validation. If it isn't
	valid, it isn't good. Others don't validate at all, rather focusing
	on "real-world" results.

	I think the answer might be somewhere in the middle, but perhaps 
	leaning torwards w3 validation. It's good to work torwards validation.
	Indeed, I think documents should be able to validate against a w3
	or other validator. However there are times where you will find reason
	to explicitly defy the specs and include invalid markup or CSS.

	It is already done once in the markup of this layout, using the name
	attribute of an anchor tag. That attribute is deprecated in XHTML 1
	but without it, backwards compatibility at even the most base level
	is destroyed. So I purposely break the spec in order to provide that
	backwards compatibility. Remove the one line, and it validates fine.

	I am willing to break the markup when I have a good reason. And I think
	this is the same type of situation. IE breaks horribly without this 
	fix. I am willing to include this invalid line of CSS in order to 
	keep IE happy. Using the * html selector, I know that CSS-compliant
	browsers (the ones where validation matters) won't apply this CSS block.
	Pretty much ONLY IE will apply this CSS. I have a reason to break the
	CSS, I am fairly certain of its effect on other browsers (none), and
	so I include it here.

	I could have used the conditional comments that IE supports in it's
	proprietary side of HTML. However that requires _every_ document to
	contain the extra lines necessary to do this. This removes any
	central point of control over at least some of the CSS being
	applied.

	In a template(d) environment, perhaps I would take that alternate route.
	But here, where I'm not in a template(d) environment, I choose to add
	this directly into the CSS.
*/
* html #pageWrapper
{
	word-wrap: break-word;
}

#masthead h1 a {
/* you can set your own image here */
   background: url(../uploads/images/mrsushi-logo.gif) no-repeat 0 0px; 
   display: block;
   height: 55px;             /* adjust according your image size */
   width: 164px;
   text-indent: -999em;  /* this hides the text */
   text-decoration:none; /* old firefox would have shown underline for the link, this explicitly hides it */
  float:left;
}

#masthead h3 {
 display: block;
height: 55px;
width:520px;
float: right;
}

.link, a, a:active {
color: #ffcc00;
text-decoration: none;
}

.link:hover, a:hover {
color: #fff;
text-decoration: underline;

}

/******************************************************************************/
/* End of 'base' */

/* Start of CMSMS style sheet 'hnav' */

.hnav
{
	border-bottom: solid 1px #fff;
	text-align: center;
 list-style: none;
}
.hnav, .hnav ul li a
{
	/* need to middor veritcal padding on .hnav and child anchor elements
	 * because the anchors are _not_ block elements. since they are not
	 * block elements web browsers will not expand .hnav to contain them
	 * even with the extra padding. by applying the same padding to both
	 * the parent .hnav _looks_ like its containing the child anchor
	 * elements. 
	 */
	padding-top: 3px;
	padding-bottom: 4px;
 list-style: none;
}
.hnav ul, .hnav ul li
{
	display: inline;
	list-style: none;
	margin: 0;
	padding: 0;
}
.hnav ul li a
{
	margin: 0 -1px 0 0;
	padding-left: 10px;
	padding-right: 10px;	/* short-hand padding attribute would overwrite
				   top/bottom padding set in a previous rule */
	border-left: solid 0px #000;
	border-right: solid 0px #000;
	white-space: nowrap;
}
.hnav ul li a:link, .hnav ul li a:visited, .hnav ul li a:active, .hnav ul li a:hover
{
	text-decoration: none;
}
.hnav ul li span.divider
{
	display: none;
}
* html .hnav ul li, * html .hnav ul li a
{
	width: 1%; /* IE/Mac needs this */
	display: inline-block;	/* IE/Mac needs this */
	/* \*/
		width: auto;
		display: inline; 
		position: relative;
	/* reset above hack */
}
* html .hnav, * html .hnav ul a
{
	/* \*/ height: 0.01%; /* hasLayout hack to fix render bugs in IE/Win. 
				 IE/Mac will ignore this rule. */
}
* html .HNAV
{
	padding: 0;	/* IE5/Win will resize #hnav to fit the heights of its
			   inline children that have vertical padding. So this
			   incorrect case selector hack will be applied only by
			   IE 5.x/Win */
}

/******************************************************************************/
/* End of 'hnav' */

/* Start of CMSMS style sheet 'colors' */
body
{
	background-color: #665;
	color: #fff;

}
#outerColumnContainer
{
	border-left-color: #161414;	/* left hand column background color */
	border-right-color: #161414;	/* right hand column background color */
}
#masthead
{    
	background-color: #000;

	color: #fff;
}
#footer
{

	background-color: #272423;
	color: #fff;
}
#outerColumnContainer, #contentcolumn	/* selector case hack to reset version 4
					   stylesheet setting */
{
	background-color: #000;		/* this sets the background color on the
					   center column */
	color: #fff;
}
#leftColumn, #rightColumn, #contentColumn
{
	color: #fff;
}

.vnav h3
{
color: #888;
}

.vnav ul li a
{
	color: #fff;
	 background-color: #161414; 
}


#rightColumn .vnav ul li a:hover, .vnav ul li a:hover
{
	 background-color: #161414; 
	color: #fff;
}
#rightColumn .vnav ul li a
{
	color: #888;
	 background-color: #161414;
}
.hnav, .hnav ul li a
{
	  background-color: #272423; 
	color: #888;
}
.hnav ul li a:hover
{
	 background-color: #336; 
	color: #fff;
}
#pageWrapper, #innerColumnContainer, #masthead, #footer, .hnav
{
	border-color: #000;
}

#footer p
{
color: #888;
}

h2 {
color: #c34311; 

}

.vnav h3,h4
{
color: #ccc;
}

.vnav
{
color: #888;
}

hr {border: none 0;
border-top: 1px solid #272423;/*the border*/
color: #272423;
width: 100%;
height: 1px;/*whatever the total width of the border-top and border-bottom equal*/

}

#pageWrapper #outerColumnContainer #innerColumnContainer #rightColumn .inside .vnav a {
	text-decoration: none;
	color: #666655;
}

#pageWrapper #outerColumnContainer #innerColumnContainer #rightColumn .inside .vnav a:hover {
	text-decoration: none;
	color: #ffcc00;
}

#pageWrapper #outerColumnContainer #innerColumnContainer #contentColumn .inside h3 {

}

/******************************************************************************/


/* End of 'colors' */

/* Start of CMSMS style sheet 'borders' */


#pageWrapper
{

	border-style: solid;	/* explicitly defined within eact selector in 
				   case you want change border styles (to mix 
				   it up) between elements */
	border-width: 0 0px;	/* puts a border on the left and right sides of
				   the page. #masthead and #footer will handle 
				   the top and bottom borders */
				   
				
}
#outerColumnContainer
{
	/* the borders used to create/reserve space for the side columns are
	   now defined in base.css because they are an integral part of
	   the layout. */
}
#innerColumnContainer
{
	border-style: solid;
	border-width: 0 1px;	/* puts borders between center and the side 
				   columns. */
	margin: 0 -1px;		/* compensation for the borders because of
				   100% width declaration on this object */
}
* html #outercolumncontainer
{
	/* IE5.0/Win fix for 1px whitespace between masthead and body. */
	margin-top: -1px;
	border-top: solid 1px #272423;
	
}
#masthead
{
	border-style: solid;
	border-width: 0 0 0 0;	/* handles the top of the layout's border and the
				   bottom of the masthead section */
}
.hnav
{
	border-style: solid;
	border-width: 0 0 0px 0;
}
#footer
{
	border-style: solid;
	border-width: 1px 0;	/* handles the top of the footer section and 
				   the bottom of the entire layout */
}

/******************************************************************************/
/* End of 'borders' */

/* Start of CMSMS style sheet 'fonts' */
body
{
	font-family: arial, helvetica, sans-serif;
	font-size: 100.1%;	/* font sizing approach recommended by Dave 
				   Silvester on the css-discuss list. "the 
				   .1 is important." */
}
#pageWrapper
{
	font-size: 80%;
}
#footer
{
font-size: 90%;
	text-align: left;
}
/* :root is an invalid pseudo class but mozilla knows it */
:root code
{
	font-size: 120%;	/* monospace fonts are typically smaller that 
				   'normal' fonts under Mozilla. */
}

/*
	Time to try and get all the heading elements to the same size 
	regardless of browser. (IE seems to put them a big bigger
	than Mozilla, typically.)
*/
h1
{
	font-size: 200%;
}
h2
{
	font-size: 150%;
}
h3
{
	font-size: 130%;
}
h4
{
	font-size: 116%;
}
h5
{
	font-size: 105%;
}
h6
{
	font-size: 100%;
}
.vnav h2
{
 font-size: 110%;
}

.vnav h3 
{
 font-size: 100%;
}

.vnav h4
{
 font-size: 88%;
}

.hnav
{
font-size: 102%;
font-weight: bold;
}

.small {
font-size: .9em;
font-style: italic;
color: #888;
}

#contentColumn h2 {

	font-size: 1.4em; 
	text-align: left; 
/* some air around the text */
	padding-top: 1em;
	padding-left: 0em;
	padding-bottom: 2px;
/* set borders around header */
	border-bottom: 1px solid #632c17; 
	border-left: 0em solid #c32211; 
        line-height: .5em;

/* and some air under the border */
        margin: 0 0 0.5em 0;
}

.bold{
font-weight: bold;
}

.italic{
	font-size: 90%;
	font-style: italic;
}

/******************************************************************************/

/* End of 'fonts' */

/* Start of CMSMS style sheet 'twoColRight' */

html>body #leftColumn
{
	display: none;	/* for compliant browsers, hide this column entirely */
}
* html #leftColumn *
{
	display: none;	/* ie's ghost-text bug is triggered by key elements
			   having display:none set. #rightColumn is one of those
			   key elements. so we display:none all child
			   elements (doesn't trigger the bug) and try to
			   make #rightColumn have no chance to affect
			   document flow. */
}
#leftColumn
{
	position: absolute;
	margin: 0;
	padding: 0;
	width: 0;
	height: 0;
	border: none;	/* remove anything that'll give this elemnt width. */
}
#outerColumnContainer, #innerColumnContainer
{
	border-left-width: 0;	/* to get from 3 to 2 columns, we must hide the
				   left-side border */
}
#innerColumnContainer
{
	margin-left: 0;
}

/******************************************************************************/
/* End of 'twoColRight' */

/* Start of CMSMS style sheet 'fixedWidth' */
* html body
{
	text-align: center;	/* hack to center this under IE5 */
}
* html #pageWrapper
{
	text-align: left;	/* keep the content left-aligned */
}

#pageWrapper
{
	width: 750px;
	margin-left: auto;
	margin-right: auto;
}


/* End of 'fixedWidth' */