Skip to main content

Home/ Tools for web developers/ Group items tagged tips

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
de Villamil Frédéric

Designing Typography for the Modern Web | Tips - 1 views

webdesignledger.com/...-typography-for-the-modern-web

typography webdev webdesign design

shared by de Villamil Frédéric on 31 Oct 10 - No Cached
  • de Villamil Frédéric on 31 Oct 10
     
    As web designers, it is our job to grow with the trends of the Internet. As new technology emerges, it's our position to jump on board and see where it can take us. This includes trends all over the web, typography being a major player. Many designers don't consider type as a field of interest or focus. Ironically, typography is possibly one of the most important parts of our dynamic web. It helps deliver a website's content to users from all over the world and it truly is an art to study. I'll be getting into a few concepts about typography for the modern web. Things haven't changed too much since the previous years of web design, however many new techniques are being utilized and shared amongst the design community.
Sarah HL

10 options pour choisir un CMS - 0 views

www.nexen.net/...ptions_pour_choisir_un_cms.php

php cms lang:fr tips

shared by Sarah HL on 16 Jul 09 - No Cached
  • 1 - Le CMS que vous choisissez doit être vraiment bien à ce que la fonction principale de votre site Web. 2 - Un CMS doit travailler de manière intuitive. 3 - Le backend doit être normalisé. 4 - Le backend doit être logique et bien organisé. 5 - Le droit de CMS ne doit pas avoir une tonne de fonctionnalités supplémentaires, vous ne serez jamais utiliser. 6 - Le droit CMS devrait être facile pour les non-geeks à utiliser. 7 - Il doit inclure un éditeur WYSIWYG. 8 - Les pages qu'il crée doit être rapide et simple de chargement de code. 9 - Le moteur de template doit permettre de remplir le contrôle créatif 10 - Le droit CMS devraient avoir suffisamment de soutien et de la documentation
Sarah HL

JUnit FAQ - 0 views

junit.sourceforge.net/...faq.htm

programming bestpractices testing lang:en tips

shared by Sarah HL on 29 Jun 09 - Cached
  • They effectively communicate in an executable format how to use the software. They also prevent tendencies to over-build the system based on speculation. When all the tests pass, you know you're done!
  • Test-driven development is a lot more fun than writing tests after the code seems to be working
  • Do I have to write a test for everything? No, just test everything that could reasonably break.
  • ...6 more annotations...
  • If something is difficult to test, it's usually an opportunity for a design improvement.
  • Frequent testing gives you confidence that your changes didn't break anything and generally lowers the stress of programming in the dark.
  • Run all your unit tests as often as possible, ideally every time the code is changed
  • For larger systems, you may just run specific test suites that are relevant to the code you're working on.
  • write a failing test that exposes the defect. When the test passes, you know the defect is fixed!
  • Don't forget to use this as a learning opportunity. Perhaps the defect could have been prevented by being more aggressive about testing everything that could reasonably break.
1 - 3 of 3
Showing 20▼ items per page