- If you've never used git before, it will take getting used to

There's the risk that if the site grows it needs to be written from scratch because you might've missed some aspects that don't scale.

As for making an API, REST would be pretty simple to do some basic stuff. Like have beltchecker.com/api/v1/user/:id return JSON representing a user profile.

Anyone else in software development? I work with some great developers who would love to enhance this site in their free time. Is it open source? How can we help?

Yep, but mostly C++/python in the offline world. I did create a BJJ scoreboard/timer for free (openroll.sourceforge.io) but not currently planning any more releases of it. I'm kind of new to the web game but I'm catching up quickly with an online code camp. http://github.com/crajun if you want to connect.

This doesn't use any frameworks? Oof.. lol

I'm mostly a front-end dev with experience in React (I work with Drew), but if you ever decided to get some help with this thing, I would be 100% in to help. Pros of a component framework like react: -Once you have a component library of buttons, modals, icons, etc. adding new features is like legos, just combining components together. -Making this site a single page app (SPA) would make it lightning fast. Slightly increased initial load time because of the larger JS bundle, but subsequent page loads are as fast as your API can respond. -Infinitely scalable, with state management solutions like Redux or Apollo if you have a GraphQL API.. I could sell you on that too! :) -Developer quality of life is fantastic. FB is extremely careful with updates, so things like Hooks can be used with legacy things like class components. Testing is super easy, I learned most of what I know about unit testing react in a weekend. -Using React, you could also expand to a mobile app (although, the mobile experience on your site currently is really good, everyone loves apps) and share most of the same codebase using React Native. Who doesn't love making mobile apps in HTML/JS/CSS??? You could have your back-end expose some CRUD endpoints and really have a separation of concerns from your API and your front-end too. Could host everything on AWS so it would scale as needed. Also remember, open source doesn't mean you are just releasing your idea to the public freely. There is licensing that comes along with it. You could also just do a private github repo (those are free now) and invite devs you want. Consider it! I would be ecstatic to pitch in, and I'd teach you React too if you wanted! I am mostly self taught. If you have any interest in a screen share demo of some React development, feel free to PM me and I'd be happy to walk you through some code. Edit: spelling and formatting and stuffs

Making some assumptions about the existence of a user object, etc. Something like this https://pastebin.com/FDRHji4X in /api/v1/user/read_one.php would do it.

Tadaa :) https://www.beltchecker.c[...].php?id=10 All comments appreciated, I have never worked with this before.

Didn't work.

Tadaa :) https://www.beltchecker.c[...].php?id=10 All comments appreciated, I have never worked with this before.

Looks like it's showing the firstname in the lastname slot. Depending on expected use you might want to include profile image url.

Outside users probably would use the “beltname” field so they don’t need to worry about the belt rank enumeration.

Nice, for your api to be useful you need to document how to parse the output (json file) for example belt rank :11 This isn’t obvoius to a caller of the function

Btw if you feel like the site is running a bit faster today, then you're right. My friend Eric (https://beltchecker.com/p[...].php?id=35) just did some magic on the database and the improvements are just ridiculous. That's what I get for not coding anything in 15 years haha