Ask HN: Who needs help with side projects?

I really like this idea! I feel like you could have the character mapping and input be geared towards writers for a story documentation tool as a UI and framework for the generated content would be in what a writer would need. Then offer as much or as little generator access as the user wants.

For that generated content, I do a lot of character creation in a completely different context than writing/D&D, and I would pay for a service or software that let me input or override the story type character data with ones of my own making.

The goal of self-sustaining stories that can be tweaked or woven into is awesome.

I am working on "Free Hero Mesh" project (but it is not written in Python or Java). It is a puzzle game engine, and is FOSS.

Things that I can use help with are including (but not necessarily limited to):

- Promotion of project

- Testing

- Bug reports and feature requests

- If you are interested to make something with this

- Porting and distributions

- Patches to the code, if necessary

- Maybe someone has idea to improve documentation (such as tutorials) or to make a logo, or something else

http://chiselapp.com/user/zzo38/repository/freeheromesh

http://sparrowhub.io:2222 - SparkyCI - dead simple CI service.

Please give me a shout if you need to add other languages support. I would consider such an interest as a help )))

So far the service supports amazing Raku language, but the platform is general enough to support other languages as well …

Also I would appreciate help with frontend … The UI is simple html plus some JS / css under bulma.

Thanks. Something I missed is that the JSON is gonna be updated every 1 minute.

I've never tried netlify or vercel, I've been told that the 1 min updates are a problem in platforms like that. I'm an nginx kind of guy but I'm helping an org that has no budget whatsoever and I'm exploring options.

Perhaps less of a code-related comment than you are looking for, but: to make it easier to collect feedback on the architecture/code, I think it might help to add a readme document that summarizes the layout and structure of the repository in a few paragraphs.

Yes, there's a bit of overhead to maintaining that, and it can fall out-of-sync with the code over time.. the key benefit, though, is that it provides useful context for reviewers, a bit like a geographic map does when navigating a new place.

The goal should be to make people feel like they understand more of the purpose and design of the project shortly after they arrive; as a result they'll be able to figure out what aspects of their own experience they can use to help review (and perhaps contribute changes to) the code, and where to go (in terms of files/directories/modules) to best apply that expertise.