-
Notifications
You must be signed in to change notification settings - Fork 206
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Regarding "Giving Sugar Labs Website a New Look" #63
Comments
Thanks for reaching out, i am one of the mentors of the project.
Here is how you can get in touch with the community of developers
http://lists.sugarlabs.org/listinfo/sugar-devel
I don't really understand the other questions you asked.
Hoping to hear from you soon.
Samson G
…On Thu, Mar 2, 2017 at 2:22 PM, GeeKrypter ***@***.***> wrote:
Hi,
I am new to the sugar labs community and I am really looking forward to
contribute to this community. I have come across the "Giving Sugar Labs
Website a New Look" idea posted on "https://wiki.sugarlabs.org/
go/Summer_of_Code/2017". Being a UI/UX designer and developer, I was
really excited to draft my proposal based on this idea for GSOC 2017. But I
have few queries which I wish would be answered.
1.Is there a mailing list which I could join for communication?[I was not
able to find it.]
2.Should I be posting the UI mockups in form of Issues on github or is any
preferred way?
3.As mentioned on https://github.com/sugarlabs/www-sugarlabs/blob/master/
STRUCTURE.md, is there any particular design aspects that is being looked
into adopting from {https://learningequality.org and http://haxe.org}?
I hope my queries will answered as soon as possible so that I can start
contributing to this exciting community.
Thank you.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#63>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFxLWQD2ePG0fg9UFjnYnPTmeu-SsN_0ks5rhsKDgaJpZM4MQ-lT>
.
|
Hi @samswag, I apologise for not phrasing my queries in a proper way. Below the rephrased queries:
Thank you. |
You can share your designs here. Maybe send images from screenshots. First the if you take a look at the proposed plan, you will see that this website mentioned gives you examples of what we would like the website to be or become. Unlike our current website, most of the information have been outdated, birth of new projects like the sugarizer. So we basically need a interactive website where both developers, learners, teachers and possible donors can easily understand. For example Sugar is available on windows, IOS and android (http://sugarizer.org/). Also great footers like the haxe website, we we can add our social media links and other details. I hope this helps. Samson G |
Thank you @samswag, I will start working on the design and keep you updated. |
Sure, may the force be with you. |
Thanks for looking into this. Please ensure the web site works with Sugar itself. The Sugar browser; the Browse activity, contains a link to www.sugarlabs.org, and so the result must be successfully rendered and responsive; or the site should identify Browse and redirect to a simpler site. Most users of Sugar are using Browse-157.3 or slightly earlier, upon WebKit 1.10. New users of Sugar will be on WebKit 2.14 or later. Please also briefly research and understand why several previous redesign efforts have faltered. It hasn't been for lack of ideas, but for failure to achieve a consensus on the design changes. Early functioning pages on web servers that can be tested with Sugar would help. Designs shared as screenshots won't get as much testing. |
Duly noted, thanks for the tips.
…On Fri, Mar 3, 2017 at 7:31 PM, James Cameron ***@***.***> wrote:
Thanks for looking into this.
Please ensure the web site works with Sugar itself. The Sugar browser; the
Browse activity, contains a link to www.sugarlabs.org
<https://github.com/sugarlabs/browse-activity/blob/master/data/index.html#L55>,
and so the result must be successfully rendered and responsive; *or* the
site should identify Browse and redirect to a simpler site. Most users of
Sugar are using Browse-157.3 or slightly earlier, upon WebKit 1.10. New
users of Sugar will be on WebKit 2.14 or later.
Please also briefly research and understand why several previous redesign
efforts have faltered. It hasn't been for lack of ideas, but for failure to
achieve a consensus on the design changes. Early functioning pages on web
servers that can be tested with Sugar would help. Designs shared as
screenshots won't get as much testing.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#63 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFxLWb-j372mKKBUt6Iuq7QkRZHXRl1Wks5riFx4gaJpZM4MQ-lT>
.
|
Thank you for the advice @quozl . Will take it into consideration. |
Hi @samswag, I apologise for the delayed response. In the meantime, I redesigned the Sugar website and integrated my design into the original Sugar website source code in my local machine. I have considered to use parallax scrolling as a design feature and would like to know if I could get any background images that could be used for the website or should I just take any suitable images? Note: Thank you. |
Hi @samswag, I have added background images taken from "http://planet.sugarlabs.org" and also logo was taken from "https://wiki.sugarlabs.org/go/Marketing_Team/Logo" for the redesigned website. I request you to provide feedback on my website design and would love to modify as required. Thank you. |
Can you host in github? That would be better.
On 12 Mar 2017 3:21 pm, "GeeKrypter" <[email protected]> wrote:
Hi @samswag <https://github.com/samswag>, I have added background images
taken from "http://planet.sugarlabs.org" and also logo was taken from "
https://wiki.sugarlabs.org/go/Marketing_Team/Logo" for the redesigned
website.
If possible do suggest any other background images that I could use for the
website.
I took a screen recording showcasing the website and below is the link to
view it:
https://drive.google.com/open?id=0B4WvXpWS9zoRYTc2X2VFSVdVaXM
I request you to provide feedback on my website design and would love to
modify as required.
Thank you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#63 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFxLWWA-iLNhvvFrBG8hJoK6nfgoIZ_Zks5rk_88gaJpZM4MQ-lT>
.
|
I like the concept of the website, but if you can host it in github pages that would be awesome for me and my fellow mentors to have a better view and possible land some comments and suggestions. |
Hi @samswag, I again apologise for the late reply. Based on your suggestion, I have hosted my redesign of "SugarLabs" website using Github Pages. URL: I would be looking forward for feedback from you and the rest of the mentors. Would be open to any modifications and keep improving my design. Thanks, |
Thanks, very interesting. On a slow data link the page loaded very slowly; total of 6MB, mostly caused by bg3.png a 3.42 MB image, but also because of the number of requests made (35). There were four (4) bursts of requests. Photographic images may be better in JPEG format. Some assets may be better encapsulated in the HTML to lower the number of requests, as requests add latency over slow links. On Ubuntu 16.04 with Browse-200.1 the page rendered and scrolled without problem, though on some laptops the fan would start.
On XO-4 with Browse-157.3, the page rendered slowly and scrolled slowly.
On XO-1 with Browse-157.3, the page loaded slowly, rendered slowly, and scrolled slowly.
Other laptop models not checked, as the above are representative of the range. For your interest, the approximate quantities manufactured by model were;
Most contained a link to activities.sugarlabs.org, which links to www.sugarlabs.org. By security design, it is not known how many are still in use, but based on anonymized update requests in server logs the number is considerable. Suggestions:
|
Hi @quozl, Thank you for your feedback. I have made the following changes to improve the website speed and additional corrections: 1.Replaced bg3.png with another image taken from "http://planet.sugarlabs.org" Please test the website speed and provide your feedback. I do have the following to-do list and will inform you once I am done with them: 1."detect Sugar as browser and disable animations, or reduce the animation frame rate". I have few queries which I hope could be answered: 1.Other occurances of "One Laptop Per Child" were mostly in the posts, should I change them too? Thank you. |
First, i am going to send you better pictures for the website. In my end, I tested the website using the updated version of Chrome from my Macbook, it pretty fine here but not too good with safari. But have some issues about the logo of the website. If you look at the current website, you will notice that the logo changes also with the favicon. We intend to keep that in check. Also speaking the color of the website it will be nice if one scrolls down it logo changes to a different color same with the favicon and the current page color. For example, this current website you hosted has blue and white background color same with the Secondly, Sugarizer is our newest project that is basically the future of sugar because of it easy installation process. Currently it is hosted and maintained by our team down in France, but we want to make new comers feel welcomed and get more like a "trailer version" of Sugar. Above is a screenshot from the current website, it is an image of Sugar interface, but we want to replace that with a frame of Sugarizer (http://try.sugarizer.org/). It will be like a frame of a space of a youtube, but instead of a video it will be a live JS version of the try.sugarizer.org (sugarizer). I will reach out to the other mentors for comments, but use https://github.com/sugarlabs/www-sugarlabs/blob/master/STRUCTURE.md as a guide. Samson Goddy Sent from my Android |
Well, if you are deprecating the Sugar desktop environment in favour of Sugarizer, because of ease of installation, then I've no further need to be involved in the web site design. You can also;
|
Nope don't get me wrong, i was only making some suggestions. There is no point for you to leave, i am speaking based on this line "Leads: Consideration, Try Outs, Action Flows" based on the https://github.com/sugarlabs/www-sugarlabs/blob/master/STRUCTURE.md, there is a plan to add "try now" on the website since Sugarizer is the taste of Sugar (not full Sugar experince like that of the Python version). |
I was giving a glance on how the "try now" which is the "Sugarizer" for people(new comers) who knows nothing about sugar. Your work is really helpful especially in the area of testing the site on Ubuntu and xo browsers. |
basically i agree with quozl
its too heavy for an XO
I recommend:
zero JS
zero images
just html and CSS
|
a core idea of design
is that for follows function
since the site must be functioning for very low end computers
that will determine the form of the website
how it looks
it is not good to then design a website that cant function
with another form
eg, the XO is bright green
because the function is to look fun for kids and not like an adult's
computer
so the form follows that
and it becomes an important 'motif'
repeated in other places
so
the website will look a certain way to function on XOs
and that should be embraced
|
@geekrypter, to answer your questions;
It would depend on the context; you decide. Where the context is referring to the organisation, the registered name of the organisation has been "One Laptop per Child Association Inc", and is now "OLPC, Inc". We use "One Laptop per Child" in new source code copyright statements. Where the context is referring to an idea of one laptop for every child, it may be better to use a more common education market term such as one-to-one computing.
I've no opinion. I ignore the images unless they cause a problem. Such as page load time.
Not necessarily. Don't respond automatically. Whether to use PNG or JPEG depends on the type of image and the use to which it is put. My reason for mentioning use of JPEG was that a photograph will be smaller, and so download quicker, yet you had used PNG for the photograph. On the other hand a UI screenshot will be smaller as a PNG. Please use appropriate tools to convert images between formats, choose an appropriate JPEG image quality, and then compare the file sizes between PNG and JPEG. The size in bytes should be minimised, so that page load times are minimised, yet without degrading appearance. You will also notice that SVG is a special case; it can scale, and can be very small.
You may have misunderstood what I was saying; I'll try again. There were produced roughly 2.6 million laptops, and we still produce them on demand, and the laptops have Sugar on them, and the Browse activity when launched has a default starting page with a link to activities.sugarlabs.org. When you visit activities.sugarlabs.org, you will find a link to www.sugarlabs.org. My purpose in mentioning this was to give you an idea of the impact to the installed base of changes to www.sugarlabs.org, and the potential for bad experiences if the site is difficult to use. |
+1 @quozl for the clearance |
Only mentioned copyright statements because that's where I fix it most. But for this new work, any copyright can be either yours, or assign it to Sugar Labs. License should probably be one of the Creative Commons. |
License ought to be BY or BY-SA
On Mar 15, 2017 6:49 PM, "James Cameron" <[email protected]> wrote:
Only mentioned copyright statements because that's where I fix it most. But
for this new work, any copyright can be either yours, or assign it to Sugar
Labs. License should probably be one of the Creative Commons.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#63 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAP9y-7DYxnpl4Nex8XHfyEvnOo3T1fEks5rmGsGgaJpZM4MQ-lT>
.
|
Thank you @samswag, @davelab6, @quozl, for spending time in involving in the discussion and helping me. Since it was a long and interactive discussion, I would like to break it up and respond in parts. 1.Thanks @quozl for giving clarification to my queries. Thank you. |
i will come up with a better explanation later. |
Hi, Made few changes:
Please provide your feedback. Thank you. |
Hi, Made the following changes: To solve issue 65, made the below changes:1.Changed the navigation bar: To solve issue 22, made the below change:1.Added a new page called "libre software culture" which can be accessed through the footer or at "https://geekrypter.github.io/sugarLabsWebsiteRedesign/about-libre-software-culture/" Optimization:
Please provide your feedback. Thank you. |
Hi, I apologise for not updating what I was working on for the past 8 days. (I was working on the changes but did not post them here) I will list out all the changes I have worked on below based on dates. 20th June to 26th June:Changes:
Optimization:
27th June:Changes:
Optimization:
Thank you. |
Hi, I will list out all the changes I have worked on below based on dates. 28th July - 4th JulyChanges:
5th July - 11th JulyChanges:
Optimization:Changes were made for optimization but did not note them down. Please provide your feedback. |
Sean Daly isn't involved in Sugar any more AFAIK; you can use me or walter
in his spot :)
…On 13 July 2017 at 10:29, GeeKrypter ***@***.***> wrote:
Hi,
I will list out all the changes I have worked on below based on dates.
------------------------------
####28th June - 4th June
#####Changes:
1. Added a loader screen with animations.[The main concentration was
this in this period]
2. Created a new page which can be reached at
"https://geekrypter.github.io/sugarLabsWebsiteRedesign/booting-soas/"
or through the "downloads section".
3. About link in the header has been linked to the "about us" page of
website.
4. Maze image screenshot in "Glimpse of Sugar" section has been
changed.
5. There was an issue for the device animation in the loader screen so
tried different solutions to fix the issue.
6. For the desktop, added an info icon next to the + button and on
clicking it, the user is directed to the about irc page.
7. For the mobile, added an info icon next to the title and on
clicking it, a popover will prompt the user if he/she would like to know
more about irc and on clicking it the user is directed to the about irc
page.
8. Fixed the below line issue.
[image: capture]
<https://user-images.githubusercontent.com/9636925/28171174-35be231a-6805-11e7-838d-e832d03df0cf.PNG>
------------------------------
####5th June - 11th June
#####Changes:
1.
Header color for mobile changed to a bit lighter color accent.
2.
The "Glimpse of Sugar" slideshow has been changed.
3.
(Chat window for desktop):
a. Title font increased
b. The info icon placed next to the title instead of close button and
its size is also increased.
c. The hover text will appear on top instead of left side.
4.
(Chat window for mobile):
a. Title font increased.
b. Info icon size increased.
5.
Added a thumbnail for the video in the main page.
6.
Added a new page in the attempts of redesigning this page
https://developer.sugarlabs.org <https://developer.sugarlabs.org> and
the result can be found at https://geekrypter.github.io/
sugarLabsWebsiteRedesign/developers/
<https://geekrypter.github.io/sugarLabsWebsiteRedesign/developers/>
7.
Added a new page in the attempts of redesigning this page
https://developer.sugarlabs.org/what-can-i-do.md.html
<https://developer.sugarlabs.org/what-can-i-do.md.html> and the result
can be found at https://geekrypter.github.io/sugarLabsWebsiteRedesign/
developers/what_can_i_do.html
8.
A lot of mini changes were made to the main page of the website.
9.
Also instead of the long quote of walter bender, replaced it with a
simpler quote.
10.
Fixed the below line issue.
[image: screen shot 2017-07-08 at 11 55 41 pm]
<https://user-images.githubusercontent.com/9636925/28171017-c6caec2c-6804-11e7-9d88-5a2b1919e138.png>
11.
The chat window for desktops was not that responsive before, now it is
better.
12.
The background image was not scaling properly before, it is better now.
13.
The buttons in the developers page was not properly rendering to the
correct section of the website, now it is working properly.
14.Decreased the height of the background image section and it now
looks neat.
15.The buttons section of developers page is more neat with clearer
white text color and background color.
#####Optimization:
Changes were made for optimization but did not note them down.
------------------------------
####12th June
#####Changes:
1. The chat icon window that appears for mobile screens now appears
for tablet screens.
2. The chat icon window has been changed in terms of the icon itself,
different styling for tablet and mobile screens, etc.
3. One of the fun facts "20,000 cups of coffee" has been removed for
now.
4. The fun facts area on the main page has been rearranged to be
responsive for 3 fun facts.
5. The colors of social media icons floating have been changed.
6. The colors of social media icons in the footer have been changed.
7. The padding for chat icon window that appears for mobile screens
was readjusted.
8. The padding for chat icon window that appears for mobile screens
was readjusted.
------------------------------
Please provide your feedback.
Thank you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#63 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAP9yx86ZWYA0xmn-JxfvbQFiWtV8Evkks5sNinMgaJpZM4MQ-lT>
.
--
Cheers
Dave
|
@davelab6 , thanks a lot for the information. :) |
Hi, I will list out all the changes I have worked on below based on dates. 12th July - 17th JulyChanges:
Optimization:Changes were made for optimization but did not note them down. 18th July - 24th JulyChanges:
Optimization:
Please provide your feedback. |
When will this reach production? Looking at your GSoC proposal, plan
was "Fix final merging issues" on August 11th to 13th.
|
Hi @quozl , I did not quite understand the context of your comment. Could you explain more? |
Really? Could you instead tell me which part of my message you had
trouble with?
|
Hello @quozl i didn't also understand the message. You mentioned "When will this reach production" do you mean hosting the website?, so i believe @geekrypter question is related to mine. |
Sorry, must be language issues. This should help;
https://en.wikipedia.org/wiki/Software_development#Deployment_and_maintenance
"Deployment starts directly after the code is appropriately tested,
approved for release, and sold or otherwise distributed into a
production environment. This may involve installation, customization
(such as by setting parameters to the customer's values), testing, and
possibly an extended period of evaluation."
In this case, the production environment is the virtual host pointed
to by the DNS record for www.sugarlabs.org.
|
Hi @quozl, |
On an OLPC XO-4 with Browse-157.4, your site consumes 30% CPU
cycles after initial page load and before scrolling. 4.8 watts.
This compares to 12% CPU cycles of www.sugarlabs.org or a static page
with no JavaScript. 3.8 watts.
Could you change your JavaScript code to be active only when needed?
p.s. nothing happens if mouse is clicked on "Chat on our IRC" text.
|
Thanks @quozl for the input. For the chat window, we should be clicking on the "+" symbol to expand it. But, I am changing it so that the chat window will be expanded only when a user clicks on the "Chat on our IRC" text. Regarding the cpu usage, its mostly due to the loader animations. We are planning to change the loader and keep it as simple as possible. |
@geekrypter i think it'll be nice if it expands when you click on any part of the chat, not just on the text, and in a private browser the chat doesn't come up. |
Thanks @chimosky for the suggestion. Will surely look into it. There is a minor problem with the chat window currently which I am working upon. Do provide more suggestions if any. |
As for the private browser it's working fine now. |
@chimosky, thanks for update :) |
Hi, I will list out all the changes I have worked on below based on dates. 25th July - 1st AugustChanges:
2nd August - 8th AugustChanges:
Optimization:
Please provide your feedback. |
Disagree with some of your changes.
* we already have https://developer.sugarlabs.org/ maintained as
restructured text in https://github.com/sugarlabs/sugar-docs yet
your developer section is seeking to squat on this concept-space and
moving maintenance to git `www-sugarlabs`?
* we already have Raspberry Pi, Rasbian, and Debian content in
https://wiki.sugarlabs.org/ maintained as Wiki-text using either web
browser or `git-mediawiki`, yet your developer section is acquiring
this with the expectation of moving maintenance to git
`www-sugarlabs`?
* your plans will briefly provide two places for some content,
doubling the cost of maintenance, or making content out of date,
* your plans will reduce the number of people willing to make edits,
as we have seen that using git effectively is one hurdle too far for
many people, and HTML is way harder to learn than restructured text
or Wiki-text.
Please remove the developer content, link that concept to
https://developer.sugarlabs.org/ and make new commits in `sugar-docs`;
especially adding CSS so the sites will have the same user experience,
and common navigation.
Please do make new commits in `help-activity` adding CSS so that
https://help.sugarlabs.org/ will have the same user experience, and
common navigation.
Please do not add content for the Raspberry Pi Debian work, as it is
not finished, and is much lower user experience than the Raspberry Pi
Fedora SoaS.
Please do reference the Raspberry Pi Fedora SoaS build, as this is
working very well, and has many activities. See
https://wiki.sugarlabs.org/go/Raspberry_Pi
https://wiki.sugarlabs.org/go/Sugar_on_a_Stick
Please do work with Jatin Dhankhar to get the new ASLO to use your CSS.
Your scope has crept, and you have not asked for wider consensus for
these changes to intended audience. You're probably operating in a
filter bubble with other GSoC participants.
You have enough content already for the site and should be focusing on
SEO, integration with other Sugar Labs sites, and going live.
Hope that helps! 😁
|
Thanks a lot for the suggestions, @quozl. I will surely keep them in mind and do the necessary changes :) |
Hi, I will list out all the changes I have worked on below based on dates. 9th August - 28th AugustChanges:
SEO:
Optimization:
Please provide your feedback. |
@geekrypter really good work. Congrats on sucessfully completing and becoming a mentor this year!! I am hopeful to get a chance to work on the social website for sugarlabs with all of you!! will share my proposal soon. |
Looking forward to
…On Sat, Mar 24, 2018, 10:19 PM Love Mehta ***@***.***> wrote:
@geekrypter <https://github.com/geekrypter> really good work. Congrats on
sucessfully completing and becoming a mentor this year!! I am hopeful to
get a chance to work on the social website for sugarlabs with all of you!!
will share my proposal soon.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#63 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFxLWe4jeRkkWYt8eCQ_LWbjyClR2MMvks5thrg9gaJpZM4MQ-lT>
.
|
Hi,
I am new to the sugar labs community and I am really looking forward to contribute to this community. I have come across the "Giving Sugar Labs Website a New Look" idea posted on "https://wiki.sugarlabs.org/go/Summer_of_Code/2017". Being a UI/UX designer and developer, I am really excited to draft my proposal based on this idea for GSOC 2017. But I have few queries which I wish would be answered.
1.Should I be posting the UI mockups in form of Issues on github or is any preferred way?
2.As mentioned on https://github.com/sugarlabs/www-sugarlabs/blob/master/STRUCTURE.md, is there any particular design aspects that is being looked into adopting from {https://learningequality.org and http://haxe.org}?
I hope my queries will be answered as soon as possible so that I can start contributing to this exciting community.
Thank you.
The text was updated successfully, but these errors were encountered: