General code audit

[jessicaschilling]

This issue is for the need for an overall code audit, focusing in particular on:

• Modules etc that could be removed as a result of being ported over from PL blog but not needed here
• Potential barriers to deployment over IPFS

Please separate the results out into their own issues so they're easier to work - thanks!

[jessicaschilling]

@cwaring -- thank you for identifying any problems here as you find them! 🙏 I can separate into checklists or individual issues as need be.

[cwaring]

I'll report back with an evaluation within the next couple of weeks, and also my suggestions to #41.

[jessicaschilling]

@zebateira - per our conversation, are you able to work with @cwaring and @jdiogopeixoto to get this and #41 resolved? As we discussed, we might also want to look into establishing some sort of ongoing instrumentation for the blog to keep an eye on performance as the blog continues to expand over time. Thank you!

[jessicaschilling]

Note re instrumentation: @atopal recommends https://speedcurve.com/.

[jessicaschilling]

Do we feel we can close this issue in favor of #41?

[zebateira]

@jessicaschilling I would prefer to go forward with a separate code audit from the payload issue. Will leave an update here soon about this.