Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [phoenix-dev] First steps towards a better eclipse.org website 
If we really want do this we need to indicate that on the web page,
otherwise we can get into serious trouble in Europe. Tracking user data
ourselves like with EPP is fine with me, tracking it using a third party
service like Google is not something that I am keen on.

Jochen 

-----Original Message-----
From: phoenix-dev-bounces@xxxxxxxxxxx
[mailto:phoenix-dev-bounces@xxxxxxxxxxx] On Behalf Of Nick Boldt
Sent: Thursday, April 17, 2008 5:54 PM
To: ian.skerrett@xxxxxxxxxxx; For developers on the new Eclipse.org
website project.; Bjorn Freeman-Benson
Subject: Re: [phoenix-dev] First steps towards a better eclipse.org
website

Have you ever used Google Analytics? It's meant to track conversion
rates for ad campaigns, but I've used it to see what the traffic
patterns are on sites I've built -- entry points, exit points, click
tracks (# pages in a trail & visit duration), and of course the usual
stuff like # of visitors, # of page hits & geoIP data.

Setup is really easy -- you add a chunk of html (<script> ... </script>)
in your pages (eg., the Phoenix header), and voom, you have data.

I suggest installing this & waiting a month. That way you have a
baseline from which to experiment with new campaigns / pages / designs /
flows, in order to quantify changes. 

Might also be useful to have different sites w/ different foci &
branding, in order to keep things compartmentalized. For example,
live.eclipse houses all the A/V stuff. Perhaps you might want to further
split into community.eclipse, library.eclipse, and foundation.eclipse?

Nick


On Thu, Apr 17, 2008 at 11:41 AM, Ian Skerrett
<ian.skerrett@xxxxxxxxxxx> wrote:


	I think this is a great discussion.  :-)   To add to this maybe
we should also discuss the objectives of the site.   As you mentioned,
we don't have anything to convert but I see the site providing the
following objectives (not in order):

	 

	1.	Make it easy for our community to access the different
Eclipse project technology.
	2.	Be an information source on how to use the project
technology.
	3.	Promote the wider Eclipse ecosystem and be a value for
our Eclipse member organizations.
	4.	Provide the infrastructure to support the Eclipse
projects.

	 

	In addition to some of your ideas, I would suggest we could also
measure.

	 

	1.	Number of unique users to our site  (new and returning
users).   We want to encourage returning users.
	2.	Length of time they spend on the site  -  Longer means
they are getting the useful information or they are struggling to find
stuff .  This might be dependant on the pages they are visiting.  For
instance, if they go to the download page it should be quick.   If they
go to project pages (ie they are looking for information) they it might
be longer. We might want to think of use cases for this.
	3.	Number of pages visited.   
	4.	Overall satisfaction with the site (yes we don't measure
conversions but I would hope the goal of the site is to be a useful
information source.)

	 

	 

	 

	 

	 

	
________________________________


	From: phoenix-dev-bounces@xxxxxxxxxxx
[mailto:phoenix-dev-bounces@xxxxxxxxxxx] On Behalf Of Bjorn
Freeman-Benson
	Sent: Thursday, April 17, 2008 10:42 AM
	To: phoenix-dev
	Subject: [phoenix-dev] First steps towards a better eclipse.org
website

	 

	Phoenix-oids,
	As many of you know, I think our website could be much much
better (that's the "safe for the public version of my opinion" :-)  As
I've been thinking about what needs to be done, I realize that we don't
have a clear definition of what a "good Eclipse website" does for the
community, ecosystem, and the Foundation. In commercial website land,
they measure conversion: the converting of a visitor into a sale. Given
that the Eclipse Foundation doesn't sell anything, what should we
measure - our conversion if you will - to verify that our website is
doing a good job for the ecosystem?
	
	An obvious thing to measure is downloads, but that's too narrow
for what we are trying to accomplish, but it's definitely one aspect of
our "conversion" number.  Additionally, we could measure click-through
to member companies.  And we could include downloads of articles
<http://www.eclipse.org/resources/> , live events, clicks to
plug-in-central downloads <http://www.eclipseplugincentral.com/> ,
clicks that end up at mailing list or newsgroup archives, ... and (of
course) when we have EclipseCon or Eclipse Summit Europe active, we can
measure conversion to registrations there.
	
	Do you all have additional ideas about what we should be
measuring as "success" for the Eclipse websites?
	- Bjorn

	-- 
	[end of message] 


	_______________________________________________
	phoenix-dev mailing list
	phoenix-dev@xxxxxxxxxxx
	https://dev.eclipse.org/mailman/listinfo/phoenix-dev

Back to the top