Re: [Sugar-devel] Website Update for a/b testing

2018-12-21 Thread Walter Bender 
Regarding the website, I think that we two somewhat orthogonal hypotheses
to test: (1) is the content of the website a deterrent in getting and
holding people's attention? and (2) do the layout/navigation/graphic design
act as a deterrent in getting and holding people's attention? (I use
attention here as it is something roughly measurable in terms of time on
site, number of pages viewed, etc. while what really interests me is
whether or not people take action based on their interest (does the website
facilitate or deter action by our visitors).

As far as how to set up A/B testing to measure both 1 and 2 above, we can
make informed guesses as to what might be at issue in terms of content and
navigation and make one test subject or we can try to tease apart the two
factors. I suggest the former if only because we have limited time and
resources. Peace has been working on simplification (she has some good
reasoning behind most of the changes she is proposing) and I am happy to
work with Tony and the Marketing team on some new content ideas that better
reflect our relevance to would be Sugar adopters.

regards.

-walter

-- 
Walter Bender
Sugar Labs
http://www.sugarlabs.org

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Website Update for a/b testing

2018-12-21 Thread Samson Goddy 
@Alex Perez will be focusing on numbers, so I think he is in the better
position to answer that. But our initial agreement was to see which does
better per user most time spent.




On Fri, Dec 21, 2018, 8:44 AM James Cameron  What's your metrics, baseline, and hypothesis?
>
> On Fri, Dec 21, 2018 at 08:25:39AM +0100, Samson Goddy wrote:
> > Hello,
> >
> > Yes, we are working on the second landing page (B) part of the site.
> Bringing
> > perrie mockup to live. We are almost done.
> >
> > We need something to compare with the current [1]sl.org
> >
> > Regards
> >
> > On Fri, Dec 21, 2018, 6:36 AM James Cameron <[2]qu...@laptop.org wrote:
> >
> > Has this been done yet?  It has been very quiet since I gave this
> > summary.
> >
> > On Thu, Dec 13, 2018 at 08:06:44AM +1100, James Cameron wrote:
> > > Thanks.
> > >
> > > Gathering together the information so far;
> > >
> > > 1.  meeting of community members during an oversight board meeting,
> > > [3]https://wiki.sugarlabs.org/go/Oversight_Board/2018/
> > meeting-log-2018-12-07
> > > chose a goal (A/B content testing), and a team of volunteers,
> > >
> > > 2.  meeting of the team came up with several plans,
> > > [4]http://meeting.sugarlabs.org/sugar-meeting/2018-12-09
> > > and an article on the value and process of A/B testing,
> > > [5]
> https://circaedu.com/hemj/understanding-the-value-of-ab-testing/
> > >
> > > 3.  Peace has forged ahead and made a mock-up of some design
> changes,
> > > [6]http://lists.sugarlabs.org/archive/sugar-devel/2018-December/
> > 056034.html
> > >
> > > Could the team please;
> > >
> > > - decide how to measure engagement; e.g. time on page,
> click-through
> > >   to downloads; this is the metric,
> > >
> > > - begin to measure, to establish the baseline,
> > >
> > > - make some hypothesis,
> > >
> > > - establish which metrics will define pass or fail,
> > >
> > > - design an experiment,
> > >
> > > - run the experiment,
> > >
> > > - assess the results and come to a conclusion,
> > >
> > > - iterate back to the hypothesis step,
> > >
> > > I've turned on the GitHub Wiki feature for the repository
> > > [7]https://github.com/sugarlabs/www-sugarlabs in case you'd like
> to use
> > > that for sharing your work in a central place.  Otherwise you might
> > > use [8]wiki.sugarlabs.org.
> > >
> > > Thanks for working on this!
> > >
> > > --
> > > James Cameron
> > > [9]http://quozl.netrek.org/
> >
> > --
> > James Cameron
> > [10]http://quozl.netrek.org/
> > ___
> > Sugar-devel mailing list
> > [11]Sugar-devel@lists.sugarlabs.org
> > [12]http://lists.sugarlabs.org/listinfo/sugar-devel
> >
> > References:
> >
> > [1] http://sl.org/
> > [2] mailto:qu...@laptop.org
> > [3]
> https://wiki.sugarlabs.org/go/Oversight_Board/2018/meeting-log-2018-12-07
> > [4] http://meeting.sugarlabs.org/sugar-meeting/2018-12-09
> > [5] https://circaedu.com/hemj/understanding-the-value-of-ab-testing/
> > [6]
> http://lists.sugarlabs.org/archive/sugar-devel/2018-December/056034.html
> > [7] https://github.com/sugarlabs/www-sugarlabs
> > [8] http://wiki.sugarlabs.org/
> > [9] http://quozl.netrek.org/
> > [10] http://quozl.netrek.org/
> > [11] mailto:Sugar-devel@lists.sugarlabs.org
> > [12] http://lists.sugarlabs.org/listinfo/sugar-devel
>
> --
> James Cameron
> http://quozl.netrek.org/
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Website Update for a/b testing

