Designing and optimising new invoice PDFs
The Open Event project has proven to be an excellent event management application with a growing user base. With recent workflow refactors in the order process in open-event-frontend and introduction of event invoices (to be rolled out this month as a work product), the open-event-server’s invoices required a makeover. A ticket buyer is now required to give their billing information if the order is comprised of paid tickets and to accommodate this, and long information addresses, optimisation was required. Restructuring order invoices The new order invoices use nested tables concept instead of previously used two-cell tables. The pros of this new design is the accomodation of long-addresses and corresponding changes in billing information display. {% if order.is_billing_enabled %} <td style="text-align:center;"> <table> <tr> <td> <strong>Company :</strong> </td> <td> <strong>{{ order.company }}</strong> </td> </tr> <tr> <td valign="top"> <strong>Tax Info :</strong> </td> <td> <strong>{{ order.tax_business_info }}</strong> </td> </tr> <tr> <td valign="top"> <strong>Address :</strong> …