Dear All,
I have translated the MapSwipe website into Hungarian. You can deploy it.
Thanks in advance

Gábor

on the project.html page we currently load the geometry for all projects:
https://github.com/mapswipe/website/blob/f3c061b0d32a774847188c214fc094fc850fd859/assets/js/projectStats.js#L8

However, we only need to display the geometry of the selected project. This is now provided by our api:
https://apps.mapswipe.org/api/project_geometries/

(and it seems that project.html is not currently part of your gulp website compile thing...)

on the data page the map should display the points in the correct color.

too many projects are marked as "inactive".

Is it possible to download somehow the original AoI of a task again? I was looking at this task: https://mapswipe.org/project.html?projectId=-M6VE1Zwm2yQ_NPKb3HL I think it is just the admin boundary in this case. But it would be easy to download the original AoI somewhere so I can get in my Qgis an overview of what area has been swiped exactly.

Simple answer: yes it is and the link is: https://apps.mapswipe.org/api/project_geometries/project_geom_-M6VE1Zwm2yQ_NPKb3HL.geojson

We should add this link to the website directly.

Make the overview stats on the homepage H2 update automatically, similar to the data page.

Change gulp to copy CNAME to docs folder. Link of how to do.

Possibly:
let copiedFiles = gulp.src(['CNAME']) .pipe(gulp.dest('docs/'));

and then add copiedFiles to the merge line at the end.

Maybe also delete CNAME from the top level folder? Only needed in docs?

Need to improve the information and workflow for requesting a new project to be mapped. When done, we can change the call to action on the get involved page from the email link to better resources and request method.

Since the redeployment to the new repo, the pop-up no longer works on the map on https://mapswipe.org/data.html

This is supposed to be a link to the project details page for the project that is clicked on.

There is a new api endpoint providing user stats per project. This would be a nice information to be displayed on the project page.

https://apps.mapswipe.org/api/users/

E.g. the top then users for that project.

and add a link to download the data as csv.

Currently the canonical tags all point to the homepage. Either remove or change each page to point at that page.

If a project description uses markdown to be nicely style in the app, it renders as a confusing string on the website.
Example: https://mapswipe.org/en/project.html?projectId=-Lwdhk8Ui3s2ah7IGBJi

Can we dynamically draw in key information from the current projects active in the app, such as title, image, % complete?

To be added to home page? Or new impact page? Or data page?

Delete folders no longer needed:

• Double check .idea folder can now be deleted
• There is a 'to be deleted' folder with some old css and js

once implement in the back end (mapswipe/python-mapswipe-workers#247), we should set up the link to download data ready to use in the HOT Tasking Manager on the project page.

We get lots of emails for feature requests, often for issues already on the backlog.

On the 'Get involved' page, add a section for requesting features or reporting bugs. Have a more prominent link to GitHub (maybe straight to issues page) - so users can see the backlog and add to it. Email address can still be a backup for those not comfortable with GitHub.

Social preview still uses old website banner (and maybe description). Change to bring in line with the updated designs.

Tools around mapswipe can be found at:
https://wiki.openstreetmap.org/wiki/MapSwipe

Update the readme from this repo to:

• add a description of MapSwipe and explain what this project is about
• invite contributors to fill in issues for the app for bugs and requests for improvements

Move the gulp build to Actions on GitHub. Should simplify the workflow and make it easier for on-the-fly minor changes.

Maybe clean up gulp tasks and package.json. Pretty sure it's bloated and we really don't need everything.

@jhenshall Here are a couple of ideas we could use for things like the legend on the map:

• Create one version of the script per language, the same way we do for the page content. Pros: structure of the build code is ready, just add more pages. Cons: this prevents user browsers from caching the files and we end up with N copies of almost the same file, which is a bit of a waste. Also, the i18n code probably relies on html tags to work, so it may not actually work in the js content.
• Have the code load the translated strings from a specific translations file. Efficient, but you need to figure out the deployment logic to generate that translation file, and ideally limit it to the useful content, to avoid having everything loaded twice in the browser.
• Hard code the strings in a hidden part of the page during the gulp build and then have the dynamic code pull it at run time (with something like a jquery selector). My guess is that this is the easiest, you just add a hidden div at the bottom of the relevant page(s) with an html tag for each string to translate like the rest of the code (so no new deployment logic to invent), then just change the js code above to pull the relevant string from the hidden part of the page.

More than 30,000 volunteers engaged.
With over 1,000,000 sq km swiped.
Across 29 countries.

Can we replace the static numbers currently used with an API call for current number(s)?
Noting that the sq km total doesn't accurately include the new project types.

Link to https://www.transifex.com/mapswipe/mapswipe-app/ where you can volunteer to translate the app (or this website) in your own language.

Refined scope from mapswipe/mapswipe.github.io#19

the links to some of the files for download changed due to some changes in the backend. This needs to be accounted for on the website.

• tasks
• results
• agg_results
• groups

As well as calls to download from the App Store and Google Play, we should link to the apk.

To be accurate, this will be dependant on mapswipe/mapswipe#149 being completed that will ensure the same link always points to the latest version apk.

The link is likely to be this but will need testing after above ticket completed: https://github.com/mapswipe/mapswipe/releases/latest

ideally the download page for data would change based on the mission type
see https://mapswipe.org/en/project.html?projectId=-Mtnp5Rlx5n_tF5KNdjF
right now, the building footprint mission will have data products that aren't applicable and aren't generated but are still listed with broken links - e.g. "HOT Tasking Manager Geometries" and "Moderate to High Agreement Yes Maybe Geometries"

at what level does the support from American Red Cross become "large" and let us add our logo to the bottom of https://mapswipe.org/en/about.html ?

• Text in several places on the site needs to be adapted to better represent the expanding scope of the project and additional project type(s).
• Language should be updated to be more inclusive of a global community. Text such as "Help humanitarians find and help vulnerable people" removes agency/dignity from the communities we seek to support.

Related:

• #8
• #7

Like on the old website, it would be good to acknowledge everyone who works on the app.

Thinking a more lowkey design - e.g. a small photo, name (maybe as a tooltip), and a link to page of persons choice.

To be added to about page. Needs designs!

Not even sure where to add but would be good to link to the site and provide some info:

https://opencollective.com/mapswipe

Current call to action on get involved page is to email.

Need to develop training and helpful resources to host mapswipeathons. Could also link to the Missing Maps resources. Once ready, change the call to action to link to / download those resources, rather than email.

• need to choose the site-builder/CMS first.
• it should be easier to translate the website and faster to publish new language version
• review alternatives to Transifex. the app is translated through Transifex, so we probably don't want to switch but is there reason to move to something else like Weblate?

Related:

• #11
• #46

Currently we have things sit for extended periods because the flow is not well understood. Such as:

• #53
• #54
• #62

And there's no way of knowing which versions are live (e.g. https://mapswipe.org/cs/) and no way of easily switching between them.

Setup the site to be able to translate into multiple languages:

• Design for language selector
• Integrate the solution - probably Transifex
• Workflow for translating and updating