Hi, the project was built on sapper. I was obliged to do this, because the first plan was to create a SPA. I have decided to do this in svelte - It is nice environment to create such small nice webpages. And when it was done, client said me that now he thinks, that he needs a multipage -_- .The only way to do this and not rebuilding my code was to move to sapper. If i knew, that it will be a multipage, I would do it in Gatsby. If you are curious - I don't recommend using sapper, but svelte as a framework works fine.
I also gave a headles CMS to my client - In my case it was DatoCMS. I did a whole job with it, and at the end gave account to my client, and then teached him how to manage content with it.
Client has no problems with managing content and netlify hosting works absolutely fine
Nice, I'll check out Svelte + DatoCMS. So I guess that DatoCMS also has webhooks to connect with Netlify?
Speaking of image-heavy portfolio websites, I also recently built a Gatsby site for an artist. The gatsby-image plugin is really great, I can absolutely recommend: On the server side it does automatic resizing of your image files, and on the templating side it helps you with responsive images. That being said, the image resizing also eats up build minutes on Netlify, but up to now, we're still not at capacity at Netlify's Free Plan :-)
Thanks, I know Gatsby very well, my own portfolio is built on it. I like this environment, it's amazing. I'm not sure if Dato has any webhooks, I'm just doing request on the front-end site and getting necessary data :D
I checked out DatoCMS and I'm already a fan :-D So simple and intuitive for both devs + clients (that's not easy to achieve I guess)!
I found a sample project for Gatsby + DatoCMS + Netlify that establishes the hooks automatically.
Checking out the free plan of DatoCMS: 200MB file storage is not that much though. Especially for image-heavy websites and if you want to store the raw files and do further processing with gatsby-image...
Yeah, that's true. If you want to build a big portal, dato has limited memory. It also allows you to use only 20 models (or something like that). But for really normal pages, like 4-page portfolio, dato works perfect :D
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.
Hi, the project was built on sapper. I was obliged to do this, because the first plan was to create a SPA. I have decided to do this in svelte - It is nice environment to create such small nice webpages. And when it was done, client said me that now he thinks, that he needs a multipage -_- .The only way to do this and not rebuilding my code was to move to sapper. If i knew, that it will be a multipage, I would do it in Gatsby. If you are curious - I don't recommend using sapper, but svelte as a framework works fine.
I also gave a headles CMS to my client - In my case it was DatoCMS. I did a whole job with it, and at the end gave account to my client, and then teached him how to manage content with it.
Client has no problems with managing content and netlify hosting works absolutely fine
Nice, I'll check out Svelte + DatoCMS. So I guess that DatoCMS also has webhooks to connect with Netlify?
Speaking of image-heavy portfolio websites, I also recently built a Gatsby site for an artist. The gatsby-image plugin is really great, I can absolutely recommend: On the server side it does automatic resizing of your image files, and on the templating side it helps you with responsive images. That being said, the image resizing also eats up build minutes on Netlify, but up to now, we're still not at capacity at Netlify's Free Plan :-)
Thanks, I know Gatsby very well, my own portfolio is built on it. I like this environment, it's amazing. I'm not sure if Dato has any webhooks, I'm just doing request on the front-end site and getting necessary data :D
I checked out DatoCMS and I'm already a fan :-D So simple and intuitive for both devs + clients (that's not easy to achieve I guess)!
I found a sample project for Gatsby + DatoCMS + Netlify that establishes the hooks automatically.
Checking out the free plan of DatoCMS: 200MB file storage is not that much though. Especially for image-heavy websites and if you want to store the raw files and do further processing with gatsby-image...
Yeah, that's true. If you want to build a big portal, dato has limited memory. It also allows you to use only 20 models (or something like that). But for really normal pages, like 4-page portfolio, dato works perfect :D