Skip to content
View in the app

A better way to browse. Learn more.

Web Designer Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

bb_matt

Members
  • Joined

  • Last visited

  1. Me? Front-end web dev, apache, linux, CMS systems. Lesser strengths (but growing), mysql & php + an eye for design - a path I could've chosen, but didn't pursue. (yet) ------ The other aspect of this idea is from a client side. It strikes me that the types of clients who would use services of this ilk, are often simply looking for the cheap 'quick fixes', rather than long term, quality solutions. More professional organisations & companies prefer to work with a trusted entity, rather than taking chances with an online service. The idea of "here today, gone tomorrow" isn't appealing - as I client, I would want someone to be around for the long term - commitment. The reality is, a website is *never* complete, but rather, it's a long term partnership. Good clients want face to face, a known entity, support. They 100% require an active partner - someone they can get on the blower to, meet with, discuss the project. So, who should this service aimed at? Well, obviously ... agencies. The way to work it, in my mind, is to advertise services to web development agencies, who can take the work produced forward without requiring a long term relationship.
  2. Very late to read this one and struggling to follow the exact idea in this looooong thread. Sorting out the wheat from the chaff could be done using the Forrst methodology - you need to get a certain amount of invites to be allowed in. Prior to this, you need to demonstrate your ability somehow. I may have misunderstood the entire thing, but the key idea is to keep the idiots out.
  3.    Liquid-Drive reacted to a post in a topic: Cufon (Text Shadow)
  4. Thanks guys! There goes my evening ... (the GF will be watching X-Factor)
  5. Sure, you can style it - but the specifications suggest not to. In fact, call me crazy, but I'm of the mind that semantic elements such as nav, aside, article and section shouldn't be styled at all. A small amount of extra markup, in the form of divs - which really are the main place to apply styles - seems the better route. At one point, I was doing stuff like <nav style="primary"><ul> .... Then figured, it's best to do <nav><ul style="primary"> .... Or better still, if your primary nav is within a header div, just use that to apply the styles directly to your list. There's a lot of reliance on HTML5 shiv to ensure your layouts play ball in internet explorer - so, your effectively using Javascript to do the translation grunt work for you. If those key html5 elements are not using for styling purposes.... Well, seems like the better option to me. Lest we forget, ie7 & ie8 still have a market share large enough to have to take notice.
  6. +1 here. Not sure when I'd use it, as most my work is CMS based - but bookmarked anyway - designers at work will love it!
  7. What Renaissance-Design said. Try to keep the use of ID's to main content sections. The example of id="red" above isn't a good one. As well as ensuring you know when and where to use ID's and Classes, make sure your code makes sense - semantically. Try to avoid putting classes on anything other than structural elements. IOW, <p class="bold_red_text">Text</p> is a terrible idea. But... <div class="contact_box"> <h2>Contact us</h2> <p>Address details</p> </div> div.contact_box h2 { color:red; font-size:180%; } div.contact_box p { color:green; font-size:120%; } That will set you on the right track.
  8. Cheers Mike! I should be able to get another two votes from work and then... er, well, not sure really till I get in there!
  9. Use @font-face instead.
  10. <li><p>Home</p><small>Smaller text underneath</small></li> Set small to be a block level element. Your going to have to give a width to your li tags, however, or it will destroy the layout. Basically, your li have to be block level too. Something like this: li { display:block; width:150px; float:left; margin-right:10px; } To be honest, you may as well do this with background images, so that your design fits perfectly. I presume this is for a top nav? There's methods where you still have a semantic list, but you *hide* the text and use background images. This requires an exact height and width on each list tag. Alternatively, use @font-face to get the design working for you.
  11. Well, that was a good start by me! Put some HTML code in, it didn't work, went back and edited ... And now I'm suggesting that a definition list is the best response to a design for a panning knob - bravo matt!
  12. I'm pretty keen to join too. http://forrst.com/i/CPl Some work - the first few I've done the 'design' and coding. As you can see, I'm primarily a coder. http://www.brimstonephotography.co.uk/ http://www.downfarmodiham.co.uk/ Then here's a bunch of stuff I've coded - although lots of it has been bastardised after the fact, or ruined by client: http://www.rosebowlplc.com/ http://www.gardentrading.co.uk/ http://www.handfordconstruction.co.uk/ http://www.paperiq.com/ A sample poster - I've done about 10 of them for local events: This is on my Flickr photostream. Thanks.
  13. It's designers only, right?
  14. hehe. Well, my point is, use everything and anything to get the job done. Windows 7 & Mac can both get exactly the same job done and are both easy to use. These days, they can actually 'talk' to each other too, unlike the bad old days of MacOS 9 and Win98 ! There's things I hate about MacOS X - the window management does my head in sometimes. Silly things, like the lack of # on the keyboard, I have to use Option+3. But when it works well, boy does it ever. Plugin in a printer - works. Scanner - works. Camera - works. Networking - works. And it's UNIX based! Windows 7 - I hate the networking aspect of it. At work, after all these many years, windows *still* struggles to see network resources. Memory management still sucks, there's still the nasty old .dll and registry crapola. If I had my choice - and the readies - I'd go MacBook Pro or 27" iMac any day of the week, heck, both of them.
  15. I use *everything* At work, windows 7 desktop with an Ubuntu VM that's permanently open. Access to a Mac to check layouts in browsers and work on design amends if I don't have a particular font. At home, I *did* have a Macbook Pro 15" but sold it when times got tough. I now run a Hackintosh and also have a Windows/Linux box upstairs. Shiny is nice, but really, it's what you do with your computer that counts, not what it looks like or what OS it runs. My Hackintosh is now my primary home platform - and I'd advise this route to those who *want* to run mac os x, but are cash strapped. It's not for the feint hearted - setting it up can be difficult. Legally, well, buy the OS and check your moral compass. It's against the EULA to install the OS on anything other than Apple hardware, so legally, your breaking a contractual agreement if you run it on non-Apple hardware. One thing is for sure, it's a damn side easier to fix when things go wrong. My GF's 24" iMac has been back to the repair shop 5 times in 3 years - superdrive, ram, hard drive, screen. She's still under Apple Care - but that runs out in October - then, any time anything goes wrong, she has to take it in to get it fixed and fork out the cash for parts and labour. Conclusion: If you have the cash for a MacBook Pro, go for it - they are *stunning* laptops. Or if your the DIY type and are a bit cash strapped, heck, build a Hackintosh !
  16. A lot of this is still up for discussion. I'll agree, I could've used <footer> - in fact, I originally did, then decided it's not mandatory for the footer of the entire site and could actually lead to confusion. The same applies to using <header> for the main site header content. Personal choice. Interestingly enough, there's times where it's advised you *should* use divs to style content. The first HTML5 site I constructed, I used CSS to directly define <section> style's, which is apparently, incorrect: http://html5doctor.com/the-section-element/ Confusing eh? It seems a lot of this is still being ratified/investigated/discussed and indeed modified, for instance, the <nav> element: http://html5doctor.com/nav-element/ To add even more confusion to things, some of the big players (such as Apple), have confused HTML5 with CSS3 and Javascript - the 'marketing' of HTML5 has been a little misleading to say the least, lumping everything together under a single banner - pretty much just like they did with the dreaded phrase 'web 2.0' What's most important, in the final analysis, is: Semantically sound Valid Accessible

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.