phoenix-cms VS calendlex

I've been using Elixir and Phoenix for the last six years to build from APIs to complete web applications using React and Elm on the front-end, being Elm my weapon of choice primarily. Since LiveView came out, I have played around with it a couple of times, first to build an ant farm and second to set up a headless CMS. However, I never ended up getting hooked by it, and I kept relying on Elm to build my front-ends. But when Phoenix v1.6 and LiveView v0.17 came out, my feelings about LiveView changed utterly, and I couldn't resist making something more extensive to test out all its new features, making me finally understand all of its power.

well here is another one made with elixir https://github.com/bigardone/calendlex

After confirming the action, we see the corresponding success flash message, and the deleted event type is no longer in the list. And this is it for this part, and we have finally finished with all the logic behind managing event types. In the next part, we will focus on the last part of this series, which is listing and filtering scheduled events. In the meantime, you don't forget to check the final result in the live demo, or have a look at the source code.

It works like a charm, yay! In the next part, we will continue with event types management, implementing the corresponding live views to edit existing even types and create new ones, using more live components and hooks. In the meantime, you can check the final result in the live demo, or have a look at the source code.

To give the finishing touches to the layout and styling, copy the contents of the main CSS file and paste it into your local version, and replace the content of the root and live layouts with the following:

In the next part of the series, we will jump into the action by creating a new Phoenix project and generating the necessary Ecto schemas for modeling both event types and events. In the meantime, you can check the end result here, or have a look at the source code.