Part of the events dashboard I’m working on is the ticket creator. This allows the user to create tickets for their event, with relevant details, like the time for sale – the timeframe that users have to get a ticket, the quantity of tickets available, and some additional features the client requires that won’t be outlined here.
I utilized the Shoelace library for the UI, a clean and basic way of implementing nicely styled components into HTML. Specifically, Shoelace’s Drawer component, which, after a bit of custom JS embedding into Webflow, I could get working for my use case.
For the backend (or, in this case, more of the Wized control), I had the submit button tied to an object creation that would create a new ticket object in the event object and store the latest entry into the browser’s local storage. I then tied this in with the URL query parameters, as I demonstrated in the last post. With this, I could display the locally stored ticket if the URL event ID matched the record under which the tickets were stored.
While still a rough draft, it gets the concept across and keeps the event information stored locally without calling the backend. This will be changed in the later stages as I connect with the backend and allow for more form validation, to discourage invalid forms from being sent in.
Leave a Reply