Hi guys,
I am looking for someone to work with me on a project called rhp (2.0) that has gotten pretty large in size. It is a solid-native charting/plotting library designed for web infographic-style data visualizations. Styling and interactivity were key to the tech stack choice and why I avoided SVG or Canvas for creating plots. This project was inspired by several beautiful and highly interactive hand-made (hard-coded) graphs and charts I found on a few websites I visited.
What I need help with
I need help revamping rhp-home which I now want to be the "product"-style landing page (even though this library is free and open-source). The current landing page can be repurposed somewhat but it still needs to be built out to sell people on using the library. We also need to work on framework ports or making rhp framework agnostic. Currently, I managed to get rhp 2.0 working server-side (again) and I created a react wrapper port. I want real ports because users of each framework need to be able to build their own plots without knowing solidjs.
I also need help finding and adding support/examples for other types of plots where data and information can be grouped together visually (for example, each data value has an associated image and labels and area in chart).
Also, I am evaluating a possible upgrade to Solid 2.0. I think its too early atm but if there are performance gains or other things that benefit this project, it is worth considering.
I also want to work on AI agent adaptors or mcp servers that allow agents to create these plots using the library (while at the same time, keeping developers as first class users).
Overall, rhp performs pretty well compared to many other libraries. It's of course slower than the fastest SVG and Canvas plotting libraries but thats expected given DOM and CSS which I do not want to give up (they are core features of the library). It's also pretty light-weight.
(below is extra info...its a long read)
---
Background to explain the current state of project
A long time ago (3 years ago) I created rhp which used to be short for react html plots. rhp (now called reactive html plots) is a charting library that is designed for creating interactive, dynamic, and visual infographic-type plots. Especially the types that are structured a certain way.
Obviously, I built rhp 1.0 using react and for multiple reasons such as size of user base. However, I over complicated and over-engineered the hell out of it. It was a mess because of two conflicting/competing directions I was trying to aim it towards. It was a mess but I learned a whole lot. I tried to force signal behavior and fine-grained reactivity in react to get better performance when data changes and even created a mini serializable virtual-dom. The pain of trying to squeeze performance and make it usable taught me what I should have done and how I should have built things from the start. Lessons learned. I got it working and performing ok but I was not satisfied with many things so I never promoted it. Anyways, I paused the project and put a disclaimer that I intended to revamp the whole thing.
I attempted a reworking a year later but it was a huge undertaking and stopped midway into refactoring and moving the project over to using solidjs instead of react.
Recently, thanks to AI and additional things I learned to keep in mind from my refactor, I was able to rebuild this project! Thanks to all of my notes and all of my existing code (that I coded prior to AI boom) I was able to give AI agents everything they needed and the correct instructions and specs to get this project as close to how I wanted it as I could. There were even additional places for performance improvements I was able to find thanks to Opus 5.5's performance testing approaches.
I wanted to talk about AI's involvement for transparency reasons and to make it clear that rhp 2.0 is currently an AI assisted project. However, the original code that the AI worked with and took from was all mine. Most of the endeavor was telling AI what I wanted it to strip out and explaining why I did certain things so it is aware of my goal and does not copy over things that no longer suit our goal or are superfluous/redundant. And also simplification and reorganization (reducing the number of blocks and their complexity..ie reducing excessive configurability).
rhp expects devs to code the CSS to style the chart themselves. Or grab styles from someone else's plot. Plot layout is simplified by reducing to the common denominator (a template component that we call a 'slat') which is built using a small number of building blocks. The result is that even if your plot layout is sightly different from someone else's, it is easy to adapt their CSS to work with yours. Sometimes it will be just plug n' play. This is explained in more detail in the docs.
EDIT:
If you see stutters in the video, it's something that resulted in the upload to reddit. There are no stutters in the actual video or the transitions/animations in the plots (that I can see).