rase-rocks / byw Goto Github PK

On iOS Safari (in dark mode) the primary text colour of the input fields of the submit form is black, against a dark background. The placeholder text colour is fine.

Stylesheet needs alteration to account for this.

Do we allow places of interest to be added to our index that are not within the bounds of Wales? A pro for this would be it would limit the usefulness of any old shop adding themselves for some free visibility, but it would also prevent locations in other countries from signing up. It could be quite good to see places around the world that support the language.

Taking a cue from the existing byw website the home page should likely be based around a map. I would lean towards using Mapbox to style OpenStreetMap data. Some sort of search function would then be required, likely the search will identify the type of search, coordinates, postcode, address, what3words etc.

All modern browsers now support the img srcset attribute to allow the browser to decide which image size is best under current conditions.

Home page load time would benefit from replacing the existing image loading and fading in system to one based on srcset, which would allow the processing of the downloaded image to be taken out of the JS event loop. A win for smaller download sizes on mobile or other small screen devices and also a win in reduced first render time.

This issue has been raised following a conversation with gisella-albertini on https://forum.saysomethingin.com/t/idea-for-a-new-website-breatheyourwelsh/11662/39

The infrastructure for non-english speakers should be implemented as a priority. The translations themselves can be added at a later date.

This point surrounds the issue of submitting a premise for inclusion in the data set. Should shops / businesses etc add themselves, should this be crowd sourced or should this data be collected by the maintainers?

Allow users to upload photos of the premises / location. Use an ML model to filter out unwanted images before they are uploaded

Hello.
I have recently visited the byw.cymru website and noticed that there is an option to view it in Spanish. I can speak fluent Spanish and would like to help improve the Spanish version of the website, although I don't have enough coding experience to manually edit websites, I would be happy to translate the text of the English website into Spanish.

I would make the assumption that the data set is viewable by anybody and so does not require any kind of account or authorisation to use. But it may prove useful, for security and moderation, to have user accounts for those who upload / moderate uploads. If so what is the minimum we need to make this happen.

In order to allow the maximum number of people to be able to look at and comment on the development of the main site, a staging area is needed.

Vulnerability found with Lodash.

Only loads/sample is used client side. Currently this has been upgraded to 4.17.13. Future work will remove this dependency altogether.

This issue will be closed when that happens.

It is now time for another language version to be added. This time it is the turn of Spanish. This issue will create a basic translation, powered by Google translate as I cannot speak the language. However is should be close enough to allow a fluent speaker to easily correct my mistakes without having to go through the entire translation creation process.

For the purpose of this discussion, lets assume that we have a working API that provides location data for premises where a person is likely to be able to speak Welsh. If we then combine that with the array of sensors fitted to a smartphone, at this stage an iOS device, how can be best improve the experience for a user of the system

The reason for this project is to allow a visitor or other interested person to view places of interest around Wales where they are likely to hear the Welsh language being spoken. But what sort of information should be recorded about the place? An obvious starting point would be its coordinates. At this point I would suggest that a polygon be used rather than a point, but that may be open to discussion.

Any thoughts would be appreciated.

How do we best educate our users that they may have to take extra steps in order to ensure security, even if other websites they regularly visit do not. For example it would be my preference to have a password-less login flow. Probably with some kind of one time token followed up with multi factor auth. Is there a counter argument to this? Afterall if a user account is only required to upload information, and that role is restricted to a handful of users then it would be reasonably straight forward to have those users take extra steps.

The current privacy policy was copied over from breathyourwelsh.cymru (the original idea for the site). It needs updating to show the current information and reflect updated private nature of byw.cymru