From b96ea4a217e1d3756f55744b8f6c0533ec9d0427 Mon Sep 17 00:00:00 2001 From: Deon George Date: Sat, 1 Oct 2022 10:57:16 +1000 Subject: [PATCH] Home page updates with benefits --- public/custom.css | 7 +- resources/views/home.blade.php | 106 +++++++++++++++++++++++++- resources/views/layouts/app.blade.php | 32 ++++---- 3 files changed, 127 insertions(+), 18 deletions(-) diff --git a/public/custom.css b/public/custom.css index d7f3ebd..47c1740 100644 --- a/public/custom.css +++ b/public/custom.css @@ -1,13 +1,16 @@ .theme-bg-primary { - background: #007CC3; + background: #007cc3; } +.item-icon { + color: #007cc3 !important; +} .site-logo { text-align: center; width: 5em; } .navbar-brand { - background: #007CC3; + background: #007cc3; border-radius: 10px; display: block; } diff --git a/resources/views/home.blade.php b/resources/views/home.blade.php index fc13b61..ce4c446 100644 --- a/resources/views/home.blade.php +++ b/resources/views/home.blade.php @@ -31,6 +31,110 @@ @endsection +@section('benefits-content') +

SQRL Benefits

+
+

SQRL solves an annoying situation that occurs with traditional usernames and passwords. Below is a list of a few of those benefits - both for end users and website owners.

+
+
+
+
+
+
+

No Passwords

+
+
+
+

SQRL presents a public key, that can only be generated by you to login.

+

Yes the service provider needs to first register you (with that public key), but once done, you can login everytime using it, since only you can generated it.

+
+
+
+ +
+
+
+
+

No User Names

+
+
+
+ With SQRL, as a user you no longer need to remember the username you used to login to a website. Nor do you have to think of one, if the one you wanted is already taken. +
+
+
+ +
+
+
+
+

No Private Details

+
+
+
+

When registering with websites, you dont need to use any of your private details (eg: your email address or parts of your name) as part of the authentication process.

+

The website owner will probably still want your email address to send you emails, but that can now be stored privately and securely at the backend.

+
+
+
+ +
+
+
+
+

Credentials Public

+
+
+
+

SQRL uses public/private key algorithms, and as a result, the public portion is truly public.

+

You can show you public key to anybody - and yes it is different for every site that you login - but they cannot use it to login as you.

+
+
+
+ +
+
+
+
+

User Managed

+
+
+
+

You no longer need to wait to receive, or think about creating a username to login to a website. So no more this username is already used, think of another!

+
+
+
+ +
+
+
+
+

Compromised Sites

+
+
+
+

If a website is compromised, and the hacker obtains the website authentication files, then the details in those files is completely useless.

+

If you own that website, you dont need to do any remediation actions on the lots credentials, you just need to worry about what else they were able to obtain.

+

If you are a user, then you dont need to go through the process of changing your password, as you dont have one!

+
+
+
+ +
+
+
+
+

No Forgotten Passwords

+
+
+
+

There is no longer I forgot my password, nor what email address did I use for this website?

+
+
+
+
+@endsection + @section('page-scripts') -@append +@append \ No newline at end of file diff --git a/resources/views/layouts/app.blade.php b/resources/views/layouts/app.blade.php index 76b4400..b324112 100644 --- a/resources/views/layouts/app.blade.php +++ b/resources/views/layouts/app.blade.php @@ -6,22 +6,8 @@ @includeIf('layouts.partials.header') -
-
- @includeIf('layouts.partials.hero') -
-
- - {{-- -
-
- @includeIf('layouts.partials.benefits') -
-
- --}} -
-
+

@yield('contentheader_title', 'Content Title')

@@ -30,13 +16,29 @@
+ {{-- +
+
+ @includeIf('layouts.partials.hero') +
+
+ --}} + +
+
+ @yield('benefits-content') +
+
+ {{--
@includeIf('layouts.partials.audience')
+ --}} + {{--
@includeIf('layouts.partials.lead')