Documentation [Tracking Issue]

[lseelenbinder]

This is designed to track the state of the documentation for the fork.

• Replace Mapbox Nomenclature with MapLibre maplibre-gl-js-docs#1
• Deploy to (maplibre.github.io/docs ?)

[markgis]

Is the plan to take docs from Mapbox website piecemeal and update all references to maplibre?

Or would it be better to re write them from scratch and bring in certain sections just using the mapbox docs as a guide? Happy to help with that project, if I can.

[lseelenbinder]

The docs are BSD, so there's no issue reusing them, as long as we remove references to Mapbox, as we are doing in the codebase.

[nyurik]

I would propose we create a new repo and push the content of the original one up to 1.13, instead of using the github fork feature. This way it is not tagged as a fork in github, and not linked back. This is an irony of wording -- github "fork" is different than project "fork". The first is about closely related stuff that could (hopefully) rejoin. Here projects are divorcing for good without the intention of re-merging (unless upstream changes their licensing terms again?).

Unless anyone objects, I will do this shortly.

[lseelenbinder]

Fine by me @nyurik. I thought we could ask GitHub to remove the link, though?

[nyurik]

we could, but easier to do it right from the start, without the extra hassle :)

[nyurik]

Oh, I just saw that that repo has already been forked, so yeah, might as well ask github, and plus force-push to remove newer information

[wipfli]

One thing I love about mapbox is their great documentation. Can I somehow help setting up the maplibre documentation? I would be happy to go through the repo an start changing the names.

[wipfli]

Actually this might be the wrong place to discuss about documentation since now there is a separate repo for this. If you see it this way @lseelenbinder please cross-reference the docs repo and close this issue here.