Ticket #1117 (closed prototype: fixed)

Opened 12 years ago

Last modified 12 years ago

New front page

Reported by: hans Owned by: tarmo
Priority: blocker Milestone: 1.8
Component: generic Version:
Keywords: Cc:
Time planned: Time remaining:
Time spent:

Description (last modified by hans) (diff)

LeMill front page is divided into two columns (see prototype 1).

The left column will be always the same:

  • logo (in the prototype it's just a placeholder, not final logo)
  • short slogan about LeMill ("Web community for finding, authoring and sharing learning resources.")
  • link to join LeMill
  • link to LeMill tour that will be a short presentation (5...6 slides) about LeMill

On the right column we will display a learning story (previously known as tips for use):

  • When user loads front page a random learning story will be selected
  • Three random cover images from that learning story will be also selected and displayed (content, method, tool)
  • Under each cover image a small button (arrow) is displayed. Another random cover image from that section (content, methods or tools) is selected when user clicks on the arrow.
  • If there is no learning story found about the new combination of cover images the system will display a message that encourages user to write her own learning story (see prototype 2).

Open questions:

  • What will happen when anonymous user clicks on the "Write your learning story" link? Do we redirect her to http://lemill.net/content/login_form, then to http://lemill.net/join_form and finally to a page where she can write a learning story?
  • We do not have a prototype for the page where user can write a learning story (and I do not have a good idea about that at the moment).
  • What is a good algorithm for arrow-button? I think that we must somehow keep the possibility of getting a combination that has a learning story around 50%. When it is totally random, only 1% of combinations will maybe have learning stories.
  • Is there a way to implement the arrow-button so that it doesn't require page reload?

I think that in the next release we should implement the front page without arrow-buttons (see prototype 3). We have only 5 days and we can't have an AJAX-based front page that is not tested properly in all browsers.

Prototype 1:

http://lemill.org/trac/attachment/ticket/1117/front_page_prototype1.png?format=raw

Prototype 2:

http://lemill.org/trac/attachment/ticket/1117/front_page_prototype2.png?format=raw

Prototype 3:

http://lemill.org/trac/attachment/ticket/1117/front_page_prototype3.png?format=raw

Attachments

front_page.png (82.1 KB) - added by hans 12 years ago.
front_page_prototype1.png (99.5 KB) - added by hans 12 years ago.
front_page_prototype2.png (87.4 KB) - added by hans 12 years ago.
front_page_prototype3.png (98.9 KB) - added by hans 12 years ago.

Change History

Changed 12 years ago by hans

comment:1 Changed 12 years ago by hans

  • Type changed from defect to prototype
  • Description modified (diff)

comment:2 Changed 12 years ago by hans

  • Description modified (diff)
  • Summary changed from LeMill has a front page to New front page

Changed 12 years ago by hans

Changed 12 years ago by hans

Changed 12 years ago by hans

comment:3 Changed 12 years ago by hans

  • Description modified (diff)

comment:4 Changed 12 years ago by hans

Teemu, please give your feedback about the layout ASAP. Then I can continue with XHTML/CSS.

comment:5 Changed 12 years ago by hans

  • Description modified (diff)

comment:6 Changed 12 years ago by teemu

The prototype 3 is ok, but I would group everything in the left bar: (1) the logo, (2) slogan (web community for ...), and (3) invitation (New to..) in a one portlet. This way there would be clearly only two portlets in the page, making grouping the Content, Method, and Tool in one more obvious.

I agree with Hans, that ee should spend more time to implement the "ajax" roll the resources player, to make it right from the first attempt. So, let's implement the prototype 3 now without the "rolling resources (arrows), do prototypes of the ajax UI, test them and only then put them online.

BTW: Thiese changes: te change of the home page + the change of the "activities" to the "methods" are so large that I would not implement them to the Toolbox right away. It is not good to change the major UI during the school testing.

comment:7 Changed 12 years ago by hans

  • Priority changed from waiting to blocker

OK. I was also thinking that it is problematic to make these changes to Toolbox skin. I will continue tomorrow with XHTML/CSS.

comment:8 Changed 12 years ago by tarmo

  • Owner changed from anonymous to tarmo
  • Status changed from new to assigned
  • Milestone set to 1.8

comment:9 Changed 12 years ago by pjotr

ATM ... Write your .... link is black and not underlined because of the Heading2 it is in.

So I suppose we just need to make it use some class, that will change it to something we want.

What color should be used for that one???

comment:10 Changed 12 years ago by tarmo

  • Status changed from assigned to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.