From 427d056286043ff083b1d99bb85491869e510402 Mon Sep 17 00:00:00 2001 From: ray Date: Tue, 11 Feb 2020 15:25:44 +0000 Subject: [PATCH] initial draft complete --- content/posts/flowmm.md | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/content/posts/flowmm.md b/content/posts/flowmm.md index 2a79954..925625b 100644 --- a/content/posts/flowmm.md +++ b/content/posts/flowmm.md @@ -28,13 +28,13 @@ Instead of reloading an entire page, when maybe only one small component of the So, once the initial page is loaded, the amount of data that needs to be transmitted can be greatly reduced. This also has the benefit of an improved user experience. -Navigation and updates to the state of the site appear to be almost instant, similar to a native application, rather than lengthy page reloads typically associated with websites. +Navigation and updates to the state of the site appear to be almost instant, similar to a native application, rather than more lengthy page reloads typically associated with websites. **Vue.js** is a modern JavaScript framework for creating web interfaces. It makes use of the virtual DOM, is small and fast, and is an ideal foundation for an SPA. However, Vue along with other SPA frameworks do have some disadvantages. -The main disadvantage is regarding **Search Engine Optimisation**. +A major disadvantage is regarding **Search Engine Optimisation**. SPAs can require a relatively long initial page load, and aren't as efficiently crawled by search engine crawlers due to the heavy use of JavaScript. This means sites requiring SEO, need to take steps to mitigate these issues. @@ -44,12 +44,14 @@ The HTML can be quickly displayed by the client browser, reducing the initial pa This may be taken even further, if desired, so that *all* pages are rendered on the server. In effect, creating a static site. This will then bring all the benefits of a fast, easily indexable static site. -These, **Server Side Rendered** applications can require a lot of setting up +These, **Server Side Rendered** applications can require a lot of setting up. There are also a number of pitfalls and considerations that need to be kept in mind. -For example, as there are no requests for new pages, the browser history needs to be managed. -There are many threats of security vulnerabilities and exploits. -Although browser standards have improved over time, there are still a number of differences in behaviour between the many devices and browsers in use. +To name a few: + +* there are no requests for new pages and so the browser history needs to be managed, +* there are many threats of security vulnerabilities and exploits, +* although browser standards have improved over time, there are still a number of differences in behaviour between the many devices and browsers in use. This is where a framework such as **Nuxt.js** comes in. A lot of the tedious scaffolding is taken care of and being a fully tested, mature framework, we can be confident that many common, and not so common, issues have already been solved and tested for. @@ -68,7 +70,7 @@ simple. A visually appealing, elegant site, with some background information and to use method for applicants to sign up with. A monochromatic colour scheme was chosen. I felt that a primarily black and -white colour scheme that uses the brand colour of orange would give a classy and +white colour scheme that uses the brand colour of orange as an accent would give a classy and elegant feel to the site. **Montserrat** and **Lato** were the fonts chosen for the headings and body text respectively.