Getting back to Sam's problem though: we're getting traffic - people are interested in finding out what's on these Everipedia pages. However, not a lot of people are staying on the site. They leave as soon as they browse through the info on a page that's already been created and sparked just a little bit of intrigue.
What if we worked on something that got people thinking about Everipedia in the long term?
I was listening to a presentation by Neil Patel earlier (a digital marketer and consultant), and he was talking about customer acquisitions and signups. He said something that got me thinking.
Most website funnels look like this: >Visitors come to the site > They tell users to sign up/use a service/buy a product/etc. > They use the site/tool/service/etc.
He asks the following question, "What if we switched that up?" In other words, what if the first thing they did on a website was engage with our users in a way that Wikipedia CANNOT do!
This is his example: http://imgur.com/ZZIISpX
His company, Hello Bar, created a tool that helps with conversion rates. Instead of getting people to sign up, he allowed customers to engage on his website first... before they signed up.
That got me thinking to the ultimate question Sam asked: What can Everipedia do to get people involved?
Idea #1: The #WikiChallenge: To create long-term traffic, I think we need to create a reason for people to want to contribute to the site. (Or at least visit the site more than once.)
So I thought we could create a tool that searches Wikipedia's site to see if a page exists on Wikipedia or something.
Once they do that, they will get a simple result: "Yes, this page exists." or, "This page does not exist." with two call-to-action buttons: "Find out why" and "Create one on Everipedia."
Where would this go? Every page except the home page. That way, if someone is directed to Everipedia from Facebook, The Washington Post, etc., people will go to that page and then interact on that page first AND understand what Everipedia is all about in the process.
With idea #1 (the wiki challenge), people will learn that not everything or everyone has a Wikipedia page... which can incentivize people to come on the site and contribute in one way. And because you NEED an account to contribute to the site, this could incentivize people to take part in a Wiki challenge with their friends.
That said, not everyone would be looking to contribute at first. A lot of people out there are just looking for information and aren't looking to add to it.
Which brings me to idea #2.
IDEA #2: Crowdsourced Quizzes! (I'm REALLY excited about this one!)
Quizzes are the epitome of modernized engagement within websites! They're fun, they help people learn little tidbits faster... hell, they could even help students study for tests!
Because we're branding ourselves as a scholarly website and a knowledge base, people can participate in creating questions (which the editors can look over/accept/reject/whatever) AND the quiz questions can be deleted, edited, sourced, etc. based on new information that comes out about those topics.
And the best part? Nobody would even come CLOSE to doing this! Not BuzzFeed, Sporcle, not Blackboard! Because we have the content that they don't have.
This could REALLY take things up a notch: people could share the Everipedia pages with people to challenge them. (Maybe we could gamify it by giving them IQ points for every question they answer right!)
I'm guessing this would be tough to implement, but it's something that I think could REALLY engage people and get people to sign up and stay on the site longer!
Idea 2: I am so down as long as it doesn't require big coding infrastructure. Actually, the best thing we could potentially do is start a dialogue and cool things going on our social media platforms related to quizzes and trivia. I am down to start stuff like that if you have ideas how ASAP.
I definitely wanted to take some of those internal factors into account: would this change the coding infrastructure of the EP pages? How much time would it take to build? How much would this impact the speed of the pages? (Of course, it would depend on how we'd build it; it makes me wish I knew more about developing atm.)
I'll think it over and come up with a response for what we can do with the 'crowdsourced quizzes' idea.