I want to apply the same architecture to creating a new website.
I'd probably go with Netlify and Netlify Lambda (just for a search engine that is not on client side). It seems to be fast enough. Not sure about costs...
I am currently using Nuxt, but I also considering moving to Next.js with MDX support.
I feel like I was wrong in thinking that I need a CMS, whether headful or headless. I can simulate the search function with a serverless function, anyway.
Also, I was wrong in thinking that Jekyll is putting too many files in a folder. The truth is, one folder and 10k files would still not hurt the performance. Also, it is possible build a flat file CMS on top of the single flat folder, anyway.
A from scratch CMS is probably overkill. I would look at migrating to a managed service. This coming from someone who made the same mistake lol. I also do agree with the next.js move because I'm probably going to be doing the same, but from plain react.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Actually, I shipped it -- polv.cc but,
I'd probably go with Netlify and Netlify Lambda (just for a search engine that is not on client side). It seems to be fast enough. Not sure about costs...
Related,
I am currently using Nuxt, but I also considering moving to Next.js with MDX support.
I feel like I was wrong in thinking that I need a CMS, whether headful or headless. I can simulate the search function with a serverless function, anyway.
Also, I was wrong in thinking that Jekyll is putting too many files in a folder. The truth is, one folder and 10k files would still not hurt the performance. Also, it is possible build a flat file CMS on top of the single flat folder, anyway.
In the end, Jekyll isn't so bad, but I just want
That's way I might go Next.js.
A from scratch CMS is probably overkill. I would look at migrating to a managed service. This coming from someone who made the same mistake lol. I also do agree with the next.js move because I'm probably going to be doing the same, but from plain react.