This website uses cookies and similar technologies to understand visitors' experiences. By continuing to use this website, you accept our use of cookies and similar technologies,Terms of Use, and Privacy Policy.

The votes are in, and it looks like I'm going to get to give a presentation as part of WordCamp Boston's Ignite event. Thanks to all who voted! The proposal I gave ...
I was reading this article on Information Architects web site about the features and design strategies IA expects to take hold in the near future. I found the following quote to be especially relevant to the Pressible project and wanted to include it hear as a point of reference. Instead of piling up features, web sites need to become more intelligent. Requiring less input and giving more feedback. Showing less random data and delivering more relevant information. I think this is a ni...
Marathon meeting today! Eric and Patrick have been working on NSSE and another "special" project for the past few days which are finally winding down today. It was great for us to collectively turn our attention back to Pressible and revisit our original intentions for the platform and theme. First off, we're still slated for a January 22nd release. The guys managed make a few style changes to the special Pressible project which will rollover into the entire development, including fixing problems with paragraph separations, header sizes, and author metadata. They've also w...
I'm a fan of symlink-type deployment scripts such as Capistrano, which is in heavy use in Pressible. It's not perfect, but it's how we deploy most of our non-MU code (plugins, themes, etc.). The basic premise of these scripts is that code is copied from your SCM system into a staging directory, and once everything checks out, a symlink is replaced to make the new code active. Any web server pointed at said code will then always be accessing a path that includes at least one symlink. If you are using ...
I just changed the site name from "Project Lab" to "Pressible Progress"--which I'm not in love with (not very catchy, and I'm kind of sick of alliteration) but it says more about our focus on Pressible and its derivative themes than our initial take on the theme formerly known as "ProjectPress." I'm changing our About information to align with the Pressible.org information and with a general scope of our work as it has developed up to this point.
WordPress 2.9 was released at the end of last week and has some features that are worth noting. Here is the WP blog post about the release. From a user's perspective: A simple image editor is now built into the post interface. It allows for users to crop, rotate, and scale their images. This seems like a great tool to have to be serving large user bases. WordPress now uses oEmbed which allows users to simply paste a video url( http://www.youtube.com/thisawesomevideo) and have the url converted to a ...
Here's some of our thinking around the data we'll be collecting from Pressible use and users: Learning Applications - Use/data creates more powerful learning tools - "User metrics" will encourage people to use the system - Giving users data about what they're doing will push them to do more - Data makes the site game-y: by adding competitiveness, the ability to affect order, and personal ownership, people will want to "play" more Research Applications - Show what we're learning about how TC people act and use the site - General metrics (frequency, length of ...
We've been thinking about our Terms of Service, and how they are going to promote Pressible while also protect us and TC from the apparent liabilities of hosting non-TC content on TC servers. Here are some of our thoughts: - When new users register, we ask them to self-identify as either "TC" or "Other." This will help us prioritize queries, evaluate opportunities for collaboration, and give us valuable data about site usage. - The ToS will explain deferential treatment of TC projects over non-TC projects, including but not limited to service requests, specialization, and our responsibility ...
We've been lucky enough to have a few conversations with potential Pressible users/clients. To get them onboard with us, we've shown them our (unfinished) pre-beta sites which, in turn, raised questions for them and us. The specific "what ifs" we've been considering are: 1. What if you have a lot of content that you want to input initially (e.g. what would otherwise be static content on a "regular" site) 2. What if you only have one user? 3. How do we help people who want the functions of a blog, but are averse to having "a blog"? We have tried to answer these questions by splitting up our ...
Eric and Patrick are currently on the other side of our desk-island trying to figure out how separate child categories from their parent categories and display posts from child categories while having the option to hide/show the parent category. Or something. We had a meeting today, and I'll be writing up specific parts of our conversation, but here's the gist of things: - There's been a split and we now have Pressible and Pressible Simple (details forth coming) - Patrick and Eric are working on the Pressible Simple theme for functional release next week - The proper Pressible theme (ProjectP...