• 0 Posts
  • 503 Comments
Joined 2 years ago
cake
Cake day: August 7th, 2023

help-circle
rss









  • It sounds like you need your own API with some sort of persistent store. You may be able to reuse what you’ve done as the view layer?

    If this were something I was going to tackle, I’d start by identifying the types of users (authors, admins, users, etc.)

    Then I’d think about the kinds of workflows those users are going to need to do. E.g. admins can edit or delete anything, authors can alter their own content, users can only view data, etc.

    Now with some loose requirements in mind, start thinking about how to solve the problems for your users. This is when you start evaluating what technology might be a good fit for your problem domain.

    You could probably throw together a trivial API that only you can publish to fairly quickly if that is sufficient for what you are trying to do. I dare say chatgpt can spit out a simple rest API in whatever language you like quickly and pretty accurately.

    I wouldn’t chase making a static website tool dynamic. That will almost certainly end in heartbreak.