One aspect where HER could make steps to reach out to other communities in the Central District and Rainier Valley is to make the web site available in languages than English. My suggestions would be for Spanish and Amheric, but that may be a decision which should be made in consultation with Seed/Rainier Valley Radio folks and/or the LPFM committee.
On a technical level a good portion of the static text (the Home page, About, FAQ, etc) in the website should be pretty straightforward to localize with Rails by making use of yml files (like config/locales/en.yml) to store string data, and then modifying the views to pull strings from these files depending on the local that the user has selected. Here is a link to a guide about the process: http://guides.rubyonrails.org/i18n.html
Localizing the dynamic part of the web site, such as the program names and descriptions looks more difficult, since it involves pulling info from the database. This could be a secondary goal. Perhaps Globalize would help? http://guides.rubyonrails.org/i18n.html
The other part of this project is finding volunteers to translate from English to other languages. This might be an opportunity to help establish ties with the Rainier Valley radio group or other community organizations. If this is a project we want to take on, moving the English text to a en.yml file would be the first step, and would be helpful for providing translators with text in one place.
One aspect where HER could make steps to reach out to other communities in the Central District and Rainier Valley is to make the web site available in languages than English. My suggestions would be for Spanish and Amheric, but that may be a decision which should be made in consultation with Seed/Rainier Valley Radio folks and/or the LPFM committee.
On a technical level a good portion of the static text (the Home page, About, FAQ, etc) in the website should be pretty straightforward to localize with Rails by making use of yml files (like config/locales/en.yml) to store string data, and then modifying the views to pull strings from these files depending on the local that the user has selected. Here is a link to a guide about the process: http://guides.rubyonrails.org/i18n.html
Localizing the dynamic part of the web site, such as the program names and descriptions looks more difficult, since it involves pulling info from the database. This could be a secondary goal. Perhaps Globalize would help? http://guides.rubyonrails.org/i18n.html
The other part of this project is finding volunteers to translate from English to other languages. This might be an opportunity to help establish ties with the Rainier Valley radio group or other community organizations. If this is a project we want to take on, moving the English text to a en.yml file would be the first step, and would be helpful for providing translators with text in one place.