Today, I did something I’m proud of (it always happens when you dabble a bit in something that’s not quite your field, and it works out).
In my project, there are currently about a thousand content pages, hundreds of functional components, many of which are used on many pages, with either unique or common configurations. The client updates both the components’ configurations and their composition on the pages, and as often happens with such volumes, fixing something in one place breaks something in another. And the task is to keep all this under control.
What I did: On my server, a graphic snapshot is created for all pages of the site – a set of images with a complete copy of the page at the moment the snapshot is taken. Each picture is stored in folders corresponding to the language, country, site, and hierarchical categories. All are available on the web. Graphic copies of individual page components are stored in a similar manner. Every day. There is a mechanism to visualize changes. Of course, when changes appear where they were not expected, it is both good and bad. Bad, because it means someone did something wrong, and good because it was detected early.
I can’t show anything; it’s a commercial project.
Technologies: python, selenium, chromedriver, imagemagick.
Hi, I'm Rauf Aliev. 