server":123456, "photos_list":"[{\"photo\":\"e9f2eba71b:y\",\"sizes\":[[\"s\",\"123456852\",\"e65f\",\"Br4ir9YAvO8\",75,41],[\"m\",\"123456852\",\"e660\",\"Lqpe1N8s8zY\",130,71],[\"x\",\"123456852\",\"e661\",\"tRFbnaIP_4c\",604,330],[\"y\",\"123456852\",\"e662\",\"8JhBOy0qR6o\",748,409],\"kid\":\"569c3da3b168b347315aa5adc92a953a\",\"debug\":\"xsymyxyyyoypyqyry\"}]", "aid":98754321, "hash":"22b333dbbef7cd9b1f9829b5f8713f86"

[Fleshreg]

Pre-requisites

• Prior to submitting documentation, please apply to join the GitHub Technology Partner Program: partner.github.com/apply. Please feel free to proceed once your application is approved.

What information would you like to add to docs.github.com?

Tasks

Please be sure to complete each of the following:

Third-party product documentation:

• MUST follow our general contributing guidelines for voice and markup format.
• MUST emphasize how the third-party product works with GitHub.
• MUST be written in Markdown format, using one of the templates provided
• MUST include the name and URL of the GitHub technology partner responsible for maintenance of the documentation being contributed. This should be added via the contributor.name and contributor.URL properties in the template's YAML frontmatter.
• MUST be proposed via a pull request to this repo following the GitHub Flow.
• MUST be located in the root of the content folder. Your filename MUST match the GitHub technology partner name, and use the .md file extension.

The Pull Request:

• MUST reference this issue, e.g. via closes #<this issue number>
• MUST pass the automated CI checks
• MUST include links to supporting material demonstrating the functionality being documented (this can be a link to a public GitHub repo, or a video / screencast walkthrough)

Once all tasks are completed, please mention @github/docs-content for next steps.

/cc @github/partner-engineering for 👀