[Sugar-devel] Merging sugarlabs.org website to new technology

[Tymon Radzik]

Thanks, Sai Vineet!

Yes, I plan to use Jekyll's post mechanism to create press blog posts. So
this feature'll be used probably :-)

Mon Feb 23 2015 at 15:19:50 użytkownik Sai Vineet <saivineet89 at gmail.com>
napisał:

> +1 to Jekyll! I use it for my blog as well. I can help with the website
> after my exams (about 3 weeks later).
>
> Jekyll is blog aware, maybe we could use that feature?
> On Feb 23, 2015 3:53 AM, "Tymon Radzik" <dwgipk at gmail.com> wrote:
>
>> Hello Sam,
>>
>> thank you for your suggestions, as I told I will implement at least some
>> of them (I mean activity log and sugarizer).
>> I will think also which activity should we present (again, all
>> suggestions are welcome!).
>>
>> I like Bootstrap, I also think its default templates are quite nice. I
>> understand landing page should show something "special" and I agree with
>> that. Currently, to make this website more personalised for Sugar I added
>> this random-color logo and favicon and also loading bar with our logo. I am
>> still waiting for suggestions what can I customize more (maybe background
>> image or different navbar color?).
>>
>> That is not good that every Sugar website looks differently. They also
>> should base on one readable and nice template (maybe without wiki...) or at
>> least have some common points, navigation, etc. We can try to create some
>> kind of this nice template here and then apply it to other sites.
>>
>> I will probably use GTKRecordMyScreen, I asked because I just thought
>> some of them are already recorded.
>>
>> Best,
>> Tymon
>>
>> Sun Feb 22 2015 at 22:09:39 użytkownik Sam P.
>> sam.parkinson3 at gmail.com> napisał:
>>
>> Hi Tymon,
>>>
>>> It does look clean and modern.  But this is a landing page, it has to
>>> convey the message of sugar.  The websites need a personality to do that.
>>> The bootstrap theme won't do that.
>>>
>>> I will implement Sugar colors and random Sugar logo image. Many people
>>> like this idea.
>>>
>>> Activity stream also shouldn't be something really hard to implement. I
>>> gonna work on this tomorrow.I can add also embeeded Sugarizer, what is your
>>> opinion which activity should we mainly present?
>>>
>>>  IDK... But you don't have to put all that stuff in!  It would probably
>>> get easily overloaded with content then!
>>>
>>> I am not sure about videos... I don't have them, recording will take
>>> some time,... Do you have any place where can I find already recorded
>>> movies? Btw your idea to put it inside XO frame is really nice and
>>> interesting...
>>>
>>>  Maybe you could use GTK-RecordMyDesktop
>>>
>>> What is your exact idea about pictures? Should we place them everywhere
>>> or only in gallery? Currently we put ~2 thumbnails with link to gallery on
>>> every one page. Also - any ideas where can I find that kind of photos?
>>>
>>>  Pictures can be used as background images for sections of the site.  I
>>> will find an example.
>>>
>>> I don't understand your message about consistent with other web
>>> proporties, but I agree you activity-2 website is nice (I embed it in
>>> Activities section if my project).
>>>
>>>  Right now every sugar site looks different.  Maybe we could have some
>>> visual clarity.
>>>
>>> Thanks,
>>> Sam
>>>
>>> Looking forward your reply.
>>>
>>> Best,
>>> Tymon
>>>
>>> ps sorry I cant sign this message, i dont have gpg on phone
>>>
>>> On Sun 22 Feb 2015 at 00:27 Sam P. <sam.parkinson3 at gmail.com> wrote:
>>>
>>>
>>>  Hi Tymon,
>>>
>>> On Sun Feb 22 2015 at 2:56:21 am Tymon Radzik <dwgipk at gmail.com> wrote:
>>>
>>>
>>>  -----BEGIN PGP SIGNED MESSAGE-----
>>>
>>> Hash: SHA1
>>>
>>> Hello,
>>>
>>> I talked with Walter Bender about refactoring and improving current
>>> http:// <http://sugarlabs.org/>sugarlabs.org/ <http://sugarlabs.org/>
>>> website and decided to work on this project.
>>>
>>> I have created website basing on Jekyll (http:// <http://jekyllrb.com/>
>>> jekyllrb.com/ <http://jekyllrb.com/>), Liquid templates and Github
>>> Pages. It is possible to see it here: http://
>>> <http://people.sugarlabs.org/~tymon>people.sugarlabs.org
>>> <http://people.sugarlabs.org/~tymon>/~tymon
>>> <http://people.sugarlabs.org/~tymon> (I know "Gallery" and "Press"
>>> sections don't work, I am currently working on this matter). My source code
>>> is avaliable in this repo - https
>>> <https://github.com/walterbender/www-sugarlabs/pull/1>://
>>> <https://github.com/walterbender/www-sugarlabs/pull/1>github.com
>>> <https://github.com/walterbender/www-sugarlabs/pull/1>/walterbender/
>>> <https://github.com/walterbender/www-sugarlabs/pull/1>www-sugarlabs
>>> <https://github.com/walterbender/www-sugarlabs/pull/1>/pull/1
>>> <https://github.com/walterbender/www-sugarlabs/pull/1> (giving link to
>>> pull request as my changes are not merged yet).
>>>
>>> I would like to as you for your suggestions about this website, info
>>> what should be fixed/improved/added.
>>>
>>>
>>>  I really like the idea of using a static site generator (less server
>>> load!).
>>>
>>> I like the idea of modernizing the website.  It looks like a dodgy
>>> BTC/illegal website now IMHO, so we should really change it.
>>>
>>> However, I'm sure about replacing it with a website that is basically
>>> the default theme of jekyll.  I think that you need to start with a design
>>> idea about where we should go with the site.   Here are a few suggestions:
>>>
>>> * Embed sugarizer/turtlejs?  That is the easiest way show people what
>>> sugar is!
>>>
>>> * Pictures?  Happy pics of pople using sugar are always  good for a
>>> landing page (www. is really just a big ad for sugar, all real info is on
>>> the wiki?)
>>>
>>> * Use sugar colors.  Maybe this will help?  https
>>> <https://github.com/SAMdroid-apps/aslo/blob/master/web/css/_colors.sass>
>>> ://
>>> <https://github.com/SAMdroid-apps/aslo/blob/master/web/css/_colors.sass>
>>> github.com
>>> <https://github.com/SAMdroid-apps/aslo/blob/master/web/css/_colors.sass>
>>> /SAMdroid-apps/
>>> <https://github.com/SAMdroid-apps/aslo/blob/master/web/css/_colors.sass>
>>> aslo
>>> <https://github.com/SAMdroid-apps/aslo/blob/master/web/css/_colors.sass>
>>> /blob/master/web/
>>> <https://github.com/SAMdroid-apps/aslo/blob/master/web/css/_colors.sass>
>>> css
>>> <https://github.com/SAMdroid-apps/aslo/blob/master/web/css/_colors.sass>
>>> /_
>>> <https://github.com/SAMdroid-apps/aslo/blob/master/web/css/_colors.sass>
>>> colors.sass
>>> <https://github.com/SAMdroid-apps/aslo/blob/master/web/css/_colors.sass>
>>>
>>> * Consistent with other web properties?  Here is my idea of how we
>>> should be consistent, but this is a topic for discussion:  https
>>> <https://activities-2.sugarlabs.org/>://
>>> <https://activities-2.sugarlabs.org/>activities-2.sugarlabs.org/
>>> <https://activities-2.sugarlabs.org/>
>>>
>>> * Live activity stream?  Could we have a live activity stream from ASLO
>>> + SocialHelp + Mailing List + Wiki?  That would be really cool!
>>>
>>> * Video demos?  Having little videos embed transparently in the site is
>>> very nice on the android design site:  https
>>> <https://developer.android.com/design/building-blocks/tabs.html>://
>>> <https://developer.android.com/design/building-blocks/tabs.html>
>>> developer.android.com
>>> <https://developer.android.com/design/building-blocks/tabs.html>/design/
>>> <https://developer.android.com/design/building-blocks/tabs.html>
>>> building-blocks
>>> <https://developer.android.com/design/building-blocks/tabs.html>/
>>> <https://developer.android.com/design/building-blocks/tabs.html>tabs.
>>> html <https://developer.android.com/design/building-blocks/tabs.html>
>>> Possibly we could have demos inside a XO frame or a desktop monitor
>>>
>>>
>>>  There is also a case of hosting this website. We can use GitHub pages
>>> with their CDN, etc. (we'll just have to change DNSes of domain) or host
>>> website on one of our machines (and e.g. auto-pulling from repository) -
>>> instrunctions for sysadmins are here: https
>>> <https://help.github.com/articles/using-jekyll-with-pages/>://
>>> <https://help.github.com/articles/using-jekyll-with-pages/>
>>> help.github.com
>>> <https://help.github.com/articles/using-jekyll-with-pages/>/articles/
>>> <https://help.github.com/articles/using-jekyll-with-pages/>
>>> using-jekyll-with-pages
>>> <https://help.github.com/articles/using-jekyll-with-pages/>/
>>> <https://help.github.com/articles/using-jekyll-with-pages/> . Advice
>>> from somebody from Infrastructure Team is really welcome.
>>>
>>> I don't think Github can do TLS for our domain, so I would just keep it
>>> on sunjammer.  + I haven't read great things about their "CDN".  Setting up
>>> a pulling & building webhook is very easy.  But deployment is a long time
>>> away :)  Just make a nice site and we can deploy easy :)
>>>
>>>
>>>
>>> Thanks,
>>>
>>> Sam
>>>
>>>
>>>
>>> Regards,
>>>
>>> Tymon
>>>
>>> GPG Signature: 0017 C42D AB1A B31F B82F  3E1C 65A2 9FFD EF2F 0D25
>>>
>>> -----BEGIN PGP SIGNATURE-----
>>>
>>> Version: GnuPG v2
>>>
>>> iQIcBAEBAgAGBQJU6LdJAAoJEGWin/3vLw0ljGEP/iycVVvbN1UCjlvVD2nvA1Lj
>>>
>>> DsyDnXzP9HoUP+fbWFvNujvcD81FPsQxAUrl4eeI5/1Quf1LgjvJ7K5l+60QJmPI
>>>
>>> yDZ5facrN8SR5FnfiJBSMCHzM//7TxCMwd4mkTfappv2g1tTdkDqPI+aGr/qO57N
>>>
>>> lU25cNJ3JhWtPwia/a5ZpamNIl6b/IGFoabddg+7iM/XZkUXt2RDNy0HKTgc9zrG
>>>
>>> YF7vfY/6oOBaW0pzdHtEMvab49wC1e6bwnhlUYO85lYKQbCXH8Jr7N5QGS0FpRAN
>>>
>>> Sfh3reUKXMg5wI17b0ivse2EJMvYvsERyWtU120jK3Rz2b3JAGBDY3airlyWjkPd
>>>
>>> Ff9OoG85+AG41a0WW6JVsaj5OtmuoWCXIVNcoIJvNeDuZpjQmLp3jBIcJ1h9ot88
>>>
>>> 1HYC+diZ581BVnd9794H68c9hmpHmScFOYxVxew+8NKZG73qR0fiZciZO3ZCqYEo
>>>
>>> 45XQFDTxCR04qYJNMwb/u9fn4c2LcKR/PMtfmS33LYCJIs57FhtSR5/X4ndJPYD6
>>>
>>> s+t8oFGaFRBzBUtVzevLKwyXsF+Pus8n+PSG1gRiwVbL23GJPS9zpcqIyJ+EEqVQ
>>>
>>> XUK5lsONrthr4dVwUpHVRxONAYQbH6xuH89zRPImK97MHeDrbeVOd1mWq/QjMgkp
>>>
>>> wsNJUyXtsxF3sYZW312D
>>>
>>> =ReI2
>>>
>>> -----END PGP SIGNATURE-----
>>>
>>>  _______________________________________________
>>> Sugar-devel mailing list
>>> Sugar-devel at lists.sugarlabs.org
>>> http:// <http://lists.sugarlabs.org/listinfo/sugar-devel>
>>> lists.sugarlabs.org <http://lists.sugarlabs.org/listinfo/sugar-devel>/
>>> <http://lists.sugarlabs.org/listinfo/sugar-devel>listinfo
>>> <http://lists.sugarlabs.org/listinfo/sugar-devel>/
>>> <http://lists.sugarlabs.org/listinfo/sugar-devel>sugar-devel
>>> <http://lists.sugarlabs.org/listinfo/sugar-devel>
>>>
>>>
>> _______________________________________________
>> Sugar-devel mailing list
>> Sugar-devel at lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20150223/5cb0de6b/attachment-0001.html>