Arkansas Bride
About Arkansas Bride
Since 1990, Arkansas Bride has been the No. 1 resource for Natural State brides planning their big day. It's not only the biggest bridal magazine in the state, but it is also the best online tool for soon-to-be newlyweds in search of vendors and inspiration. The magazine is published twice a year, with Spring/Summer and Fall/Winter issues. The editorial content includes a guide to 700-plus Arkansas wedding professionals, inspiring Real Weddings, styled shoots, beautiful floral and fashion shoots, and so much more! And a special supplement – Hot Springs Wedding Planner – is included inside each issue too!
About The Project
Mission: Use a more modern mobile first design since most users are coming to the site via mobile device, and create a system for advertisers to update their listings.
Technologies Used: Laravel's Notification system, Tailwindcss
Links
Before: From the Web Archives
After: Visit new live website
Video Demo
Summary
This was the first industry project I did almost 100% solo. Before this project, our team used Bootstrap for the frontend design, but we wanted to try to Tailwindcss out because it is a utility first css framework.
Before this upgrade, the Arkansas Bride team would update the Vendor listings manually as request come to them via email or telephone call from a vendor. In this project, we built a system that let the vendors update their listings from the website. We did it by using Laravel's built in Authentication class, and created a new user model called a Vendor. This Vendor class used the Notifiable trait, which allows us to setup custom events that fire off certain Notifications to the Vendors email.
So in simple terms, a Vendor would request a login link that required no password. There was about 800 vendors in total and we wanted the process to be as simple as possible for them. So the login link didn't required a password. Instead it has special parameters that our server could read and each login link requested would expire after a certain amount of time. Once inside the admin, the vendor could update their listings data. On save, the listing would be copied as a "Revision", and members of the Arkansas Bride team would be Notified by Laravel's Notification system. The Bride team then reviews the revision for typos and can approve or reject the changes. If they approved the changes, the revision in the database would have all its data copied into the real listing, and then the revision would be deleted. Their live production data is fully updated, so we send the Vendor another notication letting them know that their Vendor Listing is updated live on the website and will be published in the print magazine. The same data from the website listings is used in the vendors listing in the magazine.
This was quite a challenge for me to get all these moving parts hooked up correctly, and lots of testing was needed to make sure the system would work at a production scale with 100s of folks updating their info automatically rather than over the phone. But we got it done! And the new Vendor Listing design looks much better I think! It was a super fun project.