2018-12-20 Thread James Cameron 
What's your metrics, baseline, and hypothesis?

On Fri, Dec 21, 2018 at 08:25:39AM +0100, Samson Goddy wrote:
> Hello,
> 
> Yes, we are working on the second landing page (B) part of the site. Bringing
> perrie mockup to live. We are almost done.
> 
> We need something to compare with the current [1]sl.org
> 
> Regards
> 
> On Fri, Dec 21, 2018, 6:36 AM James Cameron <[2]qu...@laptop.org wrote:
> 
> Has this been done yet?  It has been very quiet since I gave this
> summary.
> 
> On Thu, Dec 13, 2018 at 08:06:44AM +1100, James Cameron wrote:
> > Thanks.
> >
> > Gathering together the information so far;
> >
> > 1.  meeting of community members during an oversight board meeting,
> > [3]https://wiki.sugarlabs.org/go/Oversight_Board/2018/
> meeting-log-2018-12-07
> > chose a goal (A/B content testing), and a team of volunteers,
> >
> > 2.  meeting of the team came up with several plans,
> > [4]http://meeting.sugarlabs.org/sugar-meeting/2018-12-09
> > and an article on the value and process of A/B testing,
> > [5]https://circaedu.com/hemj/understanding-the-value-of-ab-testing/
> >
> > 3.  Peace has forged ahead and made a mock-up of some design changes,
> > [6]http://lists.sugarlabs.org/archive/sugar-devel/2018-December/
> 056034.html
> >
> > Could the team please;
> >
> > - decide how to measure engagement; e.g. time on page, click-through
> >   to downloads; this is the metric,
> >
> > - begin to measure, to establish the baseline,
> >
> > - make some hypothesis,
> >
> > - establish which metrics will define pass or fail,
> >
> > - design an experiment,
> >
> > - run the experiment,
> >
> > - assess the results and come to a conclusion,
> >
> > - iterate back to the hypothesis step,
> >
> > I've turned on the GitHub Wiki feature for the repository
> > [7]https://github.com/sugarlabs/www-sugarlabs in case you'd like to use
> > that for sharing your work in a central place.  Otherwise you might
> > use [8]wiki.sugarlabs.org.
> >
> > Thanks for working on this!
> >
> > --
> > James Cameron
> > [9]http://quozl.netrek.org/
> 
> --
> James Cameron
> [10]http://quozl.netrek.org/
> ___
> Sugar-devel mailing list
> [11]Sugar-devel@lists.sugarlabs.org
> [12]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> References:
> 
> [1] http://sl.org/
> [2] mailto:qu...@laptop.org
> [3] https://wiki.sugarlabs.org/go/Oversight_Board/2018/meeting-log-2018-12-07
> [4] http://meeting.sugarlabs.org/sugar-meeting/2018-12-09
> [5] https://circaedu.com/hemj/understanding-the-value-of-ab-testing/
> [6] http://lists.sugarlabs.org/archive/sugar-devel/2018-December/056034.html
> [7] https://github.com/sugarlabs/www-sugarlabs
> [8] http://wiki.sugarlabs.org/
> [9] http://quozl.netrek.org/
> [10] http://quozl.netrek.org/
> [11] mailto:Sugar-devel@lists.sugarlabs.org
> [12] http://lists.sugarlabs.org/listinfo/sugar-devel

