I don't know if you read the article. REST is a post-hoc description of how the web worked (at the time it was made). You had web pages with hyptertext conten

I don't know if you read the article. REST is a post-hoc description of how the web worked (at the time it was made). You had web pages with hyptertext content, and that included forms. The forms had fields with names and an "action" destination. The client (the browser) knows nothing about the server or even its APIs. It just knows how to send an HTTP request with parameters. In the case of forms, those parameters were encoded in the body of a POST request. That's it. There was no "client side code" that talked to the server. The "client side" is literally just the browser. Talking to the server is done by the user clicking links and filling forms. I don't think the article is particularly encouraing you to program this way in 2022. Just telling you that if you are not programming in this way, do not call what you are doing "REST", because it is not.