Fr. Kenny Ang's personal website built on React Gatsby.

• Updating Posts
• Writing a Post
  • Front Matter
  • Body
  • Images
    • Best Practices
    • Alignment
    • Captions
  • Headings
  • Links
  • Book Component
• Forms
• Web Analytics

Posts can be found under src/posts folder. Each post consists of a folder with a unique name. That folder contains an index.md file and all the necessary assets such as images. For translation, create a file named index.{lang}.md, for example index.id.md. Currently this site only supports ID (Bahasa Indonesia) and EN (English), which is the default.

Basic folder structure:

posts
  |-- Post Title 1
    |-- index.md
    |-- index.id.md (optional)
    |-- image123.jpg
  |-- Post Title 2
    |-- index.md
    |-- etc ...

In your index.md file, you will need to write some data in Front Matter. Front Matter must be written at the very top of the document, sandwiched between two lines of triple hyphens (---), like this:

---
title: Lorem Ipsum
featuredImage: image.jpg
format: Article
date: 2020-02-01
category:
  - Homily
  - Mass
excerpt: Lorem ipsum
---

Currently supported Front Matter data is as follows:

1. title: Title of the post / article
2. featuredImage: Featured image, referencing file name within the same folder as the .md file
3. format: Choose Article or Video
4. date: Date when the post is published. Must be in YYYY-MM-DD format.
5. category: An array of categories of the post (can be more than one). See above for formatting
6. excerpt: Short excerpt of the post. Recommended length is less than 250 characters.

For more information on Markdown syntaxes, visit the following links (not everything is tested):

1. Basic Syntax
2. Extended Syntax
3. Cheat Sheet

1. Image dimension. Image width should be <= 1800px for full-sized images. Images of landscape orientation is always preferred than portrait.
2. Image compression. Try to upload images that are less than 300 KB. It's recommended to run the image through a compression tool such as Squoosh first before using them. For optimal compression, for images without transparency, compress them to MozJPEG format. If they have transparency, compress them to OxiPNG format.
3. Thumbnail ratio: 5:2.8.
4. Image source. Ensure that you have the right to use all your images. If you need to use stock images, ensure that they are royalty-free, or else you might need to credit properly. For example, Unsplash has royalty-free stock images.
5. Image alternative text. Ensure that images have proper alternative texts. This is crucial for the site's accessibility and SEO. Alternative text needs to be wrapped by square brackets ([your alt text here]) before the image source reference, for example:

![Child studying](child.jpg)

For inline images (i.e. images used within the body of your post, not as featured image), you may choose to align the image to right / left (and therefore wrapping some texts on the opposite side). To do so, you need to use the following syntax:

![Child studying](child.jpg '#float=left')

Adding '#float=left' after the image source will align the image to the left. To align it to the right, use '#float=right' instead.

Inline images will always be of 45% width of the container on all viewports except on mobile viewports, where 100% width will be maintained.

To caption an image, add the caption as image title, with the following syntax in Markdown:

![Child studying](child.jpg 'Credit: lorem ipsum')

If the image has a specific styling such as #float=left, you will need to specify title= before the image caption, for example;

                      style attribute(s)  image title / caption
                               ▼           ▼
![Child studying](child.jpg '#float=left;title=Image Title')
                                        ▲
                           Don't forget the separator   

Important: Make sure to separate each attributes with ; as shown above.

A few important notes:

1. Ensure that headings remain hierarchical, that is, don't use Heading 4 (#### Title) after Heading 2 (## Title), but use Heading 3 (### Title) instead.
2. Ensure that Heading 1 is used only for the post title. For other headings, start with Heading 2.
3. Every heading will be automatically hyperlinked, so that you can share the link of the post anchored to a specific heading. You can get this link by hovering over a specific heading, clicking the link icon on the left-hand side, and copy the URL on your browser.

Ensure that internal links (i.e. links pointing towards a URL within the same site) use relative path instead of absolute path. A relative path is essentially an absolute path without the protocol & hostname, i.e. https://www.fatherkenny.com. An example of relative path is as follows:

[Learn more](/about)

Whereas an absolute path is as follows:

[View on Facebook](https://www.facebook.com/)

A book component is a custom component where you can show an image of a book, with its title, description and link.

To use this component, you will need to copy and paste the following HTML code directly to your Markdown file:

<div class="book">
  <div class="book__img">
    <div class="book__img__inner">
      <img src="{image.jpg}" alt="{Image description}" />
    </div>
  </div>
  <div class="book__text">
    <h4>
      <a href="{/path/to/book}" target="_blank" rel="noopener noreferrer">
        {Book Title}
      </a>
    </h4>
    <h5>{Book metadata / author}</h5>
    <p>{Book description ...}</p>
  </div>
</div>

Note that you'll need to replace to contents wrapped by { } (including the curly brackets) in the example above.

You can also remove certain elements by removing the HTML opening & closing tags entirely. For example, if you don't want to include the Book metadata / author section:

<div class="book">
  <div class="book__img">
    <div class="book__img__inner">
      <img src="{image.jpg}" alt="{Image description}" />
    </div>
  </div>
  <div class="book__text">
    <h4>
      <a href="{/path/to/book}" target="_blank" rel="noopener noreferrer">
        {Book Title}
      </a>
    </h4>
    <p>{Book description ...}</p>
  </div>
</div>

All form submissions are logged in this Google Sheets.

All forms are protected by honeypot as the spam-prevention measure.

Let Kevin know if you notice that spam submissions successfully creep in.

Web Analytics are provided by Cloudflare. To view reports:

1. Log in to Cloudflare
2. Select your account (Kenny Ang)
3. Click Web Analytics on the right hand sidebar.
4. Click the site (fatherkenny.com) to view analytics.

1. Git Branches, Pull Requests, Preview URLs