"
Team:Cornell/testing/notebook/drylab/5
From 2012.igem.org
(Difference between revisions)
DanVLevine (Talk | contribs) |
DanVLevine (Talk | contribs) |
||
| Line 63: | Line 63: | ||
</dd> | </dd> | ||
<dd> | <dd> | ||
| - | <a href="#pillTab2"> | + | <a href="#pillTab2">Details</a> |
</dd> | </dd> | ||
<dd> | <dd> | ||
| Line 89: | Line 89: | ||
Focus: Notebook Section of the Website<p></p> | Focus: Notebook Section of the Website<p></p> | ||
| - | The student engineer’s solution to an engaging, well-organized blog? Hashtags. <a href="#" class="technical-desc" for="#technical-desc1" style="display:block;margin-top:20px;"> | + | The student engineer’s solution to an engaging, well-organized blog? Hashtags. <a href="#" class="technical-desc" for="#technical-desc1" style="display:block;margin-top:20px;">Details</a> |
<div class="hide-me panel" style="background:white;margin-top: 20px;" id="technical-desc1"> | <div class="hide-me panel" style="background:white;margin-top: 20px;" id="technical-desc1"> | ||
| - | <h6> | + | <h6>Entry:</h6> |
This afternoon, Dan organized a dry lab meeting focused mostly on the team website. Most of us met our main website designer Eric for the first time today. Tall, skinny and pale, Eric was not timid when it came to voicing his opinions about the website layout. His professionalism and grasp on modern style convinced us that he was the right person to spearhead the construction of our new website.<p></p> | This afternoon, Dan organized a dry lab meeting focused mostly on the team website. Most of us met our main website designer Eric for the first time today. Tall, skinny and pale, Eric was not timid when it came to voicing his opinions about the website layout. His professionalism and grasp on modern style convinced us that he was the right person to spearhead the construction of our new website.<p></p> | ||
The subteam discussed the format of the website’s “notebook” section. An ensuing heated debate led us to reevaluate the purpose of the notebook. We drew inspiration primarily from DTU and Imperial College London’s iGEM websites. And we finally agreed that the notebook should be more than a log of activities and should be lean closer toward a blog, conveying information in an engaging, well-organized manner. The notebook would be divided into two general categories: biological and mechanical--each category further dividing into detailed sections (such as naphthalene or chassis design). We decided to emphasize structure with the use of hashtags. Ultimately, entries would start with the date and an interesting one-sentence overview, briefly narrate the day’s events, and end with relevant hashtags.<p></p> | The subteam discussed the format of the website’s “notebook” section. An ensuing heated debate led us to reevaluate the purpose of the notebook. We drew inspiration primarily from DTU and Imperial College London’s iGEM websites. And we finally agreed that the notebook should be more than a log of activities and should be lean closer toward a blog, conveying information in an engaging, well-organized manner. The notebook would be divided into two general categories: biological and mechanical--each category further dividing into detailed sections (such as naphthalene or chassis design). We decided to emphasize structure with the use of hashtags. Ultimately, entries would start with the date and an interesting one-sentence overview, briefly narrate the day’s events, and end with relevant hashtags.<p></p> | ||
| Line 106: | Line 106: | ||
<h3>Monday</h3> | <h3>Monday</h3> | ||
BRIEFINGS | BRIEFINGS | ||
| - | <a href="#" class="technical-desc" for="#technical-desc7" style="display:block;margin-top:20px;"> | + | <a href="#" class="technical-desc" for="#technical-desc7" style="display:block;margin-top:20px;">Details</a> |
<div class="hide-me panel" style="background:white;margin-top: 20px;" id="technical-desc7"> | <div class="hide-me panel" style="background:white;margin-top: 20px;" id="technical-desc7"> | ||
| - | <h6> | + | <h6>Entry:</h6> |
ALLTHEDETIALS | ALLTHEDETIALS | ||
</div> | </div> | ||
| Line 120: | Line 120: | ||
<h3>Tuesday, July 3, 2012</h3> | <h3>Tuesday, July 3, 2012</h3> | ||
BRIEFINGS | BRIEFINGS | ||
| - | <a href="#" class="technical-desc" for="#technical-desc2" style="display:block;margin-top:20px;"> | + | <a href="#" class="technical-desc" for="#technical-desc2" style="display:block;margin-top:20px;">Details</a> |
<div class="hide-me panel" style="background:white;margin-top: 20px;" id="technical-desc2"> | <div class="hide-me panel" style="background:white;margin-top: 20px;" id="technical-desc2"> | ||
| - | <h6> | + | <h6>Entry:</h6> |
ALLTHEDETIALS | ALLTHEDETIALS | ||
</div> | </div> | ||
| Line 134: | Line 134: | ||
<h3>Wednesday</h3> | <h3>Wednesday</h3> | ||
BRIEFINGS | BRIEFINGS | ||
| - | <a href="#" class="technical-desc" for="#technical-desc3" style="display:block;margin-top:20px;"> | + | <a href="#" class="technical-desc" for="#technical-desc3" style="display:block;margin-top:20px;">Details</a> |
<div class="hide-me panel" style="background:white;margin-top: 20px;" id="technical-desc3"> | <div class="hide-me panel" style="background:white;margin-top: 20px;" id="technical-desc3"> | ||
| - | <h6> | + | <h6>Entry:</h6> |
ALLTHEDETIALS | ALLTHEDETIALS | ||
</div> | </div> | ||
| Line 148: | Line 148: | ||
<h3>Thursday</h3> | <h3>Thursday</h3> | ||
BRIEFINGS | BRIEFINGS | ||
| - | <a href="#" class="technical-desc" for="#technical-desc4" style="display:block;margin-top:20px;"> | + | <a href="#" class="technical-desc" for="#technical-desc4" style="display:block;margin-top:20px;">Details</a> |
<div class="hide-me panel" style="background:white;margin-top: 20px;" id="technical-desc4"> | <div class="hide-me panel" style="background:white;margin-top: 20px;" id="technical-desc4"> | ||
| - | <h6> | + | <h6>Entry:</h6> |
ALLTHEDETIALS | ALLTHEDETIALS | ||
</div> | </div> | ||
| Line 162: | Line 162: | ||
<h3>Friday, July 6, 2012</h3> | <h3>Friday, July 6, 2012</h3> | ||
BRIEFINGS | BRIEFINGS | ||
| - | <a href="#" class="technical-desc" for="#technical-desc5" style="display:block;margin-top:20px;"> | + | <a href="#" class="technical-desc" for="#technical-desc5" style="display:block;margin-top:20px;">Details</a> |
<div class="hide-me panel" style="background:white;margin-top: 20px;" id="technical-desc5"> | <div class="hide-me panel" style="background:white;margin-top: 20px;" id="technical-desc5"> | ||
| - | <h6> | + | <h6>Entry:</h6> |
ALLTHEDETIALS | ALLTHEDETIALS | ||
</div> | </div> | ||
| Line 176: | Line 176: | ||
<h3>Saturday, July 7, 2012</h3> | <h3>Saturday, July 7, 2012</h3> | ||
BRIEFINGS | BRIEFINGS | ||
| - | <a href="#" class="technical-desc" for="#technical-desc6" style="display:block;margin-top:20px;"> | + | <a href="#" class="technical-desc" for="#technical-desc6" style="display:block;margin-top:20px;">Details</a> |
<div class="hide-me panel" style="background:white;margin-top: 20px;" id="technical-desc6"> | <div class="hide-me panel" style="background:white;margin-top: 20px;" id="technical-desc6"> | ||
| - | <h6> | + | <h6>Entry:</h6> |
ALLTHEDETIALS | ALLTHEDETIALS | ||
</div> | </div> | ||
| Line 295: | Line 295: | ||
The student engineer’s solution to an engaging, well-organized blog? Hashtags. | The student engineer’s solution to an engaging, well-organized blog? Hashtags. | ||
<div class="panel" style="background:white;margin-top: 20px;"> | <div class="panel" style="background:white;margin-top: 20px;"> | ||
| - | <h6> | + | <h6>Entry:</h6> |
This afternoon, Dan organized a dry lab meeting focused mostly on the team website. Most of us met our main website designer Eric for the first time today. Tall, skinny and pale, Eric was not timid when it came to voicing his opinions about the website layout. His professionalism and grasp on modern style convinced us that he was the right person to spearhead the construction of our new website.<p></p> | This afternoon, Dan organized a dry lab meeting focused mostly on the team website. Most of us met our main website designer Eric for the first time today. Tall, skinny and pale, Eric was not timid when it came to voicing his opinions about the website layout. His professionalism and grasp on modern style convinced us that he was the right person to spearhead the construction of our new website.<p></p> | ||
The subteam discussed the format of the website’s “notebook” section. An ensuing heated debate led us to reevaluate the purpose of the notebook. We drew inspiration primarily from DTU and Imperial College London’s iGEM websites. And we finally agreed that the notebook should be more than a log of activities and should be lean closer toward a blog, conveying information in an engaging, well-organized manner. The notebook would be divided into two general categories: biological and mechanical--each category further dividing into detailed sections (such as naphthalene or chassis design). We decided to emphasize structure with the use of hashtags. Ultimately, entries would start with the date and an interesting one-sentence overview, briefly narrate the day’s events, and end with relevant hashtags.<p></p> | The subteam discussed the format of the website’s “notebook” section. An ensuing heated debate led us to reevaluate the purpose of the notebook. We drew inspiration primarily from DTU and Imperial College London’s iGEM websites. And we finally agreed that the notebook should be more than a log of activities and should be lean closer toward a blog, conveying information in an engaging, well-organized manner. The notebook would be divided into two general categories: biological and mechanical--each category further dividing into detailed sections (such as naphthalene or chassis design). We decided to emphasize structure with the use of hashtags. Ultimately, entries would start with the date and an interesting one-sentence overview, briefly narrate the day’s events, and end with relevant hashtags.<p></p> | ||
| Line 311: | Line 311: | ||
BRIEFINGS | BRIEFINGS | ||
<div class="panel" style="background:white;margin-top: 20px;"> | <div class="panel" style="background:white;margin-top: 20px;"> | ||
| - | <h6> | + | <h6>Entry:</h6> |
ALLTHEDETIALS | ALLTHEDETIALS | ||
</div> | </div> | ||
| Line 324: | Line 324: | ||
BRIEFINGS | BRIEFINGS | ||
<div class="panel" style="background:white;margin-top: 20px;"> | <div class="panel" style="background:white;margin-top: 20px;"> | ||
| - | <h6> | + | <h6>Entry:</h6> |
ALLTHEDETIALS | ALLTHEDETIALS | ||
</div> | </div> | ||
| Line 337: | Line 337: | ||
BRIEFINGS | BRIEFINGS | ||
<div class="panel" style="background:white;margin-top: 20px;"> | <div class="panel" style="background:white;margin-top: 20px;"> | ||
| - | <h6> | + | <h6>Entry:</h6> |
ALLTHEDETIALS | ALLTHEDETIALS | ||
</div> | </div> | ||
| Line 350: | Line 350: | ||
BRIEFINGS | BRIEFINGS | ||
<div class="panel" style="background:white;margin-top: 20px;"> | <div class="panel" style="background:white;margin-top: 20px;"> | ||
| - | <h6> | + | <h6>Entry:</h6> |
ALLTHEDETIALS | ALLTHEDETIALS | ||
</div> | </div> | ||
| Line 363: | Line 363: | ||
BRIEFINGS | BRIEFINGS | ||
<div class="panel" style="background:white;margin-top: 20px;"> | <div class="panel" style="background:white;margin-top: 20px;"> | ||
| - | <h6> | + | <h6>Entry:</h6> |
ALLTHEDETIALS | ALLTHEDETIALS | ||
</div> | </div> | ||
| Line 376: | Line 376: | ||
BRIEFINGS | BRIEFINGS | ||
<div class="panel" style="background:white;margin-top: 20px;"> | <div class="panel" style="background:white;margin-top: 20px;"> | ||
| - | <h6> | + | <h6>Entry:</h6> |
ALLTHEDETIALS | ALLTHEDETIALS | ||
</div> | </div> | ||
Revision as of 07:48, 3 October 2012
Week 5
-
Sunday, July 1, 2012
Focus: Notebook Section of the Website The student engineer’s solution to an engaging, well-organized blog? Hashtags. DetailsMonday
BRIEFINGS DetailsTuesday, July 3, 2012
BRIEFINGS DetailsWednesday
BRIEFINGS DetailsThursday
BRIEFINGS DetailsFriday, July 6, 2012
BRIEFINGS DetailsSaturday, July 7, 2012
BRIEFINGS Details -
Sunday, July 1, 2012
This afternoon, Dan organized a dry lab meeting focused mostly on the team website. Most of us met our main website designer Eric for the first time today. Tall, skinny and pale, Eric was not timid when it came to voicing his opinions about the website layout. His professionalism and grasp on modern style convinced us that he was the right person to spearhead the construction of our new website. The subteam discussed the format of the website’s “notebook” section. An ensuing heated debate led us to reevaluate the purpose of the notebook. We drew inspiration primarily from DTU and Imperial College London’s iGEM websites. And we finally agreed that the notebook should be more than a log of activities and should be lean closer toward a blog, conveying information in an engaging, well-organized manner. The notebook would be divided into two general categories: biological and mechanical--each category further dividing into detailed sections (such as naphthalene or chassis design). We decided to emphasize structure with the use of hashtags. Ultimately, entries would start with the date and an interesting one-sentence overview, briefly narrate the day’s events, and end with relevant hashtags. #website #notebook #hashtagMonday
ALLTHEDETIALSTuesday, July 3, 2012
ALLTHEDETIALSWednesday
ALLTHEDETIALSThursday
ALLTHEDETIALSFriday, July 6, 2012
ALLTHEDETIALSSaturday, July 7, 2012
ALLTHEDETIALS -
Sunday, July 1, 2012
Focus: Notebook Section of the Website The student engineer’s solution to an engaging, well-organized blog? Hashtags.Entry:
This afternoon, Dan organized a dry lab meeting focused mostly on the team website. Most of us met our main website designer Eric for the first time today. Tall, skinny and pale, Eric was not timid when it came to voicing his opinions about the website layout. His professionalism and grasp on modern style convinced us that he was the right person to spearhead the construction of our new website. The subteam discussed the format of the website’s “notebook” section. An ensuing heated debate led us to reevaluate the purpose of the notebook. We drew inspiration primarily from DTU and Imperial College London’s iGEM websites. And we finally agreed that the notebook should be more than a log of activities and should be lean closer toward a blog, conveying information in an engaging, well-organized manner. The notebook would be divided into two general categories: biological and mechanical--each category further dividing into detailed sections (such as naphthalene or chassis design). We decided to emphasize structure with the use of hashtags. Ultimately, entries would start with the date and an interesting one-sentence overview, briefly narrate the day’s events, and end with relevant hashtags. #website #notebook #hashtagMonday
BRIEFINGSEntry:
ALLTHEDETIALSTuesday, July 3, 2012
BRIEFINGSEntry:
ALLTHEDETIALSWednesday
BRIEFINGSEntry:
ALLTHEDETIALSThursday
BRIEFINGSEntry:
ALLTHEDETIALSFriday, July 6, 2012
BRIEFINGSEntry:
ALLTHEDETIALSSaturday, July 7, 2012
BRIEFINGSEntry:
ALLTHEDETIALS