-- 
James Cameron
http://quozl.netrek.org/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Website Update for a/b testing

2018-12-20 Thread Samson Goddy 
On Fri, Dec 21, 2018, 8:30 AM Perrie Ojemeh  This is a very good point! Alex, James and Samson thoughts about it?
>
> For reframing content purposes.
>

Agree can we have signed similar content to the B side of the site?
Addresssing Tony's concerned?

Tony, would you want to help reframe the content?

>
> On Fri, 21 Dec 2018 at 7:19 AM, Tony Anderson 
> wrote:
>
>> I didn't read everything but it appears this has to do with
>> www.sugarlabs.org and not Sugar.
>>
>> Our fundamental problem is the perception that Sugar is limited to the
>> XO platform. Not only do we need to focus on Sugar for
>> other platforms but on the basic question: What does Sugar offer that
>> makes it a compelling choice for education in schools? Once that is
>> decided, it would be appropriate to use the website to convey the
>> message to the public.
>>
>> Tony
>>
>> On 12/21/18 5:36 AM, James Cameron wrote:
>> > Has this been done yet?  It has been very quiet since I gave this
>> > summary.
>> >
>> > On Thu, Dec 13, 2018 at 08:06:44AM +1100, James Cameron wrote:
>> >> Thanks.
>> >>
>> >> Gathering together the information so far;
>> >>
>> >> 1.  meeting of community members during an oversight board meeting,
>> >>
>> https://wiki.sugarlabs.org/go/Oversight_Board/2018/meeting-log-2018-12-07
>> >> chose a goal (A/B content testing), and a team of volunteers,
>> >>
>> >> 2.  meeting of the team came up with several plans,
>> >> http://meeting.sugarlabs.org/sugar-meeting/2018-12-09
>> >> and an article on the value and process of A/B testing,
>> >> https://circaedu.com/hemj/understanding-the-value-of-ab-testing/
>> >>
>> >> 3.  Peace has forged ahead and made a mock-up of some design changes,
>> >>
>> http://lists.sugarlabs.org/archive/sugar-devel/2018-December/056034.html
>> >>
>> >> Could the team please;
>> >>
>> >> - decide how to measure engagement; e.g. time on page, click-through
>> >>to downloads; this is the metric,
>> >>
>> >> - begin to measure, to establish the baseline,
>> >>
>> >> - make some hypothesis,
>> >>
>> >> - establish which metrics will define pass or fail,
>> >>
>> >> - design an experiment,
>> >>
>> >> - run the experiment,
>> >>
>> >> - assess the results and come to a conclusion,
>> >>
>> >> - iterate back to the hypothesis step,
>> >>
>> >> I've turned on the GitHub Wiki feature for the repository
>> >> https://github.com/sugarlabs/www-sugarlabs in case you'd like to use
>> >> that for sharing your work in a central place.  Otherwise you might
>> >> use wiki.sugarlabs.org.
>> >>
>> >> Thanks for working on this!
>> >>
>> >> --
>> >> James Cameron
>> >> http://quozl.netrek.org/
>>
>>
>> ___
>> Sugar-devel mailing list
>> Sugar-devel@lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>
> --
> Peace Ojemeh(Perrie)
> Twitter: https://twitter.com/Peace_Ojemeh
> Email: fidelis.peaceoje...@gmail.com
> peaceoje...@sugarlabs.org
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Website Update for a/b testing

2018-12-20 Thread Perrie Ojemeh 
This is a very good point! Alex, James and Samson thoughts about it?

For reframing content purposes.

On Fri, 21 Dec 2018 at 7:19 AM, Tony Anderson  wrote:

