Bridging users & manuals creatively
Enter your email address above to be alerted when doQer goes live!

Posts Tagged ‘HTML’

New Feature: Edit and Create Manuals From Within doQer

Thursday, August 13th, 2009

Running the initial Beta trials of doQer hasn’t taken up all of our attention recently; we’ve also been working hard on adding a major new piece of functionality to the system. Whereas up until now users have only been able to put an existing manual into doQer, we’re now implementing the functionality required for users to actually edit their manuals from within doQer, and even create new manuals from scratch.

This capability represents a major piece of the jigsaw in making doQer a really useful application, and it has always been in our roadmap to implement, but it’s complex to achieve from a technical perspective. Embarking upon it, there were some key objectives that we wanted to achieve:

Version Control
It should be possible for users to revisit previous edits, compare, and revert to previous versions of the manual.

Easy Formatting
Writing the manual should not need extensive knowledge of a mark-up language. It should be easy, allowing users to put ideas down quickly to create a manual.

Media Manager
Uploading and including images in a manual must be easy and quick.

The more we thought about these requirements, the more it seemed that integrating a Wiki engine would do the trick. Wikis are flexible and powerful, and most importantly allow us to work with existing, stable code without reinvent the wheel!

Settling on a Wiki engine was difficult given the large number of options available. Luckily we found WikiMatrix, a really useful site that let’s you enter what you are looking for in a Wiki and then gives you a couple of options to try.

In the end we decided to go with DokuWiki:

DokuWiki is a standards compliant, simple to use Wiki, mainly aimed at creating documentation of any kind. It’s targeted at developer teams, workgroups and small companies. It has a simple but powerful syntax which makes sure the datafiles remain readable outside the Wiki and eases the creation of structured texts. All data is stored in plain text files – no database is required.

DokuWiki has all the features we need, and the syntax is perfect in it’s simplicity. The software is Open Source and lightweight, so we were able to modify it to integrate with doQer’s current features. It also keeps the manuals as text files, so from a development perspective it eases the difficulties of managing lots of database tables!

Once the new functionality is implemented, as well as allowing full authoring capabilities from within the browser, authors will benefit from complete version tracking that will enable them to see exactly what changes have been made to each document. It will even be possible to view older versions of the manual and compare differences. Basically, complete wiki-style version control will be available for every manual stored in doQer.

We’re really excited to be rolling out the new functionality. Beta trial participants will be seeing it very soon now…

doQer is hiring!

Thursday, June 4th, 2009

We are looking for an HTML/CSS developer to help us convert PDF documents into standards-compliant HTML files for an exciting new web application.

We will provide an HTML template structure for you to follow, and a user manual in PDF format. You will convert the manual, either manually or using automated tools, into well-formatted HTML.

Applicants should:
- Be conversant in HTML and CSS
- Have experience working with HTML templates (please provide examples of previous work if possible)
- Posses good attention to detail

Interested applicants are welcome to e-mail us at jobs@doqer.com.

Homepage Designs Have Arrived!

Wednesday, April 29th, 2009

It’s an exciting day here at doQer HQ as we’ve just received the final design for the doQer homepage, created by the insanely talented Winnie Lim. I’ve worked with Winnie on a few different projects now and every time she’s exceeded expectations. We’re really pleased with the look and feel of the new homepage - classy and elegant!

Only the homepage has been designed so far. Obviously the same “look and feel” will be used throughout the site, but the sub-page designs haven’t been created yet as not all of the functionality has been finalised. We’ll get round to that soon, but in the mean time here’s a run down of how we arrived at the current design.

First of all, we sent a (very vague!) design brief to Winnie. Here’s an excerpt:
“we’ll be hosting user manuals that might contain their own graphics, artwork etc, so it’s quite important that the colour-scheme of our site (which will appear around the edge of the user manuals) is neutral enough not clash with lots of different stylistic elements, but also stands out enough to be noticeable as a distinct part of the page (what an impossible request! - sorry!)”

We also created a very rough mockup in PowerPoint:

design brief

With only our kindergarden-style drawings and impossible colour palette requests to work with, Winnie came up with this amazing first draft in no time at all:

first design

We loved the new design, but having requested toned-down colours when we saw this design we did a U-turn and decided it needs much more bold colours in order stand out and be memorable. Winnie cheerfully accepted our feedback and came back with the following masterpiece:

second design

That was pretty much perfect. We just wanted to change the diagram a bit so it was more in-keeping with the rest of the design, and put in a footer so we could see how it would look. That led to the third and final design, which we’re now in the process of transforming into HTML/CSS goodness. Check back soon to see it for real!

third design

It looks nothing like how we imagined it would, but that’s the great thing about working with a talented designer - it leads in directions you never thought you’d go, and the final product is better as a result. Thanks again Winnie!