Hello everyone,
I'm Fabio, a master student at the HPI Software Architecture Group.
As you might have heard already, Marcel Taeumel and I are working on a
Squeak.org update.
You can find our latest version at: https://fniephaus.com/squeak.org/
Please feel free to provide as much feedback as you wish. We're happy to
incorporate your ideas.
Marcel and I are wondering how the current page is being served.
Also, we are looking for a good way to serve the new site while still being
able to update it collaboratively.
Currently, our version is being developed and hosted on GitHub and can
therefore be changed easily.
Could someone please point us in the right direction?
Many thanks and kind regards,
Fabio
--
Fabio Niephaus
IT-Systems Engineering Student
Hasso-Plattner-Institut für Softwaresystemtechnik GmbH, Potsdam
Prof.-Dr.-Helmert-Str. 2-3
D-14482 Potsdam
www.hpi.de
Amtsgericht Potsdam, HRB 12184
Geschäftsführung: Prof. Dr. Christoph Meinel
http://box4.squeak.org:9971/seaside/ss
Here's a beta to replace map.squeak.org. Not all of the features work (Join, New Proejct, Save in the Your Project form). I didn't see much point in doing everything until qmail is installed on box4.
It's Seaside2.8 and SS2. (Well, I've removed Magritte and re-installed SSTableReport, so perhaps I'm hacking SS2Retro). I'll save SS2Retro to its own repo. I'll then push SMServer to the SqueakServices repo.
Chris
cc'd to box-admins, as there's some overlap
squeak.org issues list:
- zip resources for faster download
- use minified versions of files
- get that 404 image (broken paper showing a code browser) out of my email Archive and install
- check multi platform layouts (i.e. cell phone, tablet)
- doesn’t work on IE8
- sometimes hogs the CPU, needs to be watched
Levente is right, we need to get the new website set up under a
webteam id, that only has access to what it needs for the website.
Chris C., yourself, and Timothy (if he wants), and I'm interested too,
added as group members.
This would take care of the immediate security need, as well as
distribute some of the burden currently concentrated on Chris C.
Chris C., is this something you would like to handle or would you
prefer someone else do it?
On Fri, Mar 28, 2014 at 10:50 PM, Levente Uzonyi <leves(a)elte.hu> wrote:
> On Thu, 20 Mar 2014, Levente Uzonyi wrote:
>
>> On Thu, 20 Mar 2014, Chris Cunnington wrote:
>>
>>> locator at: (ALPath / 'favicon.ico')
>>> put: (ALFileResource on: (FSLocator imageDirectory /
>>> 'squeakfavicon.ico') resolve)
>>>
>>> This code is in the current squeak.org image for the favicon, which is a
>>> file in the imageDirectory. The simplest thing is for Altitude to be fed a
>>> path to wherever Levente wants to put the files for the homepage. The files
>>> currently served from my webpage could then be dropped into that directory.
>>> Then I can change the absolute references to my site to the disk from:
>>>
>>> html footer: [ html img src:
>>> 'http://www.chriscunnington.com/poweredsqueak.png'].
>>>
>>> to something like:
>>>
>>> html footer: [ html img src: (ALPath / 'poweredbysqueak.png') ].
>>>
>>> That is if the image will handle it's own files. If we are separating
>>> static and dynamic requests in nginx for speed and such, then I think I
>>> need to change the links to something in Altitude like:
>>>
>>> html footer: [ html img src: '/img/foo.jpg' ].
>>>
>>> with a locator like:
>>>
>>> locator at: (ALPath / 'img' / 'foo.jpg') put: (ALFileResource on:
>>> FSReference * 'img' / 'foo.jpg')
>>>
>>> where nginx sees the token /img/ and sends the request to wherever the
>>> static files are served from.
>>
>>
>> The goal is to let nginx serve the static files, and let the browsers and
>> proxies cache them forever.
>>
>> I wanted to use a separate subdomain (or a set of subdomains) for the
>> static files, but it's easier for now to use a path prefix with the
>> following pattern:
>>
>> /static/*/...
>>
>> Where * is the version label - a sequence of alphanumeric characters, and
>> ... is the actual path to the resource. For example for /img/foo.jpg the
>> actual path is
>>
>> /static/v1/img/foo.jpg
>>
>> If there's a new version of the resource with the same name, then all you
>> have to do is to replace v1 with v2, then v3, etc.
>>
>> If you upload the static files to the server, then I'll configure nginx to
>> serve them.
>
>
> More than a week has passed since my mail, so I decided to fetch the files
> myself. I extracted the names of the static files from the source code, and
> downloaded them to the server to the /var/www/www.squeak.org directory. I've
> configured nginx to serve these files as I described before. Please check if
> all of them are there.
>
> The next step is to change the source code in the image to use these files.
> I saw that the css and js files are not minified, so that's another thing to
> do. I also think that the source code of the web site should be versionned
> by MC, and probably stored on source.squeak.org to let others modify it.
>
> The image serving the www.squeak.org site is constantly using ~50% CPU for
> some reason (even when it's not serving any requests). It's also being ran
> by root, which is really bad from security POV. Please fix these.
>
>
> Levente
>
>>
>>
>> Levente
>>
>>>
>>>
>>> Chris
>>>
>>>
>>
>
I just completed a round of changes to squeak.org, which I'll upload tomorrow.
The homepage seems to be a Pandora's box I've opened. I see a collision about to happen where strong opinions meet in a space where there is no time. I want to say that there is time. The homepage went for a long time with no tending and now I feel people think they need to get their changes in exactly as they want them quick before it disappears again.
It's not about to disappear. And there is time. And your content will go on the site. And it will not be rendered exactly as you want it to be. I don't have a solution for inlining links at the moment. And I'm not sure I want one. I do have a strong distaste for links to Wikipedia. (Now that I think about it, there is a strong paradigm in people's mind that squeak.org should be a wiki. I don't see it that way.)
And please remember, I'm a volunteer. It's important to allow me to feel I own part of the process. I elect to own presentation and not content. Not entirely, but some. And there's value in this, because somebody needs to see the whole. People have been making comments that would warp the overall look of the site. And some comments show people haven't noticed their changes have already happened or if something they want already exits somewhere else on the site.
There's lots of time to figure these things out. A lot has improved in two weeks.
Thank You,
Chris
squeak.org issues:
image shouldn’t run as root
resource links are to chriscunnington.com
zip resources for faster download
- use minified versions of files
- get that 404 image (broken paper showing a code browser) out of my email Archive and install
- check multi platform layouts (i.e. cell phone, tablet)
---------- Forwarded message ----------
From: Marcel Taeumel <marcel.taeumel(a)student.hpi.uni-potsdam.de>
Date: Mon, Mar 24, 2014 at 11:43 PM
Subject: [squeak-dev] Re: The new site looks great! [EOM]
To: squeak-dev(a)lists.squeakfoundation.org
I think the colors are all messed up and the spacing needs to be fixed. The
forward/backward buttons besides the central screenshot have a strange
offset upwards. The screenshots are kind of confusing and do not actually
promote the features they aim to visualize.
How about applying some visual concepts that are well known from other
popular sites? Hmmm... what about Twitter's Bootstrap? Or, to get started,
we could use a harmonizing color scheme. -> http://colorschemedesigner.com/
Maybe we can promote our features in tiles like www.fogcreek.com does. Big,
sliding screenshots could be used for cool projects that actually use that
features. Maybe we can just get rid of that slideshow because the site
visitor has almost no control about it. And it does present those features
at a glance. I found this interesting to read:
http://www.nngroup.com/articles/auto-forwarding/
"Squeak is a modern, open source, full-featured implementation of the
powerful Smalltalk programming language and environment. Squeak is
highly-portable, running on almost any platform you could name and you can
really truly write once run anywhere. Squeak is the vehicle for a wide range
of projects from multimedia applications and educational platforms to
commercial web application development. Read on and join in!" --- What are
the definitions of "modern" and "powerful"? Do we need those adjectives?
Isn't it paradox to say "highly-portable" and "almost any platform" in one
sentence? How does "really truly" provide any argument to a site visitor?
What actually *is* the target group of this advertisement? ;)
Most importantly: The download link on the home page should be *above the
fold*
Just my two cents. :-)
Best,
Marcel
--
View this message in context:
http://forum.world.st/The-new-site-looks-great-EOM-tp4750425p4750585.html
Sent from the Squeak - Dev mailing list archive at Nabble.com.