"Import" Language key/value pairs into Templates about aardwolf HOT 2 CLOSED

Here are my notes, combined with the wisdom of @asonix

Goal:
-- Add a configuration parameter to the Aardwolf.config so that the admin can set a -default- language
-- The User-preferences template will ALSO need to be able to access set languages from a fixed list (UI dropdown)

Question:
Are there any other scenarios where the language files will need to be accessed?

Functional specifications:

• If user exists, use their language
• If user doesn't exist, use default language
• By default the crate will expect a /lang folder to be in the application root
• Add a parameter to the aardwolf.config to allow the language folder path to be modifiable
• The crate should define an enum which represents every valid language
  • This allows lookups can say "You have a valid language, here's your language data" or "You're language is not supported"

Optional:

• Build a function to read through the languages folder in order to determine which languages have been implemented. It will then build a 'state' that can be queried for language data so even if the crate thinks a language is valid, it still relies on what exists to accept or deny requests

from aardwolf.

This issue is superseded by the i18n-templates branch

from aardwolf.