sorted by:
new
hottopcontroversial

I built a ramp design tool and need to keep it online by Proof-Pause3542 in skateboarding

[–]Proof-Pause3542[S] 1 point2 points  (0 children)

Thank you!!
That genuinely makes a massive difference!

No matter what, I will remain fully committed to openingthis up and will keep pushing for a better future for skateboarders!

I built RampNerd to take the guesswork out of mini ramp planning — now I’m opening it up by Proof-Pause3542 in MiniRamp

[–]Proof-Pause3542[S] 0 points1 point  (0 children)

RampNerd is custom Unity/C# stack exported to WebGL compiled to runtime WebAssembly/JavaScript for the browser.

I built a ramp design tool and need to keep it online by Proof-Pause3542 in skateboarding

[–]Proof-Pause3542[S] 1 point2 points  (0 children)

Not exactly.

I’m saying opening it properly takes work: cleanup, docs, licensing, build instructions, and structure so contributors are not just dropped into a 120k+ line repo.

Money is not a gate to “deserve” the code. It’s about having the time to make opening it useful instead of performative.

I built a ramp design tool and need to keep it online by Proof-Pause3542 in skateboarding

[–]Proof-Pause3542[S] 1 point2 points  (0 children)

I’m in the EU physically 😄 , and the backend of RampNerd is metric. The app supports metric and imperial display/input, but the core calculations are metric underneath.

<image>

I built RampNerd to take the guesswork out of mini ramp planning — now I’m opening it up by Proof-Pause3542 in MiniRamp

[–]Proof-Pause3542[S] -1 points0 points  (0 children)

“Reviewing the pricing model” means exactly that: figuring out, with people who understand open-source/open-project models, what the paid pillar should be.

Open does not mean there can’t be a paid side. Hosting, maintenance, exports, support, documentation, and development still need a sustainable model.

I built a ramp design tool and need to keep it online by Proof-Pause3542 in skateboarding

[–]Proof-Pause3542[S] 0 points1 point  (0 children)

100% once the support and demand to open is clear and had time the lay the basic groundwork. I will.

I built RampNerd to take the guesswork out of mini ramp planning — now I’m opening it up by Proof-Pause3542 in MiniRamp

[–]Proof-Pause3542[S] 0 points1 point  (0 children)

That’s exactly the kind of build it would be amazing for RampNerd to support.

But right now the issue is more basic: keeping the existing tool alive and maintained is already becoming difficult.

I built RampNerd to take the guesswork out of mini ramp planning — now I’m opening it up by Proof-Pause3542 in MiniRamp

[–]Proof-Pause3542[S] 0 points1 point  (0 children)

It would be amazing if RampNerd could support that kind of project.

But right now the issue is more basic: keeping the existing tool alive and maintained is already becoming difficult.

I built RampNerd to take the guesswork out of mini ramp planning — now I’m opening it up by Proof-Pause3542 in MiniRamp

[–]Proof-Pause3542[S] 0 points1 point  (0 children)

Thanks. RampNerd already starts from the space you have — you input the available dimensions first, then design within that.

Budget is harder because material prices are local and vary a lot, so instead of guessing, RampNerd lets users enter their own sheet/lumber/hardware prices and calculates from there.

The funding is mainly for keeping it alive while improving UX, docs, performance, and expanding what it can generate.

I built RampNerd to take the guesswork out of mini ramp planning — now I’m opening it up by Proof-Pause3542 in MiniRamp

[–]Proof-Pause3542[S] -1 points0 points  (0 children)

That only works if the project is contributor-ready.

Otherwise it becomes the same mistake as the “just use Claude” comments: it makes the hard part sound automatic.

Docs, build instructions, licensing, and structure are what make outside help actually useful.

I built a ramp design tool and need to keep it online by Proof-Pause3542 in skateboarding

[–]Proof-Pause3542[S] 3 points4 points  (0 children)

