Infinite scroll on the index view and article view seems to be all the rage these days. TIME reports their bounce rate went down by 15 percentage points with their redesign. At some point in the discussion, AdOps will raise their hand and say “how can we get ads in the scroll experience?”
Short answer: with code! Because AdOps only wants to create a limited set of ad slots, and Google DFP slots can be used once per page, you’ll need to display the slot first, and reload it for each subsequent use.
The slots are added dynamically as the user scrolls. If a given slot has already been loaded once, then the next time we try to use it we actually pull the first instance over to our new slot, reload it, and add a placeholder for its old position so the page height doesn’t jump. We can use the same trick scrolling back up, simply replacing the placeholder with the refreshed ad.
Google’s documentation has a similar example that’s a good reference point for methods, etc. Pay attention to
googletag.refresh( unit ); and
unitInstance is what’s returned by
googletag.defineSlot(), so you’ll need to store that somewhere for later reference.
I look forward to hearing about the straightforward approach I missed…
Where Tumblr Came From. Wonderful “making of” piece.
John McAfee, yes the household name in tech, is on the run from the law in Belize. His situation sounds larger than life — who knows how much of it is true.
But, as a testament to the world we now live in, the man has a blog and it’s powered by WordPress. I look forward to hearing his story.
10 years in the making: The new DailyOrange.com. Syracuse University’s Daily Orange finally makes the switch from College Publisher to WordPress, with a very nice responsive design at that. Joey Baker has been vindicated.
Many news sites display related content at the end of an article that’s often based on textual analysis or visitor traffic. Articles often assume a baseline of knowledge on a story, regardless of whether the visitor knows anything about the topic or not.
It would be neat if you could include a quiz widget within the article. The reader could take the quiz which would test their knowledge and then suggest content based on their responses. The news organization would collect useful demographic data to refine their editorial planning.
Co-Authors Plus makes it easy to add multiple bylines to a given post, and has full support for custom post types. Out just a moment ago, v2.6.3 has the following improvements:
- AJAX user search is back to searching against first name, last name, display name, email address and user ID. The method introduced in v2.6.2 didn’t scale well across hundreds of users.
- French translation courtesy of Sylvain Bérubé.
- Spanish translation courtesy of Alejandro Arcos.
- Bug fix: Resolved incorrect caps check against user editing an already published post. Thanks to Doug in the WordPress.org forums for the help.
Please post any questions, bug reports, feature requests, etc. in the WordPress.org forums. If you want to contribute code, I’m eyeballing co-author management in Quick Edit and guest author functionality for v2.7.
For WordPress.com VIPs, this update has already been deployed to the shared plugins repo.
Today, I’m down at Google in Mountain View at Techraking, a gathering of technologists and investigative journalists. It’s been super inspiring because of the fresh to me perspectives — I’d love to help Portland media outlets with projects like those I’ve heard about.
At lunch, I learnt I was to lead a small group breakout on “the future of the CMS.” To keep the discussion going, we started out by brainstorming the things we liked and want to improve our respective software, and then did a roundtable to identify our six month personal goals.
Some things people like about their CMS:
- Drupal done well is easy to use; there are a ton of modules
- Affordability, open source is cheap
- Community to work with
- Many different homepage templates to choose from depending on the stories of the day
What people would like to improve (lots of conversation, as expected):
- Data portability
- More headless; produce output other than HTML
- Scalability, faster when many people are working in the admin
- Less steps for completing common, simple tasks
- Integration with story budgeting, calendaring; API for story flow
- Magical WYSIWYG editor; auto-save that works; track changes
- Support structured data / semantic markup
- Customization for story layout
- Small pieces loosely joined; better integration with other services
Given the short notice, I thought the breakout session went quite well. About twenty people showed up. In terms of what worked:
- Small group discussion; knew enough backgrounds to call out different people to talk
- Noted salient points on the whiteboard as a way of plotting direction
- I enjoyed the “what are you going to work on in the next six months” takeaways at the end
Next time, we should:
- Figure out the location ahead of time so we don’t waste time finding it
- Have people introduce themselves if they haven’t spoken yet
- Every fifteen minutes, have something for everyone to participate in so people don’t check out