Add Contact form to your Ghost blog

Standard

Ghost does not ship with the functionality of a form so we have to choose a third party service and there is one Formspree. It lets you add forms to a static site which is great since all we need to do is embed an HTML5 form that does not require any coding skill. All you need to do is replace your email address in place of

<form id="contactform" action="//formspree.io/me@example.com" method="POST">
<input name="name" type="text" placeholder="Your name" />
<input name="_replyto" type="email" placeholder="Your email" />
<textarea name="message" placeholder="Your message"></textarea>
<input type="submit" value="Send" />
</form>

Once you add this form submit it and it will ask you to verify the setup by sending you mail on that address once verified your form is ready. Thank you for reading, For more posts stay tuned.

Downgrading Ghost

Standard

You would have recently noticed the downtime on my website, well it was not a server maintenance day it was me being fed up of the numbers of bugs and other issues I was facing with Ghost version 0.9.0.

In the recent months, I switched to Ghost and the reason was due to the way its interface was and ease of use. Completely designed for content development. It helped me be more productive because I could focus on writing and all I wanted was that. I preferred it because my website has a minimal designed and is oriented towards readers for other types of websites a fully blown CMS is a much better option like WordPress.

I was enjoying every moment of writing in Ghost until 0.6.4. I was aware that it lacked a lot of features that other platforms offered but the fact that I could preview Markdown side by side and have almost complete screen occupied for content writing made me stick with it. It was all perfect until Ghost decided to redesign the admin interface in version 0.7.0 which looked nice. I instantly upgrade to it and started working with it, at first it was nice until I started feeling that the sidebar occupies a lot of space and when set to hide would pop up every time my cursor moved close to the focus area, I could avoid that so I did not care about it and continue to upgrade it with the latest release.

Over time I started discovering that sometimes I typed to search for a blog post with the right post name it would never appear in the search result and at times open the post I was editing earlier that was not related to the search. What I expect was it being fixed in a newer release which never happened it started getting worse.

The admin panel already started loading slower and the login process would take a longer time instead of thing speeding or getting stable newer feature were included in beta that was not at all functional which was most disappointing.

Normally a software or app is supposed to get better more stable in a newer release instead this got slower and start to have more bugs and non-functional beta features.

All the beta features are supposed to be functional and not to be part of the app as a dummy.

I got annoyed and switch to version 0.6.4 which is faster and feels nicer.

Thank you for reading,

for more posts stay tuned.

When to use a static site?

Standard

Static sites are great they don’t require a Database or pre-processors and they don’t require any complex server sided setup to get working. All you need is a web server that is set to serve a static folder. In the earlier days of the Internet, everything was static and had to be written because pre-processors and server side scripts were not a thing. At that time almost every web page had to be hand coded which was time-consuming. These days we have pre-processors and server side scripts which let us create websites, web applications with ease and has also reduced the amount of code we have to write this also has resulted in a lot of developers adopting DRY(Don’t Repeat Yourself). The static site still exists and are in use, but the real questions are *Are they an overkill?When to use one? and How often is the content being updated mattersIs it difficult to create one?**The benefit over another type?*Hosting?

Are static sites an overkill

Yes, if it is being used in a setup where a Database drove the website is doing fine and does not turn into a resource hog on a web server.

When to use one? and How often is the content being updated matters

If yes, then you how often? if the site is going to be updated every date or once in a week, it makes total sense to go static especially if you are a single user/admin. If the site is updated hourly or after certain minutes then it can remain static only till the updates are client sided why? because after a certain number of pages (150-1000) static site generators and website builds get slow and can be much slower if pre-processing of stylesheets and scripts are done. I would highly recommend going for a Database driven CMS if your website has multiple authors are multiple content publishing in such a senior a static site build would be more of a hassle and at some point turn unmaintainable as each author might end up having a different version of the same or different content.

Is it difficult to create one?

No, these days we have static site generators like Jekyll and many other popular static site generators that are well documented so a less knowledge person can also create a simple and fast website. Most of the static site generators like Jekyll ship with markup stylesheet and scripts pre-processors like Markdown, Sass, CoffeeScript that give you more control over your output. It is also lighter because it is a pre-rendered page which can be great for a high traffic website that does not update often especially when running on a low spec server

Benefits?

It is faster than a Database driven website because it does not require any server sided pre-processing or querying or doing any kind of fetching. It can be built on any system supported by the specific static site generator. It can be previewed locally much easily before being published to production. It is more like a filesystem, so it can be version controlled easily with the help of Git or Mercurial or any other DVCS tool.

Hosting?

All you need is the output of the static site and place it into the webroot even the most minimal web server can serve the website. GitHub offers GitHub Pages service that lets you host your websites on *.github.io domain, which is great if you want to have an open source website. It also offers Jekyll integration. Which makes it cheaper to host, which is great if you don’t want to spend a lot of money on. I would recommend that you do good research over static site generators and builders so you can find the right tool for your website. The other great benefit is Thank you for reading, Like always stay tuned for more content.