Hi everyone, I hope you're having a good start to your week. If you don't know me, my name is Perry, I work for Netlify, and I'm currently in the process of building out Netlify's first ever forum! It's not open to the public yet, as we are currently still beta testing things, but when it is, it'll be a fantastic resource to get your technical questions answered and also to connect with likeminded people, make some new friends, hear about new resources and meetups, that kind of thing.
If this sounds exciting to you - I'd love to add you to our list of people who are getting sneak previews to our community. Ping me here or send me a note to firstname.lastname@example.org and I'll get you added! See you around soon.
Hi all! Just curious what kind of topics you've covered at your meetups? Which topics brought the most interest/least interest? Here's some we've had at the JAMstack Boston meetup so far:
Hi JAMstack community. I'm new here and i would submit my example site on jamstack.org website, but i'm not able to create a new brach on website repository, to make a pull request. Whats the best way to submit my example site on jamstack.org repository?
Thanks for help and support.
@QueyeHaach sounds like your use case is well suited for JAMstack, so far. You would benefit from faster load times, better caching and (depending on your CDN provider) more local servers. By having an explicit build step, you might find it easier to pack, minify and compress your assets better (if you're not using something like webpack already).
You might want to go serverless from there: firebase can be used serverlessly by using Netlify Functions or other FaaS providers, so you'd have to adapt your code if you wanna go serverless. If you do not want, you can keep running your own API server for the database stuff via Firebase CLI, though.