feat: update firebase post; update site description

This commit is contained in:
Ayo Ayco 2021-06-26 01:37:23 +08:00
parent 53f3c712f3
commit 6d9d1d0bcc
4 changed files with 8 additions and 12 deletions

View file

@ -13,16 +13,15 @@
# you will see them accessed via {{ site.title }}, {{ site.email }}, and so on.
# You can create any custom variable you would like, and they will be accessible
# in the templates via {{ site.myvariable }}.
title: "Ayos Blog"
title: Ayos Blog
description: Blogs on life and personal growth
author: Ayo
attribution: "Ayo Ayco"
attribution: Ayo Ayco
attribution-url: "https://AyoAyco.com"
bugreport_url: "https://github.com/fullhacker/blog/issues/new"
google_analytics: "UA-113797180-1"
website: blog.ayoayco.com
email: ramon.aycojr+blog@gmail.com
description: >- # this means to ignore newlines until "baseurl:"
// notes on technology and life
baseurl: "/" # the subpath of your site, e.g. /blog
url: "https://blog.ayoayco.com" # the base hostname & protocol for your site, e.g. http://example.com
twitter_username: ayoayco

View file

@ -83,7 +83,7 @@
<div class="ayo-thumb">
<img src="../assets/images/ayo.jpg" alt="Free exclusive web development tips!" />
</div>
<h2>Blogs on life and personal growth.</h2>
<h2>{{ site.description }}</h2>
<!--p>Learn how to use the best and latest web applications and technologies to boost your productivity.</p-->
<p>Want to give me a tip?</p>
<!--div class="post-readmore"><a target="_blank" class="button" href="https://docs.google.com/forms/d/e/1FAIpQLScinfuT_8-4q5Yk16nGUMxWxVpQgWZwyAaJ5oFY5_0NsRMjMw/viewform?usp=sf_link">Get FREE Consultation</a></div-->

View file

@ -12,7 +12,7 @@ I didn't really expect it to be so hard but, to my surprise, the sheer number of
In this post, let's go through my considerations for choosing the backend tech for my future projects and why I eventually chose Google Firebase.<!--more-->
## My Considerations for Choosing the Backend Tech For My Future Projects
## Considerations for Choosing Backend Tech For My Future Projects
I understand that not all apps will have the same requirements but since it doesn't make sense to have a monolithic architecture for most modern web projects today, I always make sure that my projects have a backend that is separate and is accessed by frontend client apps through APIs.
@ -20,7 +20,7 @@ To guide in our decision, let's list some things we actually want our backend to
**1. Authentication** - We want users to easily be able to get access to our app without sacrificing security. Having integration with third-party providers is ideal especially for users who do not want to sign up to yet another system.
**2. Database** - We want a database system that is flexible in data structures and is capable of handling real time transactions, as we expect growth in the number of active users doing huge numbers of transactions daily.
**2. Database** - We want a database system that is flexible in data structures and is capable of handling real time transactions, as we expect growth in the number of active users doing huge numbers of transactions daily.
**3. Serverless Cloud Functions** - We want to save time in operations by not having to worry about setting up and maintaining servers for the backend
@ -38,7 +38,7 @@ I want to make it clear that I am not paid in anyway to promote Google Firebase.
### 1. Authentication
In Firebase, authentication is a breeze with many (and I mean *many*) providers for logging in such as Facebook, Google, Twitter, and others.
In Firebase, authentication is a breeze with many (and I mean _many_) providers for logging in such as Facebook, Google, Twitter, and others.
<div class="embed-container">
<iframe width="560" height="315" src="https://www.youtube.com/embed/8sGY55yxicA" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
@ -68,7 +68,7 @@ With **Cloud Firestore** as the database, flexibility and scaling is never a pro
### 4. Low Cost
Lastly, I find the [Firebase pricing plans](https://firebase.google.com/pricing) are very reasonable. I am sure the free tier covers a lot of my needs, and I don't have to worry about testing prototypes. I even think *some* light-weight production apps may work with the free tier.
Lastly, I find the [Firebase pricing plans](https://firebase.google.com/pricing) are very reasonable. I am sure the free tier covers a lot of my needs, and I don't have to worry about testing prototypes. I even think _some_ light-weight production apps may work with the free tier.
## Summary

View file

@ -535,14 +535,11 @@ table.image caption {
--x-height-multiplier: 0.342;
--baseline-multiplier: 0.22;
font-family: "Source Serif Pro", serif;
letter-spacing: -0.02em;
font-weight: 900;
font-style: normal;
letter-spacing: 0;
font-size: 56px;
margin: 10px 0 10px -2.63px;
line-height: 1.04;
letter-spacing: -0.015em;
padding-top: 5px !important;
}
&__description {