Mainly client side. Some functions go through next's api folder.
181 karma · joined August 11, 2021
If you want to chat about how this may work in terms of UI/UX, please let me know. I think the idea is interesting. I'm @AndreVitorio on twitter.
After I've launched people pointed the existence of those CMSs. I really built this as something to scratch my own itch, halfway through I decided it could be a library.
But as someone else mentioned, it's quite hard to think of a business model around this. I'll keep working on it just so that I can use it in my own blog. If other people want to use it, that's great.
Yes, at this stage I wouldn't advise anyone to try using this in production, it's the first version of a side project after all. But I'm really surprised by the response so far. I'll definitely keep improving it.
Let me know if you manage to figure out what went wrong, and if you get any error messages/logs. I'm available on twitter @AndreVitorio
Some people have been using Outstatic without Vercel, and there's a section in the FAQs about it. But since this is the first version of the library and I haven't tested it with other services, I felt putting Vercel as a requirement would avoid people running into pitfalls with other services.
But oAuth is only setup with Github for now. So unfortunately that's pretty much a requirement.
I plan on adding support for other git providers in the future.
As for the technical details, the framework is used to manage content for statically generated websites with Next.js, using Markdown and Git to store the contents. I'll go into more detail in the docs, which should be released this week. Thanks for checking it out!