# \[Tutorials\] Web Development with Haxe

**URL:** <https://community.haxe.org/t/tutorials-web-development-with-haxe/1920>\
**Category:** Showcase\
**Created:** [July 20, 2019, 9:07pm UTC](https://community.haxe.org/t/tutorials-web-development-with-haxe/1920 "2019-07-20T21:07:46Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![tienery](https://community.haxe.org/user_avatar/community.haxe.org/tienery/32/964_2.png) [@tienery](https://community.haxe.org/u/tienery)\
**Post date:** [July 20, 2019, 9:07pm UTC](https://community.haxe.org/t/tutorials-web-development-with-haxe/1920/1 "2019-07-20T21:07:46Z")

</div>

Hello everyone!

I have begun a web development tutorial series going through the entire process of building a website using multiple approaches. I will, at first, use the AJAX approach with a hash-based router, then move into a server-based router approach using the PHP target, then finally I will be introducing my library and start using that to build the website and go from there.

You can begin the tutorial series [here](https://www.youtube.com/watch?v=yRe_7CDmros) which is the Getting Started video with Haxe, otherwise you can go to the playlist and start [right from the beginning](https://www.youtube.com/watch?v=-ngM9ONozRs&list=PL4bwI9jGGo1merqooewvCF_HHbcXKzBli) which goes through the design of the website.

Let me know of any improvements or feedback you might have either here or on the videos themselves.

---

<div class="post-metadata">

**Author:** ![filt3rek](https://community.haxe.org/user_avatar/community.haxe.org/filt3rek/32/2613_2.png) [@filt3rek](https://community.haxe.org/u/filt3rek)\
**Post date:** [July 22, 2019, 10:47am UTC](https://community.haxe.org/t/tutorials-web-development-with-haxe/1920/2 "2019-07-22T10:47:25Z")

</div>

Hi Luke,

Good initiative ! I’ve done something like that in the past to help people working with server/client side using only the Haxe toolkit [https://www.mromecki.fr/blog/post/haxite-writing-entire-website-using-haxe](https://www.mromecki.fr/blog/post/haxite-writing-entire-website-using-haxe)  
Good luck, I’ll follow that !

---

<div class="post-metadata">

**Author:** ![Confidant](https://community.haxe.org/user_avatar/community.haxe.org/confidant/32/63_2.png) [@Confidant](https://community.haxe.org/u/Confidant)\
**Post date:** [July 22, 2019, 4:01pm UTC](https://community.haxe.org/t/tutorials-web-development-with-haxe/1920/3 "2019-07-22T16:01:02Z")

</div>

Go get’em Luke!

---

<div class="post-metadata">

**Author:** ![teotigraphix](https://community.haxe.org/user_avatar/community.haxe.org/teotigraphix/32/916_2.png) [@teotigraphix](https://community.haxe.org/u/teotigraphix)\
**Post date:** [July 25, 2019, 2:18pm UTC](https://community.haxe.org/t/tutorials-web-development-with-haxe/1920/4 "2019-07-25T14:18:33Z")

</div>

Thank you for doing this, more videos about the Haxe ecosystem in the current day is great.

---

<div class="post-metadata">

**Author:** ![sundialservices](https://avatars.discourse-cdn.com/v2/letter/s/9e8a1a/32.png) [@sundialservices](https://community.haxe.org/u/sundialservices)\
**Post date:** [July 26, 2019, 1:44pm UTC](https://community.haxe.org/t/tutorials-web-development-with-haxe/1920/5 "2019-07-26T13:44:13Z")

</div>

I now use Haxe as my much-preferred way to write JavaScript, simply because of its concept of “at compile time.” Gone are the days of searching for stupid errors using a browser debugger.

---

<div class="post-metadata">

**Author:** ![tienery](https://community.haxe.org/user_avatar/community.haxe.org/tienery/32/964_2.png) [@tienery](https://community.haxe.org/u/tienery)\
**Post date:** [July 26, 2019, 6:38pm UTC](https://community.haxe.org/t/tutorials-web-development-with-haxe/1920/6 "2019-07-26T18:38:13Z")

</div>

Well, sometimes you still have to debug with Chrome if you make a stupid Haxe code mistake, such as incorrect logic, but type checking and null references can certainly be minimised with a compiler. In addition, you could debug PHP a lot easier with macro-generated errors. Perhaps I will do some future videos on debugging server-side code using macros.