brief
Brief: Last Class
Next week we’re done.
The class will be broken into 3 parts:
- Final Open Source projects presentations.
- Wrapping up the semester. (prepare to give me some honest feedback)
- Final debate on the Olympics, political engagement and national agency (if we have time)
- + Some treats to go with it
For the presentation part I want each of you to prepare a presentation which you will rehearse as a group before class. In your presentation you will:
- Present your study of the project you chose – what is it good for, who uses it? what other proprietary or non proprietary competition does it have
- What was the process of design in this project prior to your participation? how are decisions being made? How involved is the discussion of interface design in the development process?
- What is your contribution?
- Step by step presentation of the design proposals
- Summary of the process, the communication with the community/developers, how welcoming was/n’t it? What worked? What didn’t?
- How do you see your involvement in the project after the end of the class?
- More if you decide more is relevant.
You are welcomed to upload designs to the blog for feedback this week.
Good luck and see you on Friday.
Brief: Show them what you’ve got…
Main focus this week – bring your designs to the point where you actually show the community members what you came up with. This means:
- By Saturday night: Post the comments you got in class to your posts
- By Tuesday noon: Post new designs to be sent to your project’s mailing list / IRC / Forums / developers emails… This would be a draft of your actual communication (write a draft of your email or post as a part of the design)
- By Wednesday night: Work on the feedback you got to your post (design and language)
- For Friday: Hopefully present us some feedback from the community
Next week we will also want to see your blogs ready to be launched. No reason why not to. If you’re running into problems, use the list.
Brief: Archive page + Design your OS project
We are pretty close to the end of the semester (two weeks). For next week you will need to present your proposed design for the OS project you chose as your subject in this form:
- Show us a step-by-step user scenario in the existing system (if available)
- Show us your proposed step-by-step through a series of designs (Photoshop mockups)
This week will include mid-week deadlines:
- Continue your research of the community and its dynamics along the lines of the previous briefs
- By Monday night: Post one mockup presenting the main aspect of your design contribution.
- By Tuesday night, comment on every post made to the blog by your fellow students
- By Friday morning post the two user scenarios
- By Friday morning post a strategy of contacting the community with your proposed designs (we will try to make that contact in the following week)
- Through the week continue your theme like we have in the past couple of weeks. After the single.php page move to archive.php. Use the technique of reading the tags in the code, and then searching them in the outputted html through Firebug. That’s the best way to address the changes in the php files and to change the design through CSS. (and as always using the list helps)
Lots of work, the semester is almost done…
Happy Passover!
Brief: Blog pages + interaction design report
We continue in the two fold development – blog theme + OSD project:
- Come up with proposals for change in the form of an information architecture and a set of proposals
- Make draft for the first email you’ll send the list/individual developers involved in the project
- Continue your research and comment on the process of design that has been done in the project so far.
And on the theming end – work on the singular.php page, try to finish it by next week.
And again, if you’re stuck, use the mailing list. If you learned a cool trick and want to share, use the mailing list. If somebody got stuck and you think you might be able to help, use the mailing list.
Enjoy.
Brief: Reports from you OSD project + Mainpages
I want to start switching gears towards the final assignment. So each one of you should post about your progress with your OS project of choice:
- Sign up to the development mailinglist of the project
- Tell us who are the leading figures
- What are the leading issues
- Try to search for ‘design’ and ‘interface’ as a keyword in the discussion. What were the discussions around it, where did they lead? Are there already interface designers involved? How do proposals appear on the list? Is there a discussion? Do people meet in person?
- Is there a development blog? A forum? Where is the development taking place
- When you get to the step of introducing yourself / offering help, what do you think will be the best way to do that?
- Based on what you’ve learned so far and the feedback you got in class, what do you think can be your contribution to the project?
- Write all of these assessments in a post by Thursday, April 10th, 8pm.
I think we made some progress in the workshop yesterday and I want to be done with the main page by next week, so we need to still keep up the pace. Let’s break it down again:
By Tomorrow, April 5th, noon:
- Post a comment to your posts summing the feedback you got in class.
- Post at least three more comments to two of your fellow students.
By Tuesday, April 8th, noon:
- Submit a link to your blog with the header.php and footer.php index.php & sidebar.php implemented according to your design (in other words – the main page – ready) Like last week, with this link post a screenshot of the page too (it will be important for the documentation of your process)
By Wednesday, April 9th, noon:
- Post at least 4 comments to your fellow students on what they posted.
By Thursday, April 10th, 8pm:
- Post the link + screenshot of your main page, done. (by Friday next week your main page should be ready for critique as a WP theme).
And again, if you’re stuck, use the mailing list. If you learned a cool trick and want to share, use the mailing list. If somebody got stuck and you think you might be able to help, use the mailing list.
Enjoy.
Brief: Theming the main page
Based on the tutorial I gave in class today, I want you to build the main page for your blog. I also want it to be done by next week, so we need to step up the pace. Let’s break it down:
By Tomorrow, March 29th, noon:
- Post a comment to your posts summing the feedback you got in class.
- Post at least three more comments to two of your fellow students.
By Tuesday, April 1st, noon:
- Submit a fixed html/css layout for the main page based on the feedback you got in class.
- Submit a link to your blog with the header and footer implemented according to your design (if you made more progress, then by all means, share it, but if not, that will do for now) With this link post a screenshot of the page too (it will be important for the documentation of your process)
By Wednesday, April 2nd, noon:
- Post at least 4 comments to your fellow students on what they posted.
- And drop by to see my § presentation at Dorkbot that night.
By Thursday, April 3rd, 8pm:
- Post the link + screenshot of your main page, done. (by Friday next week your main page should be ready for critique as a WP theme).
If you’re stuck, use the mailing list. If you learned a cool trick and want to share, use the mailing list. If somebody got stuck and you think you might be able to help, use the mailing list.
Enjoy.
Brief: Theming on
The next two weeks are broken to two parts.
Part One:
- Get the HTML+CSS of your main page done before next Friday (March 21st) and post the link to our blog. with a reference to the design made in photoshop (upload a png image to your post).
- Comment on every post made to the blog with your feedback, we need to start helping each other so we make some more progress.
- Post about three open source projects you are thinking of contributing to as your final assignment (the contribution can be any form of design, from interface design, through web design, through icon design to logo, banners, stickers, posters and t-shirts designs)
Part Two (for next class, March 28th):
- Break the design into header, footer, main.php, sidebar and so on… and try to turn it into a theme based on the Sandbox theme.
- Read Eric Steven Raymond’s The Cathedral And The Bazaar. It might help your approach to the development of your blog and we will have a discussion on the book after the break.
- Write a post about the open source project you chose to contribute to as a designer. Try to lay out the ways in which you envision your contribution taking place.
In two weeks from now we’re all going to be theming like there’s nothing to it. please release early, release often meaning, try to post your progress on our blog or mailing list, remember, Given enough eyeballs, all bugs are shallow. If you run into problems let us know, we’ll try to crack it together, promise!
Brief: We’re theming!
Thanks Michael!
Over the next two weeks we will start making our themes. Starting from design, through HTML/CSS and further through Wordpress. You’re going to have two main deadlines over the next two weeks:
By Tuesday, March 3th:
- Upload the Photoshop designed mainpage of your blog. Based on the way you defined it for today (purpose, inspiration and so on)
Rather than using only html/css elements, try to think how background images can help you spice up your design, check CSS Zen Garden (and others) for inspiration. Use Firebugs to check how things are done behind the scenes. - Comment on at least 3 posts by other students (if you post early you get more feedback, so start working this weekend)
- Try installing themes on your blog and look through their structure
- Install the Sandbox-BP theme into your wp-content/themes folder, turn it on, play around with it.
By Friday, March 7th:
- Upload the revised design for your blog based on the feedback you got from your classmates.
- Start writing your extend.css file to add to the default styling
By Tuesday, March 11th:
- Post a link to your blog with your own design starting to be implemented and with questions and tips about building a theme
- Use our discussion list to flag issues and questions to the rest of us (by all means don’t wait for the last moment)
- Comment on other’s posts and questions
For our next class Friday, March 14th:
- Try to have your main blog page as close to completion as possible.
Enjoy!
thanks again Michael!
see you in two weeks,
Mushon
Brief: Finish the tutorial, start thinking of a blog
Hi Class.
Next week I will unfortunately not be with you, I will be replaced by Michael Mandibeg, a new media artist, design educator and web developer who will be introducing you to the behind the scenes of WordPress.
We will give our tutorial another week so we can feel good about moving to the next assignment and knowing we have learned some CSS while we were at it. We will also setup our hosting plan and install Wordpress. And we’ll also start research towards our final project involving infiltrating a real open source project and giving our Graphic Eye for the Open Source Guy.
So:
- If you still need to, finish your tutorial CSS layout. Use the Blueprint mailinglist and our mailing list to bounce ideas instead of slamming your head agains the keyboard.
- Choose the theme for your Wordpress theme:
- What kind of blog is it? (if it’s even a blog…)
- Who is it for?
- What are the functions it should fulfill?
- Pick three inspiration sources one for content, one for structure and one for presentation.
- Go theme hunting through the thousands of free-software themes out there on the internet. Post three of them to our blog in the form of a thumbnail + a links to the theme page.
- Install the The latest Wordpress release on your site:
- Follow the one click install id you’re on any of these (and others) that provide it.
- Or the step by step 5 minute install tutorial on Wordpress.org or the visual tutorial over here.
- Next week Michael will show you around the nuts and bolts of Wordpress, so make sure you’re prepared.
- Start searching for an open source project to contribute to.
Tutorial: More design, More Blueprint, More CSS (final)
Now that we got some initial experience with Blueprint let’s dive a bit more into it.
- First of all I would like you to subscribe to the Blueprint CSS mailing list where you can both ask some questions when you run into difficulties, learn from other people’s experience, and yes, one day also help others with their BP & CSS questions…
- Second, go back to your PSD file and make changes to it based on the feedback you got in class.
- Third, fix your css grid if it need any more fixing and go straight into all the details, styling all the graphic and typographic elements in the page including :hover states, images and all. Feel free to steal take inspiration on other html/css design you find online. Visit the html validator every now and then, and try to see what you can learn from it.
- Post at least once to the blog this week with a tip for the rest of us, some cleverway you found of doing something or even a problem you have that you want us to help you solve. Please post before Tuesday 11:59pm.
- Buy a domain name for yourself and a hosting space that supports PHP 4+5 and preferably also provides one-click install for Wordpress. You are welcomed to do your own research and compare your results on the blog and through our del.icio.us tag OSDP.
* Personally, I can recommend Dreamhost which (even though lately they’ve been pretty bad with downtimes) are still a good bang for your buck (they host most of my site, and I have yet not moved). Anyway, I have arranged a serious discount for you so if you register through this link and entering our promotion code:OSDor by mentioning my email as a referrer (disclaimer: it’s a win-win referrer program so I am benefiting from your discount too).
- The final links to your works should already be hosted on your own sites.
- If any of you have technical (or other) problems with this assignment, or want to consult me on anything, please email me.
(don’t wait for the last moment with it)
on 
on 
on 
