armoria-api VS whatsapp-api-nodejs

Too complex? I read the documentation https://github.com/Azgaar/armoria-api#readme didn't find anything along the lines of what I'm talking about. My hope was, to have ten or eleven cities in a Theocracy which all used the identical symbol of the religion, that same image (a heraldry "charge") but with different color-schemes; and then later when the Theocracy falls they all abandon the image but keep the rest of their arms. The city that had the hammer-and-anvil (theocratic symbol) over a field of gold, now has a horse on a field of gold; the city with the hammer-and-anvil over three ships, now has a horse over three ships; etc.. To do this, I'd have to (1) create all the originals with hammers-and-anvils; then later (2) edit out the hammer-and-anvil part. But if the created item (1) is just an SVG or a JPG or a PNG, then it's more reasonable to edit by starting from scratch, than to edit FROM the item (1) to get item (2). When a third change comes along to the cities in the region (conquered by invading empire) they all want to keep their old coats-of-arms but add a white bull (symbol of imperial participation) in the upper left. Start again from scratch?

See documentation for the details. In can be pretty hard to use, so please read carefully.

One thing that I really want you to try is Armoria API - it can be used to embed heraldry generation into your project.

Thanks, xlink is indeed easy to solve, but there are other issues, esp. the one with positioning. I have already solved it for Armoria-api and can do the same for GUI version, but it will require major change.

I have significantly reworked Armoria API and in parallel added 13 new patterns to use. These are mainly historical ones, but also a few custom ones not widely used.

We are going to use whatsapp-api-nodejs that converts users WhatsApp account into an API.

link to git