Scaffolding with pictures texts or how not to throw time in the trash

Surely all the designers have already realized that “Lorem ipsum” is not suitable for creating layouts and therefore they try to design them immediately with real data. But it gets sideways to the designers and programmers, since they have to fill out templates and bases with close to real pictures and text, which will then be deleted after the site’s release into production. That is, the time spent on it is thrown into the garbage. But you can not throw it away.


To begin with, let's imagine the average website development process:
Designers sdizaynili → Maker-ups imprinted → Server programmers programmed and pulled patterns.

Everything is cool, but there are a few subtleties. Layout designers, while creating static templates, copy caps from a file to a file, manually select texts, create a bunch of items for lists, and so on. Long, tedious, not interesting. If something has to be changed - all templates and lists have to be redone.
')
In addition, at the stage of tightening the templates, it will always be found out that something is missing, some cases are not taken into account, and so on. Hence the alteration, loss of time and so on.

It is logical to swap server programming and templates:
Designers have designed → Server programmers have programmed everything according to the requirements → The layout has been designed.

Already better. But now the burden of creating test data lay down on the server programmers and the boredom has not gone away.

And what if each field is assigned its own pseudotype? For example, a picture, a long text with pictures, a title, a name, a login, and so on. Then immediately after creating the models, it will be possible to fill the entire database with one movement that looks like real data: there are a lot of texts and pictures on the Internet, and we can collect them at random not difficult.

First, it will save time for server programmers, since there will be no more need to create meaningless entries from the admin panel. If you use “Mexicans” for this, then they can be abandoned. Secondly, such an approach will save time for designers, as they will draw up ready-made data, and they don’t have to manually create a bunch of duplicate elements, and to change them if necessary, you only need to in one or two places. Thirdly, it will speed up debugging and testing, as the design and templates immediately come across data close to real, which will help to identify flaws in the design and layout.

Perhaps, such a thing is already there, but I still could not find it. I'm going to create a similar mechanism for Yii, but to make it ideologically correct, I will need help. So if this idea seems interesting to you and you are ready to participate in its implementation - let's try to do such a thing together, it should turn out cool.

_{PS Picture for the topic borrowed from the job site of the design bureau Artyom Gorbunov}