Choose a URL encoding pattern

Considering utilizing crockford encoding, and allowing the url aliases to be generated sequentially. In order to prevent duplicates/conflicts, we would want to generate the url on node creation (or form save), meaning that we would not show any value in the form before the form is saved. With this pattern, there would be no accounting for the entity type.

Added encoding library to composer.json in commit 8a450415

Will close this issue, once I experiment a bit more with this library.

I chose this library over some of the others mentioned above because it is an implementation of the Crockford encoding pattern. In particular, I like that it prioritizes human readability, and mitigates occurrence of characters that can be confused with one another.

Automatically closed - issue fixed for 2 weeks with no activity.