Improve the usefulness of input labels and placeholders

[jtomeck]

As per the discussion in #106, the labels and placeholders seem to always say the same exact thing. Labels should tell the user what is needed (e.g. Email Address, Password, Name, etc.), while placeholders should give a useful template of information to be entered into the field (e.g. "email@provider.com").

[brianhelba]

@jtomeck My current understanding is that this will need upstream changes to Django-Allauth.

A given field "element" is generic. It has no control over where it gets injected and only has access to the attrs that it's given. I suppose that we could hardcode a bunch of special case logic into field.html like:

if attrs.label == "Email address":
   attrs.placeholder = "abc@example.com"
...

However, we'd have to inventory every single field label / placeholder combination that we care about, hardcode them into this library, and maintain it if upstream Django-Allauth ever changes their exact wording. Further, if upstream ever actually adds more relevant placeholder values, our values would actually mask theirs, so we'd then need to back out our changes (and set a dependency lower bound on whatever upstream release has the new values).

Also, note that Django-Allauth provides translations into a bunch of different languages. If we hardcode values for placeholders, we ought to verify that anyone who does apply a non-English localization doesn't have their usage outright broken.

Overall, I'm concerned about the lack of sustainability and additional maintenance burden of adopting this additional scope. Further, upstream Django-Allauth is actually very actively maintained, so I think we'd have a relatively easy time (compared to many other open-source libraries).

[brianhelba]

My current feeling is that we should close this as WONTFIX, but also pursue upstream changes, but I want to make sure that we're at least in agreement on what the necessary technical changes would be.