> I didn't read everything but it appears this has to do with
> www.sugarlabs.org and not Sugar.
>
> Our fundamental problem is the perception that Sugar is limited to the
> XO platform. Not only do we need to focus on Sugar for
> other platforms but on the basic question: What does Sugar offer that
> makes it a compelling choice for education in schools? Once that is
> decided, it would be appropriate to use the website to convey the
> message to the public.
>
> Tony
>
> On 12/21/18 5:36 AM, James Cameron wrote:
> > Has this been done yet?  It has been very quiet since I gave this
> > summary.
> >
> > On Thu, Dec 13, 2018 at 08:06:44AM +1100, James Cameron wrote:
> >> Thanks.
> >>
> >> Gathering together the information so far;
> >>
> >> 1.  meeting of community members during an oversight board meeting,
> >>
> https://wiki.sugarlabs.org/go/Oversight_Board/2018/meeting-log-2018-12-07
> >> chose a goal (A/B content testing), and a team of volunteers,
> >>
> >> 2.  meeting of the team came up with several plans,
> >> http://meeting.sugarlabs.org/sugar-meeting/2018-12-09
> >> and an article on the value and process of A/B testing,
> >> https://circaedu.com/hemj/understanding-the-value-of-ab-testing/
> >>
> >> 3.  Peace has forged ahead and made a mock-up of some design changes,
> >>
> http://lists.sugarlabs.org/archive/sugar-devel/2018-December/056034.html
> >>
> >> Could the team please;
> >>
> >> - decide how to measure engagement; e.g. time on page, click-through
> >>to downloads; this is the metric,
> >>
> >> - begin to measure, to establish the baseline,
> >>
> >> - make some hypothesis,
> >>
> >> - establish which metrics will define pass or fail,
> >>
> >> - design an experiment,
> >>
> >> - run the experiment,
> >>
> >> - assess the results and come to a conclusion,
> >>
> >> - iterate back to the hypothesis step,
> >>
> >> I've turned on the GitHub Wiki feature for the repository
> >> https://github.com/sugarlabs/www-sugarlabs in case you'd like to use
> >> that for sharing your work in a central place.  Otherwise you might
> >> use wiki.sugarlabs.org.
> >>
> >> Thanks for working on this!
> >>
> >> --
> >> James Cameron
> >> http://quozl.netrek.org/
>
>
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
-- 
Peace Ojemeh(Perrie)
Twitter: https://twitter.com/Peace_Ojemeh
Email: fidelis.peaceoje...@gmail.com
peaceoje...@sugarlabs.org
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Website Update for a/b testing

2018-12-20 Thread Samson Goddy 
On Fri, Dec 21, 2018, 7:19 AM Tony Anderson  I didn't read everything but it appears this has to do with
> www.sugarlabs.org and not Sugar.
>
> Our fundamental problem is the perception that Sugar is limited to the
> XO platform. Not only do we need to focus on Sugar for
> other platforms but on the basic question: What does Sugar offer that
> makes it a compelling choice for education in schools? Once that is
> decided, it would be appropriate to use the website to convey the
> message to the public.
>

Yes, you are correct.

>
> Tony
>
> On 12/21/18 5:36 AM, James Cameron wrote:
> > Has this been done yet?  It has been very quiet since I gave this
> > summary.
> >
> > On Thu, Dec 13, 2018 at 08:06:44AM +1100, James Cameron wrote:
> >> Thanks.
> >>
> >> Gathering together the information so far;
> >>
> >> 1.  meeting of community members during an oversight board meeting,
> >>
> https://wiki.sugarlabs.org/go/Oversight_Board/2018/meeting-log-2018-12-07
> >> chose a goal (A/B content testing), and a team of volunteers,
> >>
> >> 2.  meeting of the team came up with several plans,
> >> http://meeting.sugarlabs.org/sugar-meeting/2018-12-09
> >> and an article on the value and process of A/B testing,
> >> https://circaedu.com/hemj/understanding-the-value-of-ab-testing/
> >>
> >> 3.  Peace has forged ahead and made a mock-up of some design changes,
> >>
> http://lists.sugarlabs.org/archive/sugar-devel/2018-December/056034.html
> >>
> >> Could the team please;
> >>
> >> - decide how to measure engagement; e.g. time on page, click-through
> >>to downloads; this is the metric,
> >>
> >> - begin to measure, to establish the baseline,
> >>
> >> - make some hypothesis,
> >>
> >> - establish which metrics will define pass or fail,
> >>
> >> - design an experiment,
> >>
> >> - run the experiment,
> >>
> >> - assess the results and come to a conclusion,
> >>
> >> - iterate back to the hypothesis step,
> >>
> >> I've turned on the GitHub Wiki feature for the repository
> >> https://github.com/sugarlabs/www-sugarlabs in case you'd like to use
> >> that for sharing your work in a central place.  Otherwise you might
> >> use wiki.sugarlabs.org.
> >>
> >> Thanks for working on this!
> >>
> >> --
> >> James Cameron
> >> http://quozl.netrek.org/
>
>
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Website Update for a/b testing

