-
Notifications
You must be signed in to change notification settings - Fork 2
Good Habits For Good Little Web Team Members
-
Add comments to your code! Read this: Comments in Code
-
Always Poofread! How to spell check with emacs: https://www.gnu.org/software/emacs/manual/html_node/emacs/Spelling.html
-
When embedding videos:
1. id="resizingIframe"
2. Give it its own personal <div>
3. Width of iframe = 100%
-
Don't use
<div class="12-columns">, IT IS NOT A CLASS... Use<div class="small-12 columns">or<div class="large-12 columns">or<div class="12 columns">. Grid help here: http://foundation.zurb.com/docs/components/grid.html -
Don't have duplicates for flexibility. For example, on the teams page we had a duplicate for every piece of text, with
class="visible-for-medium-up small-6 columns"and"visible-for-small-only small-12 columns"for changing text. Useclass="small-12 medium-6 columns" -
Always put things in rows and columns. Text fills 90%, and rows fill 90% as well, so when you have text in rows it fills 90% of 90%. If you don't put everything in rows/columns, then it won't be lined up with the rest of the text. Also, it looks horrible on mobiles as it goes to the very border of the screen.
-
Don't have rows
<div>s and no columns<div>s. It doesn't really do anything, and you want to have it in rows and columns (see above) -
Close all tags, including
<p>and<div>tags. If you don't, you can mess up the website, even if it doesn't look like there are any bad effects. If you are unsure whether or not you have closed tags, tab everything and you should be able to see if tags aren't close by the amount of indent. -
DO NOT use
<br />or<br>— it is poor practice, and some kind of styling should be used instead. There is an ongoing effort to remove all of them from the site. -
DO NOT rename Wiki pages without asking.
-
Finally, remember to have fun. Its the best part of coding (besides the free food).