Netlify

Vue.js vuex Vue Router Quasar Framework Electron Node.js npm Yarn Git GitHub Netlify My tech stack that helps me develop quickly and efficiently. Wouldn't want it any other way.

So if you look through my decisions you will see I recently wrote a decision about moving from Netlify to Buddy and Amazon S3.

I want to write another decision saying that I tried this out and actually moved back to Netlify. Buddy was great until they deleted my account and all my pipelines I setup without warning me because I didn't login for a month.

Netlify is amazing and way easier to setup, support is great and they have so many amazing options... I did learn things about Amazon S3 by moving over to there but I'm sticking with Netlify for the long run now.

I was just hired to help an enterprise event production company with their web tools. Due to COVID they are streaming 100% online and need to make hundreds of mini-sites/small-scale apps for each event. They are currently using Squarespace and just making a sub-dir for each new event I i.e., our-squarespace-account/{some-awesome-stream}. This becomes a nightmare when there are several sub-events and events span several days etc.

I am trying to plan a service with the following: - Top level view of all sites we create - Ability to develop a new site locally and push up either to our domain or a custom domain - Each mini-site will be bespoke, but a CMS is needed for producers to edit content and change basic info - Some kind of interactivity and capture of email and name is a must (this can be a separate service) - Eventually, building a client dashboard for them to see statistics - Piecemeal rollout and development of these services

Currently, I have narrowed down using Gatsby as an ssg to make an event page (cloning from one of a few templates). Then I would customize and push it to a Netlify hosted site. I am running into problems with the structure. I want my company to be an umbrella site so we have a top-level view of every site we create, but each client only has access to a simple cms for their event. Content changes should be easy to make via a CMS.

I know this is a lot, so thanks in advance for the input!

We use Netlify to host static websites.

The reasons for choosing Netlify over GitHub Pages are as follows:

• Netfily can bind multiple domain names, while GitHub Pages can only bind one domain name
• With Netfily, the original repository can be private, while GitHub Pages free tier requires the original repository to be public

In addition, in order to use CDN, we use Netlify DNS.