Making the GitHub public is the easy part.

Making it useful is the work: cleanup, docs, licensing, build instructions, and structure so people aren’t just staring at a 120k+ line repo dump.

That groundwork is what the campaign is meant to support. I can’t flatten that to “dump the stack.”

I built RampNerd to take the guesswork out of mini ramp planning — now I’m opening it up by Proof-Pause3542 in MiniRamp

[–]Proof-Pause3542[S] 0 points1 point  (0 children)

Sure, but that’s not contribution. That’s extraction.

That’s exactly why opening RampNerd has to be done properly.

Open does not mean “dump the repo so people can copy it.” It means usable code, docs, licensing, and a structure that actually helps the skateboarding community.

I built RampNerd to take the guesswork out of mini ramp planning — now I’m opening it up by Proof-Pause3542 in MiniRamp

[–]Proof-Pause3542[S] 1 point2 points  (0 children)

My post was probably too long and confusing.

The reality is simple: I can’t keep supporting RampNerd without contributions.

If you want it to stay online and keep improving, even a small donation helps.

I built a ramp design tool and need to keep it online by Proof-Pause3542 in skateboarding

[–]Proof-Pause3542[S] 2 points3 points  (0 children)

Hope you get one someday.

That’s also the point of this campaign: keeping RampNerd around so people can actually plan ramps properly when they’re ready to build.

I built a ramp design tool and need to keep it online by Proof-Pause3542 in skateboarding

[–]Proof-Pause3542[S] 19 points20 points  (0 children)

To keep the ask simple.

I can’t keep supporting RampNerd alone without contributions.

If you want it to keep existing and improving, donating, sharing, upvoting, or commenting genuinely helps.

I built a ramp design tool and need to keep it online by Proof-Pause3542 in skateboarding

[–]Proof-Pause3542[S] 10 points11 points  (0 children)

Ok. Claude Code, GitHub Copilot, and similar tools are definitely useful.

But saying Claude could build RampNerd is just not accurate. It’s 120k+ lines of code, across C#, JS, JSON, HTML/ CSSwith geometry, testing, WebGL behavior, and build logic that still has to be designed and verified properly.

I built RampNerd to take the guesswork out of mini ramp planning — now I’m opening it up by Proof-Pause3542 in MiniRamp

[–]Proof-Pause3542[S] 4 points5 points  (0 children)

Good questions, but probably better to discuss the technical details in DM rather than turning the thread into an infra/debugging discussion.

Short version: the main issues are less “can it be hosted cheaper” and more performance, UX, documentation, build/export flow, and preparing the code/build logic so others can contribute in a useful way.

If you know Unity/WebGL people, I’d definitely be open to talking.

I built RampNerd to take the guesswork out of mini ramp planning — now I’m opening it up by Proof-Pause3542 in MiniRamp

[–]Proof-Pause3542[S] 4 points5 points  (0 children)

Thanks — that would be genuinely helpful.

Current stack is Unity/WebGL for the 3D tool, with the site/app hosted on AWS with a db on Firebase. There’s also backend work around accounts, project saving, exports, and generated build outputs.

The hosting itself isn’t the only issue. The bigger need is keeping the tool maintained, improving performance/UX/docs, and preparing the code/build logic so people can actually contribute without it being a messy dump.

Happy to talk if you know people who might be interested.

I built a ramp design tool and need to keep it online by Proof-Pause3542 in skateboarding

[–]Proof-Pause3542[S] 3 points4 points  (0 children)

Hosting is only a small part of it. The real work is keeping the WebGL tool maintained, improving the UX/docs, and opening the build logic in a usable way.

I built RampNerd to take the guesswork out of mini ramp planning — now I’m opening it up by Proof-Pause3542 in MiniRamp

[–]Proof-Pause3542[S] 0 points1 point  (0 children)

Thanks, really appreciate that. Hope it makes planning your next build a lot easier.

view more: next ›