Cut-and-paste content from https://github.com/commons-app/apps-android-commons/wiki#user-documentation
That could include screenshots too :-)

Love the website so far @tobias47n9e ! Do let me know when it's ready to be published, and I'll add the link on our Google Play page and such. :)

Just had the idea, that a SPARQL based campaign builder would be a great idea (if and when the campaigns are added back to the app). A simple user interface to choose the campaign duration, and other details would be ideal.

Then a query could select the relevant items and export it to a format the either the app can read or access somehow. A WLM or WLE campaign should not take more than 5 minutes to set up.

As the title says, do you think it's worth migrating to bootstrap - should be pretty easy with what's on the site currently and could be easier to maintain in the future, especially if thinking of transferring to a web framework. Currently seems to be loads of CSS code that whilst including bootstrap would remove most of it and end up looking identical, or very similar at least.

It will look awesome.

Preview

@nicolas-raoul should I go for this changes. one more change that I want is make adding little transformation on hovering on features images.

Add smooth scrolling to the webpage. @nicolas-raoul

Some users who are accustomed to communicating via talk pages would be more comfortable with providing feedback in the app talk page rather than in GitHub. I believe @misaochan seems to keep a watch of that talk page and respond accordingly. So, wouldn't it be nice if we mention that users could also provide feedback in the https://commons.wikimedia.org/wiki/Commons_talk:Mobile_app wiki page? Thoughts?

Now that we maintain our campaigns/news in this repository, it would be useful to have a simple web interface that lets you add a campaign rather than editing the JSON file manually.

Editing it manually requires an understanding of JSON and can also lead to human errors.

To still keep things under our control, the form can simply create a pull request which the collaborators can review and merge.

Github API: https://developer.github.com/v3/pulls/#create-a-pull-request

With the release of the new UI in v3.0 of the app, the UI has changed significantly. Some screenshots have been changed to reflect this. Still a few more things could be improved,

1. The "View your contributions and ongoing campaigns" needs to be updated still
2. We could include screenshot of other new features and existing features which need more attention like peer review.
3. Anything else?

I noticed that the "App versions" section of the documentation page has the following line:

If you want to switch back to a previous version, please download the APK of the version you want and install it (you may need to uninstall first).

But as far as I could see, we don't publish the APKs along with each release. Did you mean to say that they would have to download the corresponding source and build the APK themselves @nicolas-raoul ? 🤔

When introducing the app to others, it would be nice to able to load the page on your phone and show it to others for scanning - Split from commons-app/apps-android-commons#536 (comment)

An example is:

This should link to http://commons-app.github.io.

Would it be possible to update the screenshots shown on the website? The upload screen ("Upload your files anywhere") in particular has changed a lot recently.

It would be nice if we could link to some Commons policies and guidelines in the website. It would help the user be aware of them before they contribute.

The following are some of the useful resources that I discovered:

• First steps to Commons
• Licensing guide
• Licensing policy
• Categorization
• File naming

Initially came up in #39 (comment)

We might want to use this:
http://blog.gitlocalize.com/posts/introducing-gitlocalize.html

There are a few features of the app that don't have much easily-accessed documentation:

• Automatic category suggestions - nearby categories if user submits a geotagged photo, recent categories, and categories based on the title of the submitted photo
• The ability to select 'share' from the external gallery or camera app, which launches our app
• The ability to take a photo from within the app with the camera option in the menu bar

I'm not sure how to add those to the website without causing too much bloat to the current single-page design, though. What do you guys think?

Bootstrap v4 alpha has been outdated according to the website. How about switching to the stable v4.1?

We have information about the app scattered in a few places on the internet. Each place has its own set of things that should be included and kept up to date:

• https://commons.wikimedia.org/wiki/Commons:Mobile_app
• https://commons.wikimedia.org/wiki/Commons:Mobile_app/Download
• https://www.mediawiki.org/wiki/Wikimedia_Apps/Commons

In this issue we can discuss some editing strategy and where to put what information.

Should we convert the pages on Commons to just 1 page? The /Download page has very little information and it is not real Wiki-content, but better suited for our new landing page.

I am in the process of migrating the website to wmflabs:

• https://wikitech.wikimedia.org/wiki/Commons-App-Web

Some open questions:

• How to redirect from the current page?
• Where do links need to be changed to point to the new page?

It seems the website could use some improvements in terms of the responsiveness and with respect to the layout. Here are a few screenshots of the issue I noticed in the website:

• Close menu and header - Fixed in #30
  

• Spurious space to the right and oversized title - Fix in #38
  

• Over-sized list numbers - Fix in #38
  

• Very close buttons - Fix in #38
  

• Menu does not auto-close when an item in it is clicked - Fixed in #34

• Possibly, use a better typography

• etc.

I would like to work on this if people don't mind me working on this and if it's worth doing it.

Although Github is a place that attracts a lot of people, it is also not the central place where the different Wikimedia communities do most of their planing. I am wondering if we should add a link to the Phabricator project as well.

Does the app link to phabricator? There is a risk that we get bug reports twice, but there is also the chance that we draw in people from the Commons community over phabricator. Some people might also feel more comfortable commenting there.

https://phabricator.wikimedia.org/project/profile/1632/

As soon as the icons are implemented the screenshot of the nearby-places screen should be replaced.

Just above "Get it on Google Play" :-)