I have now added some acceptance tests that do "black box testing" that your GSOC additions update gatsby develop when pages are deleted, modified or added.
Example run starting from line 1222 at output log of https://travis-ci.org/collective/gatsby-source-plone/jobs/561341455
I cannot say, into how small functions you should refactor the code. Something that looks clean and easily understandable. Something you could be proud to say you wrote it.
After refactoring and updating the documentation (probably the MD-files in docs-folder is enough; updating the Plone site fixture requires use of Plone), it's up to you if you'd like to do some stretch goals (websocket reconnection, logging refactoring, or more) or just try
@iFlameing Thank you a lot for your hard work (and learning new things while doing that)!
It's been a pleasure to work with you and follow how you and your code improved during the summer.
I will pass the last evaluation for you so you can prepare to write your GSOC completion post to community.plone.org :)
@iFlameing About PloneConf, try to ask Cris Ewing about it at https://community.plone.org via private message.
Previously, when Plone Foundation was on GSOC on its own, it was possible for the foundation to use the GSOC funds from Google to sponsor students' trip to the conference.
Now, under PSF, I don't really know.
@iFlameing About feedback, communication really depends on team and project, but I really believe that issues and pull requests are the best way to communicate with open source projects. And you learned that well during the summer.