Testing of individual pages
Abilnet - October 21, 2007 - 07:33
| Project: | split_test |
| Version: | 5.x-2.0 |
| Component: | User interface |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
Thank you very much for the module, your work highly appreciated!
If you don't mind, after a quick look I got some ideas for you... the theme based split testing is a good idea, of course, but very often there's also a need to test individual pages against each other.
For example, if a coder is interested to know which of two presentation pages of a software, leads to more downloads... or which sales speech to market coding services leads to more contacts... or newsletter subscriptions, information requests... even actual sales etc. etc. By this way, there's an easy and quick way to test virtually what ever you like!
Thanks again for the module, my 2 cents from Sunny Spain :)
#1
I'm interested in this as well. We'd like to test different versions of the home page and other key pages, which are defined through Views/Panels, not directly in the theme, so essentially we'd want to test different pages/panels but have them show up at the same path.
#2
I agree that node / panel based split testing will be a very useful feature in Drupal. I will draw out a basic spec for it and setup a
reverse bounty - there are sure to be some people on groups.drupal.org/search-engine-optimization that would be keen to contribute as it is not the first time the request has been made.
Implementing node based testing should be straight forward, and in a sense that will give a version of panels based split testing. You can clone your panels, then setup two different nodes containing slightly different versions of the panel. Deeper integration with Panels will be slightly trickier. At a guess I would target Panels 2 - I think that comes with an API to make this sort of thing easier. That said I
am not intimate with that code, and with its complexity it may take some time to get up to speed with.
Perhaps for the moment it would be best to focus on node based testing, and when panels 2 comes out of beta look at adding to that
separately if there is a necessity for it. Would that cover your needs?
Lastly I would still target d5, the module needs an overhaul in some areas to bring it up to d6. I want to get that done at some point, but
I am not using 6 yet myself. Are you still using Drupal 5, and would that be sufficient for you?
Regards,
Sam.
#3
We're currently using Drupal 5/Panels 2 (I think most people are feeling fairly comfortable using Panels 2 now as opposed to Panels 1). Having the basic ability to do the split testing based on URLs would hit on most needs I think -- certainly for nodes, and it would make it easy to clone views/panels-based pages. That would cover what we need at least.
Thanks for your input, and I'll watch for the spec/bounty.