Netlify is an all-in-one workflow to build, deploy, and manage modern web projects.
Basin is a simple form backend that allows you to collect submission data without writing a single line of code.Basin Integrations
Basin + AWeberAdd new AWeber subscribers from new form submission in Basin Read More...
Basin + Google SheetsCreate Google Sheet rows on new Basin form submissions Read More...
It's easy to connect Netlify + Basin without coding knowledge. Start creating your own business flow.
Triggers when a new deploy of your site has failed.
Triggers when a new deploy of your site has started building.
Triggers when a new version of your site has successfully deployed.
Triggers when a form receives a new submission.
Triggers when a user submits to your form.
Performs a new deploy of an existing site.
Netlify is a website hosting service that utilizes Github Pages to host custom domains. Netlify allows developers to focus on designing the site itself, as they can use any markup language, including HTML, CSS, or React. This also allows developers to create custom layouts for their pages, such as responsive web design. Netlify automatically compiles and minifies all code, so that it is ready for deployment. Netlify is used by over 5 million websites and has a global rank of 2,005 (Alexa, 2018.
Basin is a community of coders that provide free hosting for blogs written in Markdown. Basin hosts websites using the Jekyll framework, which gives developers access to many different plugins to customize their sites. Basin was created in 2017 by Alan Shreve, who has been working with Jekyll since 2015. The main goal of Basin is to make it easy for non-programmers to set up blog-driven websites. Basin has a global rank of 1,824 (Alexa, 2018.
Before we can discuss how Netlify and Basin work together, we must first understand the special relationship between WordPress and Jekyll. WordPress is a content management system (CMS), which allows developers to add features and functionality to their sites without having to write the code themselves. In this way, WordPress makes it easy for non-coders to create sites. Jekyll is another form of CMS, but it uses Markdown instead of WordPress’s PHP coding language, so that developers can create custom layouts for their site. Both WordPress and Jekyll are free to use, but both require you to upload your site’s code to a server before they can be viewed on the web. You can upload your site’s code either through FTP or via Git. With FTP, you can only upload your site’s code one time — this is not a viable option for developers who want to maintain their online presence frequently. With Git, developers can clone their source code from Github and work on it offline before committing changes back to Github later. The main difference between WordPress and Jekyll is that WordPress uses SQLite databases while Jekyll uses flat text files. Developers have to install plugins in WordPress in order to create surveys, forms, and other features. In Jekyll, all of these features are included in the core package.
As you can see, there are many differences between these two CMSs. We will now show you how Netlify and Basin allow people to build their own websites using Jekyll and Github Pages without having to worry about the technicalities of setting up servers.
In order to use Netlify, developers must first configure their domain name with DNS settings for Github Pages. This may sound confusing at first, but it essentially means that you need to enter your domain into Github’s DNS settings page so that your domain points to Github’s servers when someone looks up your URL. Once this step is complete, you simply save your settings and wait for your domain to be redirected to Github’s servers. If you do not already have a custom domain name (specifically a CNAME record. set up on Github Pages, then Netlify will assign you a random subdomain name such as “gizmo2b9935dz1y1188889.netlify.com”. This new subdomain will be assigned to an Amazon Web Services instance hosted on the US East coast; however, you can use the same process we just described above to set up your own domain name on Github Pages instead of using Netlify’s default subdomain name (or alternatively, you can log in to Netlify’s dashboard and change your subdomain name. Once your domain is set up with correct DNS settings so that it points back to Github Pages, you now need to connect your website to Netlify through the dashboard. You do this by creating an account on Netlify if you do not already have one and pasting a snippet of code into your root directory in your zipped Jekyll project fpder (this step assumes you have already uploaded your Jekyll project onto GitHub using git push origin master. This step will compile your Jekyll project into HTML files that can be added into a static staging environment on Netlify’s servers. After this step completes, you should be able to view your website’s homepage or any other static webpage on your newly configured website on Netlify’s servers (for example. http://gizmo2b9935dz1y1188889.netlify.com/about. From there, all you need to do is commit changes or add new files to your project on GitHub in order for those changes to appear on your website on Netlify’s servers — no need to set up FTP or run Git commands! Finally, you need to add a CNAME record that points back from your domain name (for example gizmo2b9935dz1y1188889.netlify.com. back to the primary URL at https://my-site-name-here.netlify.com/. This is done manually on the DNS settings page for your domain name provider (for example Google Domains. Once this step is complete and DNS has propagated across the Internet, then users will be able to see your website at its primary URL (https://my-site-name-here.netlify.com/index.html), even though the actual physical address of the site happens to be on Amazon Web Services servers somewhere in Virginia or Ohio or wherever Amazon Web Services happens to store traffic from US East Coast IP Addresses (Google Cloud Platform provides similar services hosted in South Carpina. Using this unique combination of technpogies (GitHub Pages + DNS settings + Amazon Web Services + CNAME records), Netlify allows developers to host their Jekyll projects using free hosting with no advanced technical knowledge required! There are some limitations here as well — if you want dynamic functionality similar to what is available with WordPress, then you will have to use Wordpress and pay for hosting services from other companies like Dreamhost or GoDaddy (the latter of which has a free tier as well. However, if you want simplicity with no additional costs invpved beyond what GitHub charges for hosting repositories and Git fees that are incurred when making remote commits outside of GitHub due to GitHub Pages not supporting Git pages directly yet (this feature is planned), then Netlify is a very good choice!
Now let’s look at how Basin works compared with Netlify. because Basin is designed specifically for blogging platforms that utilize Markdown instead of HTML markup language like Wordpress does, it allows developers/bloggers who don’t want to pay extra per month for hosting services and who don’t want the hassle/cost associated with maintaining their own server infrastructure in order to host their blog posts on a website that utilizes Markdown as its main markup language instead of HTML like Wordpress does. Instead of doing all of that hard work themselves, they can instead utilize Basin’s free hosting platform which takes care of all of those concerns for them! By uploading their Markdown blog posts into Glacier directly from their local computer via SSH command line tops (iTerm2 + Cyberduck + Transmit + Secure Shell), developers can keep track of their blog posts while they are in development by committing changes back into the master branch of their repository using Git tops such as submodules or other various Git commands (or alternatively by using version contrp software like SourceTree. They can then deploy their website right away using GitHub Pages by deploying their web directory into Glacier via git push origin master command from the terminal window within Terminal (which displays output in Git Bash. by installing the official Git client application via Homebrew or MacPorts and typing git push origin master from within its terminal window (you will have to configure Git first by running git config --global user.email "email@example.com" ), after which GitHub Pages will compile the contents of their repository into HTML files stored within Amazon S3 storage space and serve those files via HTTP requests from Amazon S3 (which are proxied through CloudFront as well. As mentioned previously in this section, there are some limitations here as well — if you want dynamic functionality similar to what is available with WordPress, then you will have to use Wordpress and pay for hosting services from other companies like Dreamhost or GoDaddy (the latter of which
The process to integrate Netlify and Basin may seem complicated and intimidating. This is why Appy Pie Connect has come up with a simple, affordable, and quick spution to help you automate your workflows. Click on the button below to begin.