Prepare (aka update) the site content for Heist 0.10

[adinapoli]

Hi guys,

maybe I'm not getting something crucial but as far as I can see, the Heist APIs changed a lot from 0.8 to 0.10. The most relevant example is that:

Text.Templating.Heist

Does not exists anymore. So far so good, being 0.8 the last stable release, but with the 0.10 release a lot of website documentation will become stale.
Take a look here:

http://snapframework.com/docs/tutorials/heist

At the bottom of the site you'll see the old API gets called.

I suggest we create another branch for this temporary transition, so we can update all the due documentation, preserving the stable one until 0.10 is released. Once 0.10 is out, simply merging from 0.10 to master will update the site with the correct APIs and infos. This applies also for snap,
because now wrapHandlers is gone. When snap 0.10 will be out, we need also to change every occurrence of wrapHandlers to wrapSite.

Obviously I can create this branch locally and then pull req everything when the time will come.

What do you reckon?

[mightybyte]

A new branch is perfect. Thanks for working on this.

[adinapoli]

It's a pleasure :)

[adinapoli]

Just to keep everyone posted, I've complete the migration toward heist 0.10, snap 0.10 and snap-core 0.9.2.1, including the addTemplatesAt we talked about. The site seems fully functional, including the blog. Now I'm switching my focus on update stable content (e.g. wrapHandlers must be gone, same applies for Text.Templating.Heist). I'll also write the migration rule to 0.10, so if you have any observation please let me know.

ps. It would be beneficial for me to post here mismatches I encounter updating the tutorial material. If you think is an appropriate place, please let me know.

[adinapoli]

A bump just to remember you that, although not explicitly pull-requested, I have the updated website in my repos, ready to be integrated/revised :)

[mightybyte]

Thanks. I'm not going to pull this until 0.10 is released to hackage.

[gregorycollins]

Pull it into a branch maybe?

[adinapoli]

Hi Greg,
I've pulled it inside my local branch, obviously, but I don't have the
permission to create branches of the snapframework/snap-website.
If you or Doug create a new branch, I can pull-req there.

Bear in mind that my changes affects snap-static also (and maybe another
package I can't remember now) so we have to create appropriate branches
accordingly.

Bye,
A.

On 16 October 2012 11:03, Gregory Collins notifications@github.com wrote:

Pull it into a branch maybe?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/23#issuecomment-9477624.

[gregorycollins]

That's what I meant, we should pull it into a branch on the main snap-website repo.

[mightybyte]

Ok, I pulled it in. I'll leave this issue open until we make the final switch.

[adinapoli]

Perfect, thanks guys :) 👍