2018-12-20 Thread Samson Goddy 
Hello,


Yes, we are working on the second landing page (B) part of the site.
Bringing perrie mockup to live. We are almost done.

We need something to compare with the current sl.org


Regards

On Fri, Dec 21, 2018, 6:36 AM James Cameron  Has this been done yet?  It has been very quiet since I gave this
> summary.
>
> On Thu, Dec 13, 2018 at 08:06:44AM +1100, James Cameron wrote:
> > Thanks.
> >
> > Gathering together the information so far;
> >
> > 1.  meeting of community members during an oversight board meeting,
> >
> https://wiki.sugarlabs.org/go/Oversight_Board/2018/meeting-log-2018-12-07
> > chose a goal (A/B content testing), and a team of volunteers,
> >
> > 2.  meeting of the team came up with several plans,
> > http://meeting.sugarlabs.org/sugar-meeting/2018-12-09
> > and an article on the value and process of A/B testing,
> > https://circaedu.com/hemj/understanding-the-value-of-ab-testing/
> >
> > 3.  Peace has forged ahead and made a mock-up of some design changes,
> > http://lists.sugarlabs.org/archive/sugar-devel/2018-December/056034.html
> >
> > Could the team please;
> >
> > - decide how to measure engagement; e.g. time on page, click-through
> >   to downloads; this is the metric,
> >
> > - begin to measure, to establish the baseline,
> >
> > - make some hypothesis,
> >
> > - establish which metrics will define pass or fail,
> >
> > - design an experiment,
> >
> > - run the experiment,
> >
> > - assess the results and come to a conclusion,
> >
> > - iterate back to the hypothesis step,
> >
> > I've turned on the GitHub Wiki feature for the repository
> > https://github.com/sugarlabs/www-sugarlabs in case you'd like to use
> > that for sharing your work in a central place.  Otherwise you might
> > use wiki.sugarlabs.org.
> >
> > Thanks for working on this!
> >
> > --
> > James Cameron
> > http://quozl.netrek.org/
>
> --
> James Cameron
> http://quozl.netrek.org/
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Website Update for a/b testing

2018-12-20 Thread Tony Anderson 
I didn't read everything but it appears this has to do with 
www.sugarlabs.org and not Sugar.


Our fundamental problem is the perception that Sugar is limited to the 
XO platform. Not only do we need to focus on Sugar for
other platforms but on the basic question: What does Sugar offer that 
makes it a compelling choice for education in schools? Once that is 
decided, it would be appropriate to use the website to convey the 
message to the public.


Tony

On 12/21/18 5:36 AM, James Cameron wrote:

Has this been done yet?  It has been very quiet since I gave this
summary.

On Thu, Dec 13, 2018 at 08:06:44AM +1100, James Cameron wrote:

Thanks.

Gathering together the information so far;

1.  meeting of community members during an oversight board meeting,
https://wiki.sugarlabs.org/go/Oversight_Board/2018/meeting-log-2018-12-07
chose a goal (A/B content testing), and a team of volunteers,

