Jonathanks

And remember to not spend yourself broke.Merry Christmas!

Yeah. Thumbs up to Ingolme. 10,000 posts = 10,000 impacts of knowledge, inspiration and direction.Some others here, like Ingolme said, deserve the attention: justsomeguy, davej, dsonesuk and others; just the ones I've seen as a newbie.

I just found out that using CSS alone would cause some pain with cross-browser compatibility which can be avoided using JS or PHP which is your chosen server-side language. I suggest you use PHP since JavaScript may be disabled on the client side. I'm glad we found the weakness in other methods like mine. Try out those suggestions there. I may find time to come back.@Count_Zero, Bert Coules and all that find time to season this forum, making it a place to be:It's a good thing to be with you. I love forums like this.

Ouch! Sorry for the multiple posts. I had poor network coverage so it kept returning errors connecting while it had actually sent my post. Moderators, please delete the excess posts. Thank you.

@ Count_ZeroThat's a clever way to do it using PHP, but CSS does this by default without having PHP's help. Of course, we still fall back to PHP since styling is involved and, in fact, our main aim. Using CSS saves you all the stress of creating new files in another language when you could just have it in one CSS file and it applies everywhere.Something like this:/*this should render the menu link that corresponds to the current page white in color*/ul.menu a:active {color:white;}Just an example to explain my humble opinion.

@ Count_ZeroThat's a clever way to do it using PHP, but CSS does this by default without having PHP's help. Of course, we still fall back to PHP since styling is involved and, in fact, our main aim. Using CSS saves you all the stress of creating new files in another language when you could just have it in one CSS file and it applies everywhere.Something like this:/*this should render the menu link that corresponds to the current page white in color*/ul.menu a:active {color:white;}Just an example to explain my humble opinion.

@ Count_ZeroThat's a clever way to do it using PHP, but CSS does this by default without having PHP's help. Of course, we still fall back to PHP since styling is involved and, in fact, our main aim. Using CSS saves you all the stress of creating new files in another language when you could just have it in one CSS file and it applies everywhere.Something like this:/*this should render the menu link that corresponds to the current page white in color*/ul.menu a:active {color:white;}Just an example to explain my humble opinion.

Having your table data with sql and php reduces your workload. You enter it once and you can retrieve it easily at anytime from any page. You can manipulate it easily too. Just MHO. Let the gurus speak.

I do not know if the purpose of this site resonates with your suggestion. It sounds like you want some coderacer-like features. That would be great too, but it is all up to the guys at the top. But I think you can do something impromptu in the general section.

This could help you. It is just what justsomeguy posted.https://dev.opera.com/articles/opera-mini-content-authoring-guidelines/

Most apps connect to the websites' database to function properly. For an ever-changing and frequently updated resource, like a news reporting platform, you definitely need a website. Okay. Imagine how facebook app would work without the website. Most times, or currently, the app is limited. You don't want to pack every function on the site into the app considering the user's device memory, like those using low-end devices. And if you don't have a website, your users would have to update the app to get latest news, like redownloading. And you'll have ~ versions each day. The app will definitely be downloaded from your website. So websites could exist for that reason.

That's funny because I can view the codes (html and css) even if you do not post it here. The files you uploaded is contain the codes.

Those books are still relevant. There are new books too. And for css, it hasn't changed much relative to those books. You need them. Css3 doesn't make those books irrelevant. There are books on css3.

You can make use of other materials like books (hardcopy and softcopy), video tutorials (if you're a visual learner), etc. Learn everything, but you may not need to use everything. Understand what you study first before sticking it into your brain. I wish you success.

I would personally object using multiple stylesheets for unit blocks of a page (as in your menu, home, layout up there). They're all part of the page. One stylesheet is enough for this. And you need to target specific elements too. You used too many styles for your navigation list. Everything in the nav list need not be styled differently. You can target all links in the nav tags (for hover, active, visited, link) without creating a #navlist id. And you should try to keep it simple -- I mean KISS! I think you should view the source code of the page you're trying to imitate to know what they really did. *just my opinion*

Those easy-to-use tools they provide really impede learning. Try doomby.com, wirenode.com, host.sk(for php) and many more you can google. In doomby, you'll find options to either use their already built templates or write your page in html.

Html content to be displayed on the page should go in the body tags. Try getting your site up. There're many free hosting providers. Since it's for testing, using one will not be a problem.

The footer section of your site should not be outside the body. And your css has some 'ids' that are not necessary. (your nav and its ids).

In your css #contentbox_left {/*three content boxes*/...}, would you place the three content boxes on the same page. I'd suggest you use .contentbox_left instead.

Current category's in black but still clickable. And when you hover it, the similar link above it gets highlighted too. Make the one above plain text.

I saw you've made changes. Good. For the category list on the mobile site, disable one link to avoid having two links highlighted simultaneously. I'll check more later. My battery's low. I like your site. Do you manage the back end your self? Help me create an account on your site then send me the login details as private message. I want to see more features.

Sorry I seem to misunderstand you here. What I mean is the hierarchy. Articles will still be displayed as a child category of photography both in the title and the links. Explain a little more. And since I'm posting from mobile, I'll be limited a bit to the mobile page.

Check yahoo's homepage for example. The main categories are listed in the top navigation. The side navigation is more detailed. If you click answers, the answers page has its categories on the side nav but just the main categories on the top.

The path would not change. Only the position on the page changes. Your design's almost there. Make it 'Rain - photography' rather than 'home - photography'. Home is not a parent to photography.

Okay. The button (>>) should have a label (Navigation>>) for easy identification. You may add a background color and change the display to block or make it a select menu.For the navigation in the header, make it less descriptive. You should have only the main categories of your site there, i.e programming and photography. For the side navigation, you should have a vertical list. The main categories should be bolded and aligned left while their child categories should be listed under them and should be indented some pixels right. E.g just a rough code. <nav class='side'><ul><li><b>programming</b></li><ul style='text-indent:5px'><li>-articles</li><li>-java</li><li>-ruby</li></ul></ul></nav>. You get my idea. Repeat same for photography list on the side navigation too.