Disclaimer: I like all of the listed tasks (almost equally) and I'm happy to take on any of them at any time. My default answer is 'no favorites'; however, since it seems I must make choices, I've made some very hard ones here :)
My favorite thing about providing technical support is getting to solve a problem I have not seen before, and then helping someone with that same problem! I see it as the shortest and most exciting path to learning.
I thought it was awesome! My first experience was moving my existing portfolio site to Netlify. Everything, from connecting a GitHub repository to setting a custom domain to configuring SSL, was a breeze. Compared with other options I've tried: Heroku, GitHub Pages, and Surge, Netlify is far far far easier to setup. On top of this, my Netlify site is faster (blazing fast) and comes with free SSL! Yet there is more: the Deploy to Netlify feature on StaticGen, which I used to start off this site, is equally awesome!
Deploy to Netlify link on Gatsby to create starter site (thanks for this!).npm install --global gatsby-cli.npm install.gatsby deploy, made desired changes to the project and pushed changes back to the GitHub repository.I wanted something that could work on Windows and with existing development tools at the shortest possible time. Gatsby was the perfect fit: Windows, JavaScript (NPM), and React. Jekyll (based on Ruby) came close but is not natively supported on Windows - no time to invest on Ruby gem issues now. However, I intend to tinker with it later on, as its popularity makes it a more likely choice for customers.
Turned out that the first time I ran gatsby develop, the server started and then crashed with a very ugly output and a cryptic error: Cannot resolve module '.gatsby-context'. Irked, I jumped on the bug and shot it down!
./node_modules/.bin/gatsby develop, and, voila!Please consider providing some perspective (if you can) on the 5 most favorite/5 least favorite question - whether it's supposed to be a right or wrong answer question or you're just trying to check personality/preferences. I don't really have any strong preference, so it was hard for me to choose! Thank you!
Gatsby documentation. It think it's well done because it is simple and easy to follow, and it provides relevant examples to drive home the points. On top of this, the documentation site itself is highly readable!
I think SSL/HTTPS is important because it helps keep private information, from emails to credit card details, private. In word one word: security. Filling out private information on the Internet without it is as good as publishing them in the dailies. Related to this primary reason is credibility: in my opinion, even sites not handling user's private information in any way (like this one) 'command' a different level of trust and respect. I hate to see the ugly 'not secure' label on my browser's address bar!
A less-technical internet user most likely has no knowledge of basic networking, so DNS just sounds like DNA (or worse, assuming limited medical knowledge). I believe this is the fist hurdle to cross.
I suppose the only 'fire exit' from this hurdle is to employ an expert to do the 'dirty' job.
Having put the basic theoretical knowledge hurdle behind, it's time to roll up the sleeves and actually learn to configure it. This itself is another 'diploma'. Here the user will need to become comfortable with technical jargon like zone file, SOA and DNS record types like A and CNAME.
The user will also need to decide whether to host his DNS zone file with the domain registrar or another DNS host, and how to create correct records in each case. Thankfully, most DNS hosts have good documentation and support personnel to help with this.
Hi, sorry to hear that your site won't build. First, I would like you to know that we build your site in much the same way as you build it in your local development environment: we take the repository you supply along with the build command you specify and create a sandboxed development environment to build it. So the first things you might want to check are
If you need help with checking any of the above, or any other thing at all, I'll be happy to jump in and help to see what the problem might be. If this is the case, it would be very helpful if you could specify what frameworks and build tools you are using, so I would be better positioned to help out.
Whew, gotta give this a try some time later...