Archive for February, 2010
That was the hook! Now that your eyeballs are locked in from that snappy post title, I’ll dive into more details as to what I actually mean.
This weekend, starting Friday, February 26th at 5:00pm PST, the community wiki will be set to read-only access. We are going to overhaul the wiki documentation and come out of the weekend with a fresh look at community driven documentation.
Stay tuned to this channel for more exciting documentation news!
Update (February 21, 2010): Site maintenance has been postponed until 2/26. Post details have been updated to reflect this change.
Hey all, my name is Kalid Azad, I’m the new UI Dev for MindTouch!
I got in touch with the company after a tweet regarding a project of mine, which led to an email/call & trip to San Diego to meet the team. San Diego apparently has name-brand sunshine, vs. the generic packaged stuff we get up in Seattle. The team was smart, friendly, down to earth, and it was cool talking about new technologies (git, no SQL style databases) with an atmosphere of curious experimentation. Not every new tech is the right fit, but it’s important to explore the possibilities and know what’s out there.
I’m a fan of MindTouch for a few reasons. First, it’s open source — I’ve worked inside closed corporations, and did a double-take when my first spec was put on a public site. Really? Other people can… read it? Believe it or not, this is mindblowing in other circumstances :). Being able/allowed/encouraged to engage with a community, in the open, from the getgo is really freeing.
Next, I love blogging about math/programming geekery, and was looking for a way to have readers contribute. I like tinkering around with new platforms (tweaking WordPress, etc.) and being able to contribute to a project I’m experimenting with myself is just awesome. I’m keeping a list of little UX features that might be cool on my user page. Comments/feedback/UX ideas are more than welcome.
Last, I like the idea of separating the data (API) from the presentation layer, in that good ol’ MVC pattern. Theoretically, you can have a web interface, gmail-like interface, desktop interface, iphone interface, command-line interface… and it should just all work. Just having the separation gives you the freedom to experiment, which I’m looking forward to doing.
Back to normal now. Looking forward to working with everyone!
With the MindTouch 9.12 release, property search has taken a big (but still experimental) step to being a reality. First a short recap: properties are a way to associate metadata with the various kinds of resources used by MindTouch. Currently there are page, user, attachment, and global site properties. These all share a common API interface but slightly different usage patterns mostly differing in access permissions. Customers and community developers have used it for all sorts of things such as a data store for defect tracking, user workflow state, voting/feedback storage, etc.
Search is a natural progression of properties making them more powerful and effective for building solutions on top of MindTouch. There are a few usage patterns (as described with examples in the property search spec), but the most common will likely be to find pages that have a specific property that is equal to or contains a certain value. As with the page and attachment search currently in MindTouch, property search is implemented in Lucene giving it support for complex logical queries to be performed on the data you choose to store. Properties are only searched when explicitly asked. An example query combining a few concepts looks like:
+#assignedto:max +#priority:[1 TO 5] +#project:[API or DB] -#status:closed +title:"bugs/*"
We’re considering expanding property search to user properties (soon) and attachment properties (later) as well as allowing some user properties to be visible by others. These are discussed in more detail on the property search spec and we’d really appreciate your feedback!