Check the many forks if some of them has changed reasonable parts

[mliebelt]

There are many forks created, and I should check why those forks were created. So is there any reasonable implementation done? What is the main focus the forks want to address? Try to find the reason a fork was created, to see if

• there are features that should be provided
• there is functionality that is not configurable but should be
• there is styling done that could be addressed differently
• ...

[mliebelt]

So here is the list of repositories, that had some additions in their fork. I leave all out that only have forked but not committed anything.

• [Bebul]((https://github.com/Bebul/PgnViewerJS/commits/pgnPuzzle) working on puzzle #2
• chess-center worked on integration of the viewer, but no change in the viewer was necessary.
• jvsteiner introduced some functionality to allow steering the viewer from the outside. Was integrated, and is addressed by #175
• LTe provided a recipe for React, and the information to allow different import methods.
• s-farry introduced pgnTactic, similar to #2 (I think). Tried it out, nice! There would be some cleanup necessary, and I think additional features could be introduced as well, but hopefully this will be continued somehow.
• tkanjanarux A complete implementation of Thai Chess, with some interesting features. I was not able to bring the whole thing to run :-( so I cannot say anything about it. The project was not developed any more the last year ...
• xeyownt Addes some french translation, was integrated.

That is it, most of the forks have no visible changes (commits or branches), so I cannot say if there is something to be watched. The most interesting change is by Stephen Farry, hopefully this will lead sometime to a merge request.