4 ms·

One of the developers of the new site here. Simon Krajewski did an amazing job writing the manual - it's a great resource and has all the gory technical detail

by joneil 12y ago

One of the developers of the new site here. Simon Krajewski did an amazing job writing the manual - it's a great resource and has all the gory technical detail - I'd encourage you to take a look. A number of other people have contributed to content and design (though we'd still like to give the design some more love). The website itself is developed in Haxe, and all of the content is hosted on Github so we can encourage contribution but still keep an eye on the quality, unlike the wiki we had previously. There's a "Contribute" link at the bottom of each page that links you to the relevant file on Github. If you have any questions let me know, I'm happy to answer. I hope you find it a valuable resource.

phest 12y ago
Could you describe your web stack / how you used Haxe to develop the website, in a nutshell? (heads up, these are returning 404s: http://haxe.org/support.html http://haxe.org/support.html http://haxe.org/donate.html http://haxe.org/donate.html)
- joneil 12y ago
  Thanks for pointing that out - where were those links from? The new URLs should be: http://haxe.org/community/community-support.html http://haxe.org/community/community-support.html http://haxe.org/foundation/support-plans.html http://haxe.org/foundation/support-plans.html http://haxe.org/foundation/donate.html http://haxe.org/foundation/donate.html I'll have to dig around and find out where the broken links are coming from. They were not part of the old site, nor the new site, but were in the private development repo for a while. Probably my fault they're still around. Thanks!
- joneil 12y ago
  I don't seem to have the ability to edit, and I forgot to reply to the first part of your comment. I use Apache/mod_neko on the server, though after the high traffic last night we might switch to nginx/mod_tora. Either way, these basically server ".n" Neko Bytecode files, and provide caching between requests [1]. I stayed away from using a database / ORM for this website, instead using Github for all the content. When we update we pull a repo and it references flat files. The site then transforms the HTML or Markdown, pops it in a template, and serves it up. I used a library called ufront for the MVC environment on the server. You can have a look at what a controller looks like here [2]. I'm hoping to do a tutorial, ufront was written by Franco Ponitcelli and Andreas Sudderland a few years back, but I've done a lot with it in the last year and hope to release / document soon. I did do a talk at last year's conference if you're interested [3]. 1: http://jasono.co/2013/09/11/neko-web-cachemodule/ http://jasono.co/2013/09/11/neko-web-cachemodule/ 2: https://github.com/HaxeFoundation/haxe.org/blob/master/src/app/controller/DownloadController.hx https://github.com/HaxeFoundation/haxe.org/blob/master/src/a... 3: http://www.youtube.com/watch?v=c6EwJ7iU-qo http://www.youtube.com/watch?v=c6EwJ7iU-qo

by joneil 12y ago

phest 12y ago

Could you describe your web stack / how you used Haxe to develop the website, in a nutshell? (heads up, these are returning 404s: http://haxe.org/support.html http://haxe.org/support.html http://haxe.org/donate.html http://haxe.org/donate.html)

joneil 12y ago
Thanks for pointing that out - where were those links from? The new URLs should be: http://haxe.org/community/community-support.html http://haxe.org/community/community-support.html http://haxe.org/foundation/support-plans.html http://haxe.org/foundation/support-plans.html http://haxe.org/foundation/donate.html http://haxe.org/foundation/donate.html I'll have to dig around and find out where the broken links are coming from. They were not part of the old site, nor the new site, but were in the private development repo for a while. Probably my fault they're still around. Thanks!
joneil 12y ago
I don't seem to have the ability to edit, and I forgot to reply to the first part of your comment. I use Apache/mod_neko on the server, though after the high traffic last night we might switch to nginx/mod_tora. Either way, these basically server ".n" Neko Bytecode files, and provide caching between requests [1]. I stayed away from using a database / ORM for this website, instead using Github for all the content. When we update we pull a repo and it references flat files. The site then transforms the HTML or Markdown, pops it in a template, and serves it up. I used a library called ufront for the MVC environment on the server. You can have a look at what a controller looks like here [2]. I'm hoping to do a tutorial, ufront was written by Franco Ponitcelli and Andreas Sudderland a few years back, but I've done a lot with it in the last year and hope to release / document soon. I did do a talk at last year's conference if you're interested [3]. 1: http://jasono.co/2013/09/11/neko-web-cachemodule/ http://jasono.co/2013/09/11/neko-web-cachemodule/ 2: https://github.com/HaxeFoundation/haxe.org/blob/master/src/app/controller/DownloadController.hx https://github.com/HaxeFoundation/haxe.org/blob/master/src/a... 3: http://www.youtube.com/watch?v=c6EwJ7iU-qo http://www.youtube.com/watch?v=c6EwJ7iU-qo