I don't know what's in the admin backend but the only non-static things I
see on the current homepage are stats and search, both of which could be
handed off to Google. I imagine duplicating the current site would require
zero or close to zero PHP programming, you'd "just" import the articles
into a cms.

If the web team thinks it's fun to build the technology as well as the
content then fine. I'd rather not reinvent the wheel for the Xth time and
spend that time elsewhere, but then again I'm not the web team. Carry on.

rado

On Sat, Mar 9, 2013 at 1:50 AM, Colin Putney <colin at wiresong.com> wrote:

>
>
>
> On Fri, Mar 8, 2013 at 4:22 PM, radoslav hodnicak <rh at 4096.sk> wrote:
>
>> I know it's a question of pride to have the homepage of a programming
>> language done in said language but these cycles of "rewrite in technology
>> X/abandonment/how do we update the site again?" are pretty silly. Is the
>> anything on the website that's actually benefiting from having a smalltalk
>> implementation? Why not just slap a wordpress or any of the zillion
>> externally maintained cms systems on the server and be done with it? It
>> should be the content that counts.
>
>
> So you're saying that instead of rewriting it in Smalltalk, we should
> rewrite it in PHP?
>
> Bear in mind that it isn't just a bunch of static pages—it's not hugely
> sophisticated, but it's not trivial either. No matter what we do, it'll
> take some time and effort to update and maintain. Personally I'd rather do
> that work in a language  that doesn't make my eyes bleed. Perhaps the web
> team feels the same.
>
> Colin
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20130309/8bac15ac/attachment.htm