Many algorithms in Project Euler do not follow coding styles as mentioned by @dhruvmanila here, or even the standard coding guidelines.

Notes:

• A lot of inconsistencies with the solution functions (a lot of them aren't named as "solution")
• docstring inconsistencies:

>```docstring```
vs
>```
docstring``

Most appropriate sub-area of p5.js?

• Color
• Core/Environment/Rendering
• Data
• Dom
• Events
• Image
• IO
• Math
• Typography
• Utilities
• WebGL
• Other (specify if possible)

Feature enhancement details:

Currently, several DOM examples are not executed in the reference. It is always helpful to have the example code exec

Description of Change

1. adding new feature - articulation point algorithm. In a graph, a vertex is called an articulation point if removing it and all the edges associated with it results in the increase of the number of connected components in the graph. For example consider the graph given in following figure.
2. moving the GraphRep struct from Graph.c to Graph.h

References

<!

Like in #1675 we should review all the dependencies to see if we can pin exactly what dependencies we want. Something like pip freeze.