« October 2006 | Main | December 2006 »
Structure your podcast episode content and plan your recording session
1. Plan what you’ll say in the episode intro and outro, and what you want to cover in each segment.
2. Record a podcast intro that says who you are and what your podcast is about.
3. Record an episode intro that describes the topics you’ll cover today.
4. Record a few informative segments.
5. Record a short "outro" to sign off at the end.
6. After you’re finished recording, you can use GarageBand jingles to spice up your podcast. Try using the same jingle every episode after your podcast intro. You can also use jingles as "bumpers" between segments, and again after your outro.
Use the following for guidance in creating your Pocket Puzzle documentation:
Statement of Problem
"Children often get bored on long car journeys and don't like looking out of the window. There is a need to create a toy for children that will keep them engaged on trips."
Design Brief
"There is a need for a steady hand game, suitable for children aged under 12 years old. It should be packaged for sale at convenience stores, garages or supermarkets."
Click below to continue reading...
Specification
A Specification is a list of key points and/or constraints that designs must take account of. The specification is written after the design brief has been analysed and research has been carried out. The specification can be written using different headings as a guide:
Sketches
You will need to supplement your documentation with three sketches of your toy:
- Your game must be 100mm by 100mm
- Show where the holes might go and include any "bumpers"
- You should have one sketch in isometric and one in oblique
Blister Pack design
You are going to make a Blister pack for your game. Blister packs are used to package a wide range of products and combine a practical, hardwearing package with space to promote the product.Blister Pack Specification:
List all the graphic design elements that should be included on the cardboard backing. Eg: Eye-catching, colourful, must have a barcode etc. You should have no fewer than ten items in your list.Package Design
You will need to complete two designs for the package for your game. They should be of good quality and fully rendered.Evaluation
An evaluation gives the opportunity to see what you have achieved and test out the product. It also gives the chance to see what went wrong and suggest improvements.
- Explain how you have met the Brief/Specification
- List four ways you could test your product
- Carry out one of the tests and explain what happened
- Did you enjoy the project
- What could you have done to make the project more enjoyable?
- How would you improve on your design?
Middle School students: We should be nearing the end of our projects soon (Pocket Puzzle, Steadyography, Flying Toy). You will need to make sure that your written documentation is complete and in your design folders by no later than Friday, November 24th. This will include:
A detailed list of the documentation requirements is available here.
By now the majority of Middle School students will have an HTML document with code resembling the following:
<html>
<head>
<link rel="stylesheet" type="text/css" href="style.css">
</head>
<body>
<div id="header">
<h1>Toy Website</h1>
</div>
<div id="menu">
<ul>
<li><a href="#">Home</a></li>
<li>Gallery</li>
<li>Contact</li>
</ul>
</div>
<div id="placeholder">
<img src="image.jpg" />
</div>
<div id="blockquote">
<blockquote>The toy you've all been waiting for has finally arrived!</blockquote>
</div>
<div id="block">
<h2>Why Our Toy Is The Best</h2>
<h3>We Know Toys</h3>
<p>Our space-age toy was lovingly handcrafted by Aleutean monks....</p>
</div>
</body>
</html>
Read on to find out more on how you should be finishing off the formatting of your HTML pages...
You'll notice that the one element you haven't yet added to your pages are these lines:
<head>
<link rel="stylesheet" type="text/css" href="style.css">
</head>
Those lines call an external CSS file (a style sheet). That fine will contain all the information about the style of our document. The HTML page is responsible for containing the content. So, HTML (content) + CSS (style) = a readable web page across many platforms and browsers.
CSS is coded slighty differently from HTML, like this:
body {
background: black;
font-family: "Curlz MT", Verdana;
font-size: 14px;
color: white;
}
div#header {
background: #00FFFF;
text-align: center;
}
h1 {
color: yellow;
}
The code above will change any h1 (header level 1) tags you have in your HTML document to green text. Think of how you can use CSS to style your document.
Links that will aid you:
- Webmonkey HTML Cheatsheet
- Webmonkey CSS Reference
- Webmonkey CSS Examples
- Our southbank.net stylesheet
Remember: stylesheets and images will not work in this particular example unless they live in the same folder as the HTML file.