2.  meeting of the team came up with several plans,
http://meeting.sugarlabs.org/sugar-meeting/2018-12-09
and an article on the value and process of A/B testing,
https://circaedu.com/hemj/understanding-the-value-of-ab-testing/

3.  Peace has forged ahead and made a mock-up of some design changes,
http://lists.sugarlabs.org/archive/sugar-devel/2018-December/056034.html

Could the team please;

- decide how to measure engagement; e.g. time on page, click-through
   to downloads; this is the metric,

- begin to measure, to establish the baseline,

- make some hypothesis,

- establish which metrics will define pass or fail,

- design an experiment,

- run the experiment,

- assess the results and come to a conclusion,

- iterate back to the hypothesis step,

I've turned on the GitHub Wiki feature for the repository
https://github.com/sugarlabs/www-sugarlabs in case you'd like to use
that for sharing your work in a central place.  Otherwise you might
use wiki.sugarlabs.org.

Thanks for working on this!

--
James Cameron
http://quozl.netrek.org/



___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Website Update for a/b testing

2018-12-20 Thread James Cameron 
Has this been done yet?  It has been very quiet since I gave this
summary.

On Thu, Dec 13, 2018 at 08:06:44AM +1100, James Cameron wrote:
> Thanks.
> 
> Gathering together the information so far;
> 
> 1.  meeting of community members during an oversight board meeting,
> https://wiki.sugarlabs.org/go/Oversight_Board/2018/meeting-log-2018-12-07
> chose a goal (A/B content testing), and a team of volunteers,
> 
> 2.  meeting of the team came up with several plans,
> http://meeting.sugarlabs.org/sugar-meeting/2018-12-09
> and an article on the value and process of A/B testing,
> https://circaedu.com/hemj/understanding-the-value-of-ab-testing/
> 
> 3.  Peace has forged ahead and made a mock-up of some design changes,
> http://lists.sugarlabs.org/archive/sugar-devel/2018-December/056034.html
> 
> Could the team please;
> 
> - decide how to measure engagement; e.g. time on page, click-through
>   to downloads; this is the metric,
> 
> - begin to measure, to establish the baseline,
> 
> - make some hypothesis,
> 
> - establish which metrics will define pass or fail,
> 
> - design an experiment,
> 
> - run the experiment,
> 
> - assess the results and come to a conclusion,
> 
> - iterate back to the hypothesis step,
> 
> I've turned on the GitHub Wiki feature for the repository
> https://github.com/sugarlabs/www-sugarlabs in case you'd like to use
> that for sharing your work in a central place.  Otherwise you might
> use wiki.sugarlabs.org.
> 
> Thanks for working on this!
> 
> -- 
> James Cameron
> http://quozl.netrek.org/

-- 
James Cameron
http://quozl.netrek.org/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Website Update for a/b testing

2018-12-12 Thread James Cameron 
Thanks.

Gathering together the information so far;

1.  meeting of community members during an oversight board meeting,
https://wiki.sugarlabs.org/go/Oversight_Board/2018/meeting-log-2018-12-07
chose a goal (A/B content testing), and a team of volunteers,

2.  meeting of the team came up with several plans,
http://meeting.sugarlabs.org/sugar-meeting/2018-12-09
and an article on the value and process of A/B testing,
https://circaedu.com/hemj/understanding-the-value-of-ab-testing/

3.  Peace has forged ahead and made a mock-up of some design changes,
http://lists.sugarlabs.org/archive/sugar-devel/2018-December/056034.html

Could the team please;

- decide how to measure engagement; e.g. time on page, click-through
  to downloads; this is the metric,

- begin to measure, to establish the baseline,

- make some hypothesis,

- establish which metrics will define pass or fail,

- design an experiment,

- run the experiment,

- assess the results and come to a conclusion,

- iterate back to the hypothesis step,

I've turned on the GitHub Wiki feature for the repository
https://github.com/sugarlabs/www-sugarlabs in case you'd like to use
that for sharing your work in a central place.  Otherwise you might
use wiki.sugarlabs.org.

Thanks for working on this!

-- 
James Cameron
http://quozl.netrek.org/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel