-
-
Notifications
You must be signed in to change notification settings - Fork 388
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation #337
Comments
This issue appears in the answers to question “What annoys you about Maputnik?” in the survey (original spelling):
|
Just a note that we may want to document #301. |
|
Maputnik needs better documentation. Over the course of the year there have been a few issues raised and comments in issues with people confused what Maputnik actually does. I don't think it's that clear from the project what it does and what it's aims are.
How about we create a documentation repository (maputnik/docs) and start building some good documentation.
My initial thoughts of what would be good to cover
So basically it'd be a guide to both using Maputnik and to some extent working with the MapboxGl style spec. Although if you have better ideas feel free to run with them
Would anybody be interested taking on the challenge?
I would prefer someone with prior experience, I'm going to nominate @gregorywolanski @pathmapper @keum. I realise this is quite a lot of work, so there's no pressure intended from me.
The text was updated successfully, but these errors were encountered: