On Tue, Mar 6, 2012 at 9:41 PM, Peter Bittner <[email protected]> wrote:
> Some feedback on the redirects (and old documents) now in place on pyjs.org:
>
> 2012/3/2 lkcl luke <[email protected]>:
>>  mrhrrhmmm.. i just started reviewing the site - getting_started.html
>> is actually referenced by the #getting help tab; that refers to a wiki
>> page as well; the wiki page refers to the controls_tutorial.html and
>> others.
>
> I've added the usual 'Go Home' link Pyjamas logo to those files, but
> the old version is still online. Can you do a git pull and a full
> sync/upload? (All "old" HTML files, including Will and Abe.)
>
> Also, the pyjs_site source code available for browsing on the website
> is outdated.

 err... it can't be.

Makefile
----------

upload:
    cp -aux pyjs_site/output/* .
    rsync --exclude=pygit --exclude=examples --exclude=api --exclude=wiki \
          --delete -rlvz * pyjs.org:/var/www/pyjs.org/htdocs/

so i believe you may be hitting browser cache.


> (There is a link in the website's footer that leads to
> http://pyjs.local/pyjs_site/). That needs an update. It may be also
> helpful to make this subtree browsable in an "FTP-like fashion"
> (exclude the index.html from being loaded as the DirectoryIndex file
> there) otherwise nobody can go into
> http://pyjs.local/pyjs_site/public/ and
> http://pyjs.local/pyjs_site/output/ and explore their content.

 explore their content?  explore their "contentment"?  :)

> Something like the following should do the trick in the Apache2 Vhost
> configuration:
>
>        <Directory "/path/to/docroot/pyjs_site">
>                DirectoryIndex  None
>        </Directory>

 got it.

>> i've redirected the FAQ to http://pyjs.org/#FAQ and likewise the
>> uiHierarchy.html page to #Overview, so those can go.
>
> The redirect to #FAQ is fine.

 ack.

> On the other hand all references to uiHierarchy.html from inside the
> website don't work so well: Redirect Permanents cause the the whole
> site to load afresh

 bugger.  oh well.

> due to it's JS-nature.

 due to it is JS nature.  tsk tsk.


> Then a question: does the
> uiHierarchy really match the content in #Overview? (The uiHierarchy
> image may be outdated - just guessing actually, I don't know, really
> -, but it gives a different kind of overview: the class hierarchy, as
> opposed to the inner workings of Pyjamas on #Overview.)
>
> I'll kill FAQ.html and faqsplit.py from the repo. Sorry for that (for
> hurting their creator's feelings!), but I fear we won't need those
> files never again, will we?

 i kinda kept the FAQ around for non-JS browsers (and search engines)
but hey, what the heck.

>> the others have to stay where they are, not too keen on moving will
>> and abe to "articles", i'd like to think about that one some more and
>> am open to suggestions.
>
> In any case, the old files should go away sooner or later, because
> they don't belong to (and fit into) the new website application from
> June 2010. Their content should be integrated somehow, or - as I
> suggested earlier - moved out to e.g. /articles/ (then an Apache
> RedirectPermanent from the original location can lead there).

 *grumble*... naah.

 ok, i know.  a popup with a sub-history tag name.  #about.will_n_abe
should fire the popup.  and also change the tab to #about of course.


> Glad when that's all done. I'd like to start focussing on pygit... :-)

 yippeee!

Reply via email to