Posted by Anonymous on December 2, 2011 at 7:07pm
Hi everyone! We're trying to gather more information about your experience with OpenPublish as well as what types of features and functionality you would like us to add. Please email us at openpublish@phase2technology.com or respond to this post to talk to us on 12/5 or 12/6 about your experiences! We want to hear from you!
Comments
We need a OP 3.0 beta!!
We've been waiting and waiting for Openpublish for Drupal 7! At this point, it would be far better to release a "stripped down" beta, than wait for all the mythical enhancements.
It SHOULD be far easier to upgrade and enhance OP 3.0 due to the move toward features and apps that you guys are using in the Openpublic release. I assume you will use the same approach in Openpublish.
Here's all we need to start making progress with Openpublish 3.0:
1) A basic Omega subtheme that works with existing alpha code.
2) A bit cleaner implementation of boxes, with more complete directions on how to use the interface. (in reality, even this could be skipped, since us Omega users can theme our pages perfectly well using Omega + Delta.)
3) A beta release of Opencalais, since it integrates with most everything else.
4) The core Openpublish content types
That's it! Then developers can start to theme, layout, and experiment with content while you guys continue to add functionality. If new features are implemented with "features" then we should be able to upgrade an existing development copy later with little difficulty.
JUST GET SOMETHING OUT THERE, PLEASE.
Zoon_unit, we're working on
Zoon_unit, we're working on something that will be released shortly. When we release it, I'm sure you'll see that we're not working on mythical enhancements but have been working rather hard on something that looks nice and works well.
Because we are working on our roadmaps for all of our products, I am looking to find out what content people may be looking for that isn't available, what features/apps may be helpful to have, etc. There are many different kinds of publishing sites and firms out there, so we're trying to find out as much information as we can. Keep in mind that Phase 2 has many different roles so as our Community Manager, I can work on finding out what improvements we can make while our developers are finishing up code for this release. :-)
We're always looking for code and documentation contributions, so we welcome anything you may have to help us out.
Danielle- Thanks for asking
Danielle-
Thanks for asking for feedback and engaging the community for ideas. I agree with Zoon_unit that a less feature rich release is needed so the community can start helping build these features and apps to lessen the load on Phase 2 and do what drupal people do best...contribute! I am excited to hear you guys are close on a release, but what we need most right now is a stable version with a base theme, a simple story content type with Opencalais integrated and thats really it. I am hoping features are built as apps or using the features module so the core product doesn't have the extra bulk if you as a site owner don't need it.
My wish list would include features for the following:
Improved blogging platform for both staff and user generated blogs
Support for Domain access on all core openpublish features and modules
Media module integration with a VERY clean interface to easily add photo galleries via the media module and plupload.
Onsite Vimeo uploads through the media module and vimeo api.
Integrated user handling for cleaner registration, user profiles and spam control/moderation features built in.
Anything to help with site speed/performance!
An app for paywall access. Although we don't need it now, many of my clients are asking for it.
Standard set of SEO tools like pathauto, global redirect etc. etc.
PDF uploader/viewer simular to what the ipaper module does to upload digital editions and special sections.
Support for the new google standout tag with support for domain access
A well implemented nodequeue type set up to assign top content to the homepage
Breaking news templates that allow for easy promotion of breaking news with timers to pull it down after a period of time.
If these are accomplished, then I can install and launch my site with very little development work! :) Knowing that wont happen, I would love to contribute to the project with any features we can help build or test.
I want this as badly as
I want this as badly as everyone else, but after working through each previous version and upgrade I do appreciate the fact that Phase II is taking a step back to re-evaluate and approach this differently.
OP in its initial offering was a great way to build a news website. Its plethora of features allowed us to build a robust site almost out of the box, but it also seemed to require so many resources. I see the value of scaling it down, so I understand if my suggestions below are not built into it...
I totally agree with everything that was said already. I'm sure moving to Drupal 7 will already address some of the limitations, especially with media.
1) It would be nice to have robust media handling per content type. Articles need to have the ability to have photos, video and other documents added to it and displayed prominently and aesthetically. Preferably, even allowing photos and video to be displayed in the same media rotator.
2) In addition to the per content type media handling, the new OP needs to display all its media aesthetically and flexibly. News websites need to display its media content (photos and video) well. We are all used to seeing videos displayed in players with playlists, with jquery, etc... not just a views grid using lightbox. I know the closest thing to this right now for Drupal is probably Mediafront, that's definitely a step in the right direction. Video needs to be viewable in all mobile devices via html5.
3) Open Calais, Alchemy (or somethings similar) needs to be implemented. This was so vital to providing related content on the site and keeping visitors engaged.
4) Theming. Yes, the next version of OP needs to shed the dependence on the OP theme and its templates. We should be allowed to easily (and with less re-working) use other themes or use our own sub-theme.
5) It would be nice to be able to upgrade my site from OP 2.3 to the latest version. I know that this is not planned, but it would be nice to allow me to move my site out from Drupal 6.
6) In lieu of #5 not happening, the process of upgrading was not fun in the past. It seemed each time I upgraded to the latest version 1.6 > 1.7 > 2.0 > 2.1... I came across more and more errors and instability. Could the upgrade process be made less painless and more stable?
7) A mobile implementation of the site needs to be available (responsive web design? or a mobile version?). Mobile is a must.
Thank you.
Upgrade path
I would like to stress on the upgradeability. If there is no upgrade path from D6 to D7, that will be a big blow to people like us. Keeping that in mind, all future versions should have the facility to upgrade to future versions of Drupal.
sTattler.com
I agree, no upgrade path and
I agree, no upgrade path and no maintenance schedule for the D6 version will be a huge blow to OpenPublish for us. We have put a lot of content in the D6 version and it works for us, but as time goes on and other modules upgrade, OpenPublish D6 seems to be slowly breaking down (as evidenced by the recent Views bug). I think it hurts the case for using distributions when maintenance support is dropped suddenly for a current release, and the maintainers decide to move on to something new.
The direction of OpenPublish
There were a lot of comments when OpenPublish for D6 came out about how resource intensive the distribution was. The community also weighed in on their needs for specific content types and features and functionality. We listened to the community and completely re-architected OpenPublish for D7 and made changes to the content types. Those who have started using the Drupal 7 version of OpenPublish may have noticed these changes as well as the addition of the Disqus app and other features.
We have done a large amount of work on OpenPublish and have made changes based on the feedback that we have received. As maintainers, we have been striving to make sure we have a usable product that meets the community needs. We understand your concerns as to the D6 version of OpenPublish, but please keep in mind that this distribution is open source and anyone is able to contribute. We invite all of our community members to contribute both code and documentation to help improve OpenPublish.
Thank you!
Thank you for all of the suggestions. We really appreciate you taking your time to give us feedback and we'll use these ideas to improve our product roadmap, our documentation, and OpenPublish as a whole. We can't do it without you!
OpenPub Feedback
Hi --
This didn't have enough documentation for this Drupal Newbie to make work. Blocks and views were confusing and apparently not easily used. Most of it seems to go through the context menu.
Finally gave up when I got to the page of customized modules that shouldn't be updated even though Drupal says to updated them. Oops.
Yes, I should have spent more time reading the directions before jumping into it.
Here are a couple of suggestions.
Calais seemed to generate errors -- You should try to make it run on a variety of php implementations for those using shared hosts.
Calais should prioritize results for local site before global site, perhaps separate links for this site and global sites. Calais should have config option to just show related content from local site.
Menu should be expanded to some kind of "Mega" Menu with more than two levels. Doubt Calais can substitute for carefully chosen hierarchy by person knowledgeable in subject matter of site.
Creating new content type (e.g. upper level submenu page) should be documented.
I really need something that others, including newbies, can contribute too. Path is all articles/, perhaps a dropdown menu showing different areas where articles can be stored to be used under submenus, though I 'll probably end up using taxonomy terms for my menu.
There ought to be an input lite basic input form. Don't need pictures, but would like drop down menus for tags, default author info, that's about it. Try to get it to fit on one screen.
Overall, OpenPub seemed slower than ordinary Drupal installation. Perhaps I need a better web host, perhaps I'll get more than one visitor at a time.
Mollum is great, though I haven't tested on a live site yet!
Development tools have an add content feature to generate content for site. Would be nice to include an "Undo" ustility that deleted all posts in past 3 hours or one day to get rid of clutter.
Wouldn't rush too much on D7. Seems like a bunch of the modules you use are still in beta or release candidate status.
More available themes to go along with directions for creating compatible themes would be nice.
I'll probably come back and look at this again, but not suitable for my needs right now.
Thanks,
Kirk B.
OpenPub Feedback
Oh, and a calendar!
Kirk B.
More reliance on modules, less on theming
I was initially excited by the first OP release. Seemed like a dream come true, and ready-made template for a great news site. And if you stick with everything exactly the way it comes out of the box, that's what you get. But my excitement deflated once I began trying to make changes. Even a simple change like switching over to default teasers instead of using the separate teaser CCK field turned out to be impossible.
Most of the problems I ran into had to do with OP's reliance on theming. This was the most complicated theme I'd ever seen, and so much of what I saw seemed unnecessary. Most, if not all of the features I saw can be done with modules (Views, Display Suite, Panels, etc.). It seemed backward, a throwback to the pre-Views days when you had to do everything in the theme. And at the same time it used some advanced modules like Context. That made it doubly hard to figure out problems. It was like trying to reason with a schizophrenic.
If you can make the D7 version independent from the theme, it will make it a whole lot easier to work with. You should be able to enable any standard or base theme and make all the basic functions work. Maybe it won't look pretty, but it should at least work.
This doesn't mean ditch the special OP theme. But the included theme in OP should be set up as a guide, so site developers can use it for setting up other themes.
Thanks for all the work on this project, and I hope that it has a bright future.
Restructure
We are currently working on a restructure for OpenPublish for D7, so we are definitely making some improvements and adding new features!
Revelation is in changign the base
Thanks @kirkcaraway for this insight. After loading and running head on into OP I made significant changes to the base structure, pages & taxonomy and Calais. Wooooh! The challenge now is to find what OP is doing with all the changes. It's like looking from the deck of a ship into the Pacific, and hoping to see the bottom.
Better support for scheduled publishing.
In addition to the comments above regarding restructuring, I think an important addition would be support for scheduled publishing such as the Channels and Editions features of the ProsePoint profile.
Scheduler?
Are you looking for something similar to the Scheduler module (http://drupal.org/project/scheduler) or are you looking for something more than that?
I mean more of an integrated
I mean more of an integrated solution that will allow scheduled publishing, grouping and display customisation of content (Using Views + other necessary modules) into 'Issues/Editions', with basic workflow functionality as well. I had bean considering migrating a couple of sites to openpublish (due to features such as Calais, gMaps, Topic Hubs out of the box, and a more assured [I feel] roadmap) however did not find functionality equivalent to ProsePoint editions at the time (mid 2010) which made it impossible.
See also http://groups.drupal.org/node/101284 and http://www.prosepoint.org/node/334 for more info.
Some Thoughts From A Novice
Hello all,
I would like to offer some thoughts. I am completely new to Drupal, having made the decision to move away from Joomla for various reasons, after several years. I would very much like to rewrite our website (Science File - http://www.sciencefile.org) in Open Publish because, from what I have been reading, it offers many of the publishing features that I have found impossible to achieve with Joomla, particularly the Semantic Web services. So, I am not familiar with Drupal nor OP. Of course I realise there is a big learning curve ahead, but that does not put me off - I'm quite looking forward to it actually.
What I would like more than anything is easy-to-follow documentation, with examples. It should be remembered that there will be those like myself coming to Drupal and OP for the first time, and although, of course, I will have done a lot of background reading about Drupal, and have played around with a local installation of it, the OP documentation should be clear, concise and comprehensive for those who have never used it (or Drupal) before. For example, and off the top of my head, if I want to left-align an article image, where is the CSS I need to edit? If I want to include a drop capital at the start of an article, how would I achieve that? How will author information work exactly? How can I implement a useful and attractive comments system for articles? Can I create an efficient node-categorisation system using only tags and taxonomy (I'm used to doing it using relational database schemas)? Can I link a published article to a forum discussion with some sort of auto-discuss module? How can I include video in articles? What's the best way of generating a bibliography for both internal and external links? I'd like to see answers to questions like these in the documentation, either in the text or in a separate FAQ/How-To section (and apologies if any of these questions seem too simple!).
Some examples, therefore, of how to achieve common publishing tasks would be incredibly useful, because, apart from anything else, I won't have an infinite amount of time available to study these things, so any time saved would be much appreciated.
Lastly, the very best of luck with the D7 implementation of OP - I am really looking forward to getting started!
Happy Xmas!
Andy.
Documentation
Hi Andy -
This was very helpful. We are currently putting together a list of resources for those that are not as familiar with Drupal. You did raise some other points though that we can include in our documentation. Thanks!
No Problem
My absolute pleasure, Danielle, and please do not hesitate to let me know if I can be of further assistance. I am glad you found my comments useful. Happy Xmas!
Andy.
Hope it's not too late to
Hope it's not too late to throw out a few ideas...
I agree that an upgrade path is important. If the development team paved the way for us there, I wouldn't mind them ignoring any of my other ideas :P
--
My website.
I'd like to second most of
I'd like to second most of the ideas stated above and also thank the Openpublish development team for bringing OP to us all. It is an amazing tool that has allowed me to not only create an effective news site, but to also learn a whole heck of a lot about how drupal makes magic happen.
To comment on something that was brought up a few times above, more documentation would be great, especially the kind that @AndyTheAstronomer was talking about. A general guide to get people going.
But I would also like to say that we as drupal and OpenPublish users might take things upon ourselves to be a bit more diligent in contributing to the cause. That is to say, if you come up against a particularly odd or difficult problem for which there is no support or issue post, and you happen to find a solution or even if you can only root out the problem, post something about it. Chances are someone else has had or will have the same issue as you. And while a list of support resources is super helpful, information from actual users coming up against issues and solving problems is sometimes more useful.
Thanks all!
One Word: BOTCHA
Danielle, I'd like to suggest that the first line of defense against spam, bogus registrations, and forms being submitted by bots be the BOTCHA module.
On a site I inherited, BOTCHA turned an overwhelming deluge of such problems into a mere trickle. And the best part about it is that it does its job by inconveniencing the bots, not your visitors and customers.
Mollom might be able to help with the rest of the problems — I haven't begun playing with its settings — but on this particular site, I believe I can do it by tweaking a few of the registration settings.
Try it out and see what you think!
Hi Cliff. We generally use
Hi Cliff. We generally use CAPTCHA for spam prevention. Unfortunately, BOTCHA is only available for Drupal 6, so we won't be able to use it in our current OpenPublish development. We'll keep an eye out for the D7 version though, so we can check it out!
Danielle Sheffler
Engagement Manager at Acquia
http://www.acquia.com
CAPTCHA poses accessibility problems; BOTCHA doesn't
The accessibility problems and general rudeness of CAPTCHAs are well documented across the Web. The neat thing about BOTCHA is that it adds no extra work for real people.
I don't have to prove I'm human unless I start acting like a bot (for example, by filling in form fields I can't even tell are there).
Bots get caught doing what bots do, and humans just complete the form and go on — no cryptic images to decipher, no incomplete audios to figure out.
Thanks for pointing out its D7 status. I'll try to find out what it needs to move that along. It's the direction that form security needs to go!
www.imagenews.com.au
@ Danielle, have finally DUMPED OP2 6.x because it was a lot of trouble in the end.
Have now started using OP3 D7.x - everything has gone fine - except for one error - but I'm very pleased with the Alpha roll-out - it works just as I think you would expect out of the box.
I've a lot of tweaking to get to where I want to but the site so far took me two days and several coffees. The next phase should be exciting so I'm looking forward to the update.
Have a look at www.imagenews.com.au
cheers