Yes, I've read that, but it seems to be targeted to distro-dependent appimages. Instead, I wish some procedure that would allow me to create a single appimage for most distributions.
For example, if you go to the Blender download page, you'll see they're offering just one Linux binary (well, actually two: one for 32 and another for 64 bit) with a quick note that says "Requires glibc 2.11. Suits most recent GNU/Linux distributions"
A note as simple as that would be my wish for distributing appimages.
So, my question is, what procedure could I follow to build binaries so that my appimages can be easily distributed to "most distributions", just like Blender (and other packages) do.
EDIT: I thought the link you gave me was another page I visited yesterday that shows examples of creating an AppImage for common applications, but that didn't explain the problem of supporting multiple distributions. However, the link in your message does give hints at how to achieve multi-distribution binaries. Perhaps not a failsafe procedure, but following such hints and testing with some virtual machines of a few Linux distributions, I think it can be achieved.