My vote for board specific details and caveats would be in the board specific page.
There is a work item to create a page for the ESP8266 ... see issue 653. I had assumed that these pages were no more than simple web pages (say written in markdown or HTML) but it seems that they are (to some degree) generated pages and this means that the page for the ESP8266 is not a trivial matter. Rather than have to study the board specific page generation architecture myself, I was hoping that someone in our community could step up and own that as a distinct task and either create a detailed recipe that would be easy to follow or act as a resource for each board creation team and own the creation of the initial version of the page for each team.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
At the start of the
Reference
page there is a detailed list of all the boards that Espruino is believed to work upon... see:http://www.espruino.com/Reference
My vote for board specific details and caveats would be in the board specific page.
There is a work item to create a page for the ESP8266 ... see issue 653. I had assumed that these pages were no more than simple web pages (say written in markdown or HTML) but it seems that they are (to some degree) generated pages and this means that the page for the ESP8266 is not a trivial matter. Rather than have to study the board specific page generation architecture myself, I was hoping that someone in our community could step up and own that as a distinct task and either create a detailed recipe that would be easy to follow or act as a resource for each board creation team and own the creation of the initial version of the page for each team.