Firmware Documentation

@Rahul_G A good starting point is to structure your application code in a way that is consistent and readable. Here is a link to a post from one of the top contributors on this forum that should guide you: Photon offline mode

Additionally, if you are using Workbench / VSC you can include these sorts of documentation tags

/**************************************************************************/
/*!
   @brief    Write a line.  Bresenham's algorithm - thx wikpedia
    @param    x0  Start point x coordinate
    @param    y0  Start point y coordinate
    @param    x1  End point x coordinate
    @param    y1  End point y coordinate
    @param    color 16-bit 5-6-5 Color to draw with
*/
/**************************************************************************/

You could read something like this on stack exchange: https://writing.stackexchange.com/questions/36232/where-do-i-start-with-c-documentation

When you say ‘private tools’ do you mean local and not cloud?