DonationCoder.com Software > UserQuotes.com Web Service

UserQuotes.com Web Service: Initial Opening Jan 1, 2011

<< < (2/2)

adi_barb:
the idea of this website is great! a lot of webmasters receive user opinions via e-mail and most of them actually don't have a feedback page.

How does it work? You and your team manage a collection of quotes from users, links to online reviews, email testimonials, and feedback comments. Then specify how you want them displayed -- show them off on standalone pages (hosted on our server or yours), or embed them on your existing website pages using attractive "quote boxes". Automatic thumbnails create a professional and eye-catching look.
--- End quote ---

where or how can webmasters do the things above?

mouser:
Some help pages and videos are coming soon, but briefly:

The first thing you have to do is create a UserQuote SET for your quotes.  There are 3 kinds of objects you create on the site, items (quote), sets (collections of quotes), and groups (optional, to let multiple people maintain your quotes).

So there are actually a couple of ways to show quotes on your pages.


1. The easiest way is to simply embed an iframe on any web page like so:


--- Code: HTML ---<iframe src="http://www.userquotes.com/modules/userquotemod/uqlocal/uqp.php?nid=4&perpage=10&pagermode=prevnext&headfoot=0&theme=silverboxt&cols=1&allinbox=1&timage=quote16x16.png&length=notext&nobanner=1&uioptions=iframedetail&viewmode=topdetail" WIDTH=400 HEIGHT=80% FRAMEBORDER=0 TITLE="iframe quotes" ></iframe>
To see a sample of what this iframe would show just visit that url here.

That shows UserQuote *SET* number 4 which is the DonationCoder quotes set.  So you would change nid=4 to whatever node # your set is.  The iframe sidebar or whatever allows the user to page through your quotes and view the details of any of them.

There are lots of options for how to display the quotes and images, etc. That I will describe later.

The iframe method has the disadvantage of being an iframe, and making the UserQuotes.com server do all the work.


2. Another way is simply to link to the set page on the UserQuotes site itself instead of embedding quotes on your page.

For Example:  http://www.userquotes.com/uqpage?nid=4

That's the DonationCoder.com quotes again (set id 4) on a standalone page again with paging, but this time using a nicer javascript highslide option for displaying quote details without leaving the page.

And to let users anonymously submit new comments or review sitings, you'd send them to http://www.userquotes.com/uqfeedback?nid=4 (replacing your set id of course).


3. Lastly the much more powerful way and the way that really caused UQ to be delayed and to become much more complicated and messy than was originally planned, and the way that has caused all kinds of problems, is using a special local caching-proxy php script.

The local script will be available to download soon -- it lets you embed quote boxes on any page on your site in any div id you choose without using any of the iframe limitations, and most importantly, it serves up the quote text/images locally from your server, by cacheing them from the main UserQuotes site as needed.

This has some advantages:

* Hugely less load on the main UserQuotes server, very scalable.
* Much more flexibly than iframe in terms of formatting it for your pages.
* Better experience for your users (nicer pop up quote details).
* Works fine even if UserQuotes.com goes offline.
* You can create your own custom themes, graphics, etc.
As well as some disadvantages:

* Harder to configure, setup, and diagnose.
I will be posting more info about the local script stuff soon.

JavaJones:
Wooo! I'm so glad to see this finally out in the open. :D I am really hopeful that small software houses will find it useful for their website toolboxes. As you can see with the DC quotes being used in the examples above, DC itself has many such snippets to manage, so this was a big inspiration for it. Given all the DC apps, the use case here is probably on the more complex side of things and more fully utilizes the tools available, but UQ can also be used for smaller needs quite effectively.

The truth is that most good software probably has more good stuff said about it than the devs realize, or at least more than the public ever knows about. The biggest reasons for this both have to do with the time and effort it takes to collect and publicize this information. For a small single developer, they may simply not have the resources or knowledge of where opinions, reviews, etc. would be posted about their app, and not be able to easily provide a way for users to give feedback that translates quickly into testimonials and reviews visible to their site visitors. So a simple feedback from can act as a concentrator, feeding right into a great system to manage that feedback. For others, they may already get tremendous amounts of positive feedback via email, forums, or other methods, but it takes a lot of time and effort to translate that into well-presented website content. Again UQ is great for that. So it covers both those cases and more.

In particular I am hopeful that some open source projects will catch on to it as I feel they are often missing this kind of user-sourced information that can in turn really help generate more users. Many OS projects have forums, but most are used for complaints, questions, and how-tos. Where do you go to say how much you like Filezilla, for example? http://filezilla-project.org/ This is one of the biggest applications of its type in the OS world, yet there is no mention of user opinions, feedback, testimonials, etc. on its website menu or front page. Not every project would want such a thing, I grant, but for those that do I think UQ can be a great option.

I also want to say thanks to mouser for really sticking with this project, through thick and thin. I doubt most people realize how much really went in to this because the functionality may seem deceptively simple from the outside. Yet there were so many issues to solve, both because of the desire to have an alternative to iFrame and linking, and because of our choice of a CMS to base it around (note: I mean the fact that we chose a CMS at all, not necessarily the fault of Drupal itself). Ultimately it was a much longer and more challenging project than either of us anticipated, but it has been a *huge* learning experience, and I think it will set us up for many more cool projects in the future.

- Oshyan

mouser:
There were definitely some hard lessons learned while working on UserQuotes, and problems that are worthwhile talking about, especially with regard to the use of Drupal and the other choices made during development.

Oshyan and I will be writing up a little essay about them soon.

Navigation

[0] Message Index

[*] Previous page