Simpler views?

We encourage users to post events happening in the community to the community events group on https://www.drupal.org.
othermachines's picture

Again, on the topic of simplicity: despite the power of Views, I find it too cumbersome for my clients and so, about a year ago, began building a module that provides some of the basic features of views with a more accessible interface. As with workflows, in my experience 90% of the time clients just want the basics-- a listing of news articles, a staff directory, a calendar of events, that sort of thing. Another bugaboo of mine has been how a node loses context once you click through a listing; for instance, you go to the News section and "News" is highlighted in the menu, but when you click on the headline to go to the node the menu resets and you've lost your way. The module I've been using uses some trickery with the menu system and session variables to address this.

To summarize your average set up (the way I envision it), using "News" as an example:

  • Create page "News"

  • In edit mode, you find a fieldset called "Attach content". This is a radio button list of node types (the types available are configurable).

  • Select a node type, and a basic list of configurable options is displayed: date range, which available fields to display, category (taxonomy), pager limit, whether to include an RSS link, etc.

  • When the page is saved, the content is displayed as a listing (or a JQuery calendar, or whatever you like-- it's all themable). An RSS feed is created (if desired). A block is also automatically created as an optional mini-display, to be used in a homepage sidebar or whatever. The block is configurable in the same way (fields to display, # of items, etc) via Site building > Blocks. Also, the node type is now contextually attached to the page, so when you click through to view a news article, the menu reassures you that you are still in the news section.

There is a lot it doesn't do, but simplicity is the point, here. I'm not just thinking about my clients, either-- I am ecstatic if I only have to wrestle with Views when its extra features are called for (which is very occasionally). And (dare I say) my "views" load up faster.

Thoughts? Is this something others are interested in?

Comments

To me, this sounds a lot like

cpliakas's picture

To me, this sounds a lot like the http://drupal.org/project/simpleviews project. Might be a good idea to evaluate that project and see where the gaps are between your ideas, because there could be an opportunity for collaboration. In addition, check out the work that Jeff Noyes from Acquia is doing on the Views 3 interface to make it much more user friendly.

Thanks,
Chris

Thanks, Chris. I've looked at

othermachines's picture

Thanks, Chris. I've looked at SimpleViews, which is rooted in a desire for more simplicity but uses Views API. Without going into yet another debate about Views' pros and cons (zz snore), I just haven't been able to bring myself to jump on that bandwagon; once I became more familiar with the Drupal API I stopped using it altogether. I AM watching the development on Views 3 with a keen eye, however. In the meantime something a little friendlier to non-developers (Views has a very steep learning curve) that takes care of what are now considered basic must-haves sounds pretty sweet to me. Anyway, I'll scout around some more and see if there have been any other seeds planted.

Hey there othermachines, I

patcon's picture

Hey there othermachines,
I totally respect the intention, but to be honest, I personally couldn't justify contributing to an effort that attempted to replicate the business logic of views. The separation of Views UI into its own module allows you to tap into only the functionality that you need with your own simpler interface.

But hey, perhaps others feel differently :)

Views 3 for D7 now has an add

bojanz's picture

Views 3 for D7 now has an add view wizard which handles the most often use cases, and you can extend the existing wizards, or write your own.

Enjoy :)

Views is great but not for everyone

Kristen Pol's picture

I totally get this. Views is too hard for many clients to use. It's great for us back-end developers and site builders but not so good for the typical client user. Views 3 is definitely better, but it's still a little difficult.

This is the reason I created the Featured Content module. My client (NatureBridge) needed an easy way to add featured/related content blocks and views was too hard. I evaluated all the other "related content" modules and they were limited in what they could do. Essentially, I needed a small subset of the views functionality but in a very simple form that most users would be able to understand. So, now they can just create a new Featured Content block, do a little configuration and they have a custom block. It's not perfect but it fills a niche.

Kristen