-- T.J. :-)
To unsubscribe, reply using "remove me" as the subject.--
You received this message because you are subscribed to the Google Groups "Prototype: Core" group.
To post to this group, send email to prototy...@googlegroups.com
To unsubscribe from this group, send email to prototype-cor...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/prototype-core?hl=en
Wow! I didn't even realise they were updated until I read this message. Very nice work indeed!
Good work on the improved docs though.
*ONLY* if all of the old information has now been ported over. Looking
at the documentation Lighthouse project, it looks like all of the
old "merge/update" tickets have been closed (yay!), which may mean
exactly that, someone from the docs team can presumably confirm that.
Once we're ready, 301s that live in those locations for a long, long
time are indeed appropriate. Or if 301s are hard in Mephisto,
replacing each of the API documentation articles with a link to the
On Apr 5, 3:30 pm, Mislav Marohnić <mislav.maroh...@gmail.com> wrote:
We could get pdoc to generate it with a search field, etc.
We could also try JS redirection.
Anyone wants to give it a shot?
On Apr 6, 8:42 am, "T.J. Crowder" <t...@crowdersoftware.com> wrote:
> > My coworkers still find old docs (http://prototypejs.org/api) by googling. I
> > had to point them to new doc site. I think it's crucial to set up 301
> > redirects.
> *ONLY* if all of the old information has now been ported over. Looking
> at the documentation Lighthouse project, it looks like all of the
> old "merge/update" tickets have been closed (yay!), which may mean
> exactly that, someone from the docs team can presumably confirm that.
> Once we're ready, 301s that live in those locations for a long, long
> time are indeed appropriate. Or if 301s are hard in Mephisto,
> replacing each of the API documentation articles with a link to the
> new one.
We could also try JS redirection.
Otherwise, the documentation itself is phenomenal, and thanks to all!
Robert, that would be great. We unfortunately don't have this level of
access to the server.
I was suggesting crating a good 404 page. Not modifying the http
> Not saying I don't believe you, I'm just surprised that a project as mature
> as prototype is hosted in an environment that doesn't support basic
> .htaccess-style configuration.
There's historical reasons to this. We're in the process of migrating,
though (not that this will change much in terms of low-level access).
Oh well, it's hardly the end of the world. :)
On Apr 6, 8:31 am, Mislav Marohnić <mislav.maroh...@gmail.com> wrote:
> The scroll bar is native to the browser, meaning it's the same as in a
> regular window, iframe or frameset. The navigation panel should scroll with
Yes, but we're moving away from it.
you're moving from Mephisto to something else that *also* supports
A script included on each old API page that reads the current location
and figures out the new URL and inserts a prominent "This info is old,
go look here instead" box at the top (worded perhaps *slightly* more
carefully) sounds like a half-day project to do right. (It sounds like
an hour-long project, but you know it gets more complex and you get
into ito.) I have a half-day I can give it at the end of the month,
but not sooner, if that would be useful.
We're moving to github pages as it makes contributing to the website
the same process as contributing code or documentation.
I've started the project already: porting the whole blog archives to
jekyllrb and disqus comments (preserving all past comments in the
Your help is as usual, most welcomed, especially since I'm hoping to
merge parts/whole of your unofficial wiki content into it in the long
run (and if it's ok with you, of course).
> Your help is as usual, most welcomed, especially since I'm hoping to
> merge parts/whole of your unofficial wiki content into it in the long
> run (and if it's ok with you, of course).
It's funny you should mention that. I'm under the gun for the next few
days, but one of the tasks on my "to do" list for later this month is
to ping the user list to see if anyone actually wants the wiki, since
I noticed a few weeks back that in the last *year*, there had been
precisely one update to the wiki by someone other than me. :-) (Doug
Reeder added an on0 handler to the bulletproof ajax page.)
Enh, it's not going to take long, I'll go do that now.
I don't know if you're familiar with jekyll, but his sports built-
in templating and markdown/textile parsers.
We'll be using prototypejs.org directly. It's supported by Github.
Are you suggesting we move the new documentation elsewhere
(prototypejs.org/doc) for example and keep the old, 1.5 doc structure
on prototypejs.org/api but replace the content with a link to the new
documentation or maybe an HTML refresh?
Isn't that just a glorified 404?