We are embarking on a major drive to increase website conversions on our Booking Site. Driving traffic to the site is not especially difficult but, once there, the traffic doesn't convert very well.
If we are to start carrying out A-B testing of incremental improvements, we need to be able to adapt the look, feel and functionality of the site quickly and relatively easily. The site is written entirely in Perl (of course) with MariaDB database. But the Perl scripts do not use any kind of templating. Instead they have the HTML, CSS, JavaScript, etc hard coded along with the functional logic.
There are two require files, one provides common code to connect to the database, set the environment etc along with common subroutines. The other provides subroutines to output standard parts of webpages like the header, navigation, footer, etc.
As we are looking to make changes to drive Conversion Rate Optimisation (CRO) it seems sensible to refactor the website to implement Template. But - I have no idea where to start!
What suggestions can you give to start to plan a project to refactor the website to use templating?
What are the hidden pitfalls that could trip me up and suck up vast amounts of time?
In reply to Refactoring webcode to use templates by Bod
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |