Teaching with WordPress (TWP15) is an open, collaborative online course on using WordPress for teaching and learning in higher education. But choosing WordPress as a platform for teaching is only one part of the process in developing an rich, thoughtful, open learning environment.
In a recent blog post , Doug Mckee addresses three issues in how he should teach this fall.
1. Should I ban laptops in lecture?
2. Should I make discussion sections mandatory?
3. Should I cold-call students during lecture?
Basically: no, no and no—all for the same reasons.
1. Should you "ban" anything in lecture?
Or rather: were you to try, what would be the justification?
In teaching we do things for very few reasons.
a. Because they are inherent in the discipline and academic life. "We're reading Durkheim because he helped to found the discipline." "We'll use APA style because that's what professionals do." "You must offer arguments, not opinions, because in our domain, opinions have no value."
b. Because they are convenient. "We need to get all your papers at once so we can compare them and grade them before the next work is due."
c. Because they adhere to university policies and laws. "No smoking in the back row." "Grades are due on the 11th." "No sexual harassment."
d. Because they embody our values about human freedom and responsibility. "You must take up your own argumentative position." "You may turn in the work late, but it will be marked down." "Write about the one topic on the list that interests you most." Pursue your freedom. Experiment. Explore. Fail. But take on the responsibility of existing and choosing.
(I can't think of many other justifications for why we do this, that or the other in teaching.)
And all of these questions are opened to reasoned debate—because that is one of our values.
Once you say "You will not open your laptops," you are dictating. And you have lost. Now you are a cop, not a teacher.
Practically speaking, I know professors who have had good luck with the "three states": put your laptops away and focus on this (discuss with a peer, whatever); open your laptops and do this specific task; leave your laptop open or put it away—I don't care, just don't distract your neighbor.
You can also play with the sequence. If you ask them to use it, then to close it, the act of opening it may be more self-aware.
2. See "1" above.
a. What does "mandatory" mean? Again, from my perspective this is the wrong relation to the student.
We can mandate little in teaching. Rather, we reward and we punish. (Behavioral economics and game theory surely apply here--though I fear that those theories have no moral code embedded in them, and therefore they may be useful tools but they are not arbiters.)
Extrinsic rewards don't motivate learning very well. So you can reward and punish for attending or not. But neither will help students learn.
Why not go the other way? "Go to section, don't. No points for it. Go if you value it. And we'll try to make it valuable." Ask every week how section could be better. Make it a discussion topic in the web site. When you can't decide in advance, make it a learning experience.
b. One good principle in planning teaching is: treat all questions about teaching as something to be proven experimentally by teaching.
Reframe the issue as: What could I learn about making the section worth going to?
Survey students weekly--did you go or not, why? Ask the section leaders to experiment, to explore how best to meet the students' needs. Maybe the first few weeks the sections would have different specific activities that students rated, and thereafter, students chose "which activity should we do today?" Make it their section. Meet their needs.
Or just put super-important things in section. Sell how great section will be, and then say "of course it's totally optional."
3. See "1" above.
a. They are coming to lecture to learn. Would you pick on someone for not having understood the material as well as someone else? That person needs more help, not public shaming.
b. I tried this once. I would never do it again.
I once put the students' names on index cards. I shuffled them and picked one at random.
Once the index cards came out, students sat up straight in their chairs.
I called a name, and the student stammered and hemmed and hawed. Other students tried to rescue those I called on—defended them.
One student shot his hand up later, after not having known the answer to an earlier question, and after class explained to me: "I knew the answer, I just couldn't think of it, and so I had to show you that I'd done the reading."
And I thought: who am I? To make someone prove a point to me?
After that I brought out the index cards and put them on the desk. They were radioactive. Students would stare at them. If no one answered a question, I moved towards the cards, and a voice would ring out with something to say.
It wasn't motivated by something good. But I got good discussions. Not because of randomly calling on students all the time, as a policy. But by making a point that we needed to discuss and that I would do what it took to make that happen. They didn't want that.
But I would never teach that way again.
4. Learning devolves on human agency.
Agency is the center of learning. Through learning, I become more capable, and I feel myself to be more and more of an agent, less and less of a passive, receptive entity and more and more myself.
Humans become more capable by overcoming meaningful challenges in an increasing order of difficulty, a difficulty matched to their abilities. (It's tragedy when someone is outstripped by the task he faces; tragedy defines common humanity by contrast.)
Anything that takes away from the agency of the learner is bad for learning.
Yes, we need rules and limits.
But when possible, all meaningful choices should be passed to the student.
To experience one's humanity through the responsibility of choice, to embrace the possibility of failure, and to own's one's successes: this is the heart of education.
— Edward R. O'Neill, Ph.D.
I am equal parts excited and sad to announce that ITG's Robin Ladouceur will be moving to a new position in the Yale Graduate School as Assistant Dean of Humanities and Social Sciences. Robin has worked in ITG for four years supporting courses, primarily in the English Department and managing our Instructional Innovation Internship program. She has recently helped advance mobile learning initiatives like our iPad loan program. Before coming to ITS, Robin worked at the Yale Center for Language Study and earned her Ph.D. at Yale in Russian Language and Literature.
Robin, thank you for your years of service and we wish you all the best on your return engagement at HGS. On a personal level we will miss you but we'll see you around campus and, as you've assured us, when Peeps Fest rolls around.
Cross-posted from my project journal site
Since the close of classes in May, I've found more time to work on getting into the weeds with my 絵巻物 project and have made some forward motion.
One of my best discoveries has been that Adobe Photoshop CS 5.1 will execute the image tiling needed to allow zooming as happens in most of the typical large image presentations that I've found online. (For some scroll examples, see my post at Digital Humanities Questions and Answers.) Though I've only done it with my proof of concept section of the scroll, it was not a horribly intensive or time-consuming procedure. Strictly speaking, what Adobe has done is to bundle Zoomify capabilities into Photoshop. Using the steps described by Adobe's help documentation, the output is not only the image tiles for my TIFF, Continue reading
The New York Times has just issued the first in a series of articles about "Humanities 2.0: Liberal Arts Meet the Data Revolution."
The article quotes Tom Scheinfeldt, managing director of the Center for History and New Media at George Mason University. Tom will be speaking to Yale's Digital Humanities Working Group this Thursday. The session is open to the Yale public. Please join us!
Tom Scheinfeldt, Assistant Director of the Center for History and New Media
4:00 - 5:00 pm
Whitney Humanities Center, room 208
Having trouble with Apple Automator? Then try Proxi, a free workflow manager that can be downloaded from the Apple website. Automator is Appleâ€™s built in task workflow utility but Proxi is an exceptional alternative. While Automator is useful for standard repetitive tasks such as searching for folder items, moving them to another location, and editing their names, Proxi takes a slightly different approach to setting up workflows. Proxi allows users to link their tasks (similar to the ones in Automator) to "triggers" such as waking the computer from sleep, launching or closing an application/file and many more. Proxi can even recognize when the battery is low and prompt the user to close certain applications that are running. Contrary to Automator in which users must initiate their workflow and tasks, Proxi integrates workflow management into native computer processes and non-user initiated actions.
Proxi must remain open for the triggers and workflows to be recognized but once your workflow has been set up the main window can be closed and Proxi can run silently in the background. Proxi even allows you to save blueprints of your â€œtriggersâ€ and â€œtasksâ€ so that you can open them on another computer. The program is really easy to learn to use and you will even discover neat triggers to launch reminder messages that will display on the screen.
Altogether Proxi is definitely an application to add to your collection of utilities. Follow the link below to download.
While WordPress is a highly accessible platform right out of the box, it is up to the administrators and theme designers to tweak and configure their site to ensure that it is accessible to all users, including the blind, deaf, elderly, or anyone else who might for some reason have difficulty navigating the web.
This post outlines some resources that might prove useful in creating an accessible WordPress site, particularly with regard to sight impairments.
Visually impaired computer users generally use a Screen Reader, such as JAWS, which speaks the website's content using a synthesized voice. Screen Readers speak the content (headings, links, menus, blocks of text) according to the code, so it is up to the theme editor to keep the HTML and PHP clean and ensure that a screen reader can logically process the website's content.
Though a bit outdated, the Web Content Accessibility Guidelines 1.0 provide sound coding guidelines for how to maintain an accessible website. In terms of WordPress themes, it is important to minimize use of tables and to make sure graphics and videos have descriptive alternate text.
The WordPress Accessibility Codex also outlines useful accessibility guidelines unique to the WordPress platform.
WebAnywhere is a free online screen reader that is useful for testing pages. It's also worth trying out just to get a sense for the challenges of navigating the web by ear.
Fangs is a Firefox extension that simulates JAWS reader. Rather than speaking the content, it outputs a text similar to how JAWS would read the page.
More useful accessibility testing resources:
- HiSoftware's Online Content Accessibility and Quality Tester
- Evaluation, Repair, and Transformation Tools for Web Content Accessibility
- W3C Web Accessibility Initiative: Evaluating Websites for Accessibility
- WAVE Online Accessibility Tool Checker
(from WordPress Accessibility Codex)
Useful WordPress Plugins
The WordPress Accessibility Widget is a very useful widget that allows users to easily change the site's font size. The code can be easily tweaked to customize the available font sizes or add additional size options.
The WordPress Access Key Widget is another useful widget that allows the administrator to easily set up access keys for their site. With this plugin, access keys can be assigned for existing pages under "Posts" on the admin interface.
One issue with access keys is that the keyboard commands vary by web browser. For example, Mac Firefox is CTRL+access key, and Mac Safari is CTRL+ALT+access key.
You can see these plugins in action at this test site.
The Arjuna-X theme, which lacks tables, is a highly accessible theme and might be worth testing and tweaking when building an accessible WordPress site.
In this post, I will try to describe my experience with learning how to develop apps for the iPhone, and all other Apple devices using OS X for that matter.
1. What you need to know:
- Objective-C - it is a variation of the C programming language. If you have an year of experience in programming in another language, it should not be a great challenge - although, if the language you are using is not as low level as C, you will want to become familiar with pointers and memory allocation - Programming in Objective-C 2.0 by Stephen Kochan is a good introduction to the language - you will probably still need to look up some things on the internet though.
- Cocoa API and the iPhone SDK - allow you to build the GUI. This is how the code written into Objective-C is made to respond to the touchscreen and look as nice as iPhone apps look. Depending on the project you are working on you will probably want to learn how to access the internet and how to store information in SQLite databases. Sams Teach Yourselves Cocoa Touch Programming is a somewhat good introduction to the topic. At this point, I would definitely recommend watching youtube and blog tutorials, and referring to all other resources and books that you have at your disposal.
2. How to start:
I think it all boils down to the level of complexity of the app you want to create, and the programming background that you have. For Xunzi it helped me a lot to first familiarize myself with Objective-C, and then move on to see how to manipulate the GUI to some extent. Then learn how to work with SQLite (since that is the DB system that OS X uses). Then learn how to make your app get info from the internet.