{"id":3995,"date":"2023-11-13T09:03:58","date_gmt":"2023-11-13T08:03:58","guid":{"rendered":"https:\/\/www.lepatron.email\/?p=3995"},"modified":"2023-11-20T09:30:10","modified_gmt":"2023-11-20T08:30:10","slug":"enregistrement-blocs-personnalises-email-builder","status":"publish","type":"post","link":"https:\/\/www.lepatron.email\/en\/save-custom-blocks-email-builder\/","title":{"rendered":"Custom block saving finally available in your email builder"},"content":{"rendered":"

Among the missing features of the Open Source LePatron email builder<\/a>, there was one that was sorely lacking. One that you regularly asked us for. One that could save you an incredible amount of time when creating your emails. In short, one you're going to love: custom block saving<\/strong>.<\/p>\n\n\n\n

Also known as custom blocks<\/em> or customized blocks<\/em>. This sweet dream is now a reality. It gives us great pleasure and emotion to announce this new version of the LePatron email builder. Yalaaa!<\/p>\n\n\n\n

Create and save your customized blocks<\/h2>\n\n\n\n

Take an existing block from your template. Add content: text, images, links<\/em>. Modifying styles : colors, sizes, position, margins, typography, buttons<\/em>...<\/p>\n\n\n\n

Save it. It will be saved in a dedicated library. You can then use it in all your other creations.<\/p>\n\n\n

\n
\"\"<\/figure>\n<\/div>\n\n\n

Your library of personalized blocks<\/h2>\n\n\n\n

Depending on the number of users and\/or the number of blocks available in your template, you're likely to have a rich library of saved blocks<\/a>.<\/p>\n\n\n\n

It was therefore essential to link the recording of saved blocks to a dedicated library so that you could find them easily.<\/p>\n\n\n\n

You can search for three essential elements:<\/p>\n\n\n\n

    \n
  1. the block name<\/strong><\/li>\n\n\n\n
  2. the block description<\/strong><\/li>\n\n\n\n
  3. the author's name<\/strong> block<\/li>\n<\/ol>\n\n\n\n

    <\/p>\n\n\n\n

    \"custom<\/figure>\n\n\n\n

    You'll need to get organized as a team. All the more so if your teams are numerous and changeable. For example: set up naming conventions for block names, systematically insert a date, use words like \"latest version\". In short, jointly find a way of naming your blocks so that all users can find their way around.<\/p>\n\n\n\n

    Example:<\/em><\/p>\n\n\n\n