Re-check H1,H2,H3 order

Author: olaru

src/App/templates/app/index.html.twig

@@ -312,7 +312,7 @@
                     {% for post in posts %}
                         <a class="post-card" href="{{ url('page::blog-resource', {categorySlug: post.category.slug, slug: post.slug}) }}">
                             <div class="post-date">{{ post.postDate|date('M d, Y') }}</div>
-                            <h4>{{ post.title }}</h4>
+                            <h3>{{ post.title }}</h3>
                             <p>{{ post.excerpt }}</p>
                             <span class="read-more">Read more →</span>
                         </a>

src/App/templates/error/404.html.twig

@@ -6,8 +6,7 @@
 {% block content %}
     <div class="page-intro home-intro error-messages">
         <div class="container">
-            <h2>Oops!</h2>
-            <h2>This is awkward.</h2>
+            <span class="eyebrow">Oops! This is awkward.</span>
             <h1>404</h1>
             <p class="text-dark">
                 You are looking for something that doesn't exist or may have moved. Check out one of the links on this page

src/App/templates/error/error.html.twig

@@ -6,8 +6,7 @@
 {% block content %}
     <div class="page-intro home-intro error-messages">
         <div class="container">
-            <h2>Oops!</h2>
-            <h2>This is awkward.</h2>
+            <span class="eyebrow">Oops! This is awkward.</span>
             <h1>{{ status }}</h1>
             <h2 class="message">{{ reason }}</h2>
         </div>

src/App/templates/partial/meta.html.twig

@@ -9,7 +9,7 @@
     <meta property="og:image"        content="{{ meta.image ?? app.meta.image }}"/>
     <meta property="og:type"         content="{{ meta.type ?? app.meta.type }}"/>
     <meta property="og:site_name"    content="{{ app.meta.siteName }}"/>
-    <meta property="og:url"          content="{{ meta.url ?? app.meta.url }}"/>
+    <meta property="og:url"          content="{{ meta.url ?? url(routeName ?? null) }}"/>
     <meta property="og:locale"       content="{{ app.meta.locale }}"/>
 
     <meta name="twitter:card"        content="{{ app.meta.twitterCard }}"/>

src/Blog/templates/page/author-resource.html.twig

@@ -42,7 +42,7 @@
                                 <path d="M14 4v6h6"/>
                             </svg>
                             <span class="post-card-kicker">{{ post.category.name }}</span>
-                            <h4>{{ post.title }}</h4>
+                            <h2>{{ post.title }}</h2>
                             <p>{{ post.excerpt|length > 200 ? post.excerpt|slice(0, 200)|trim ~ '…' : post.excerpt }}</p>
                             <span class="post-card-meta">{{ post.postDate|date('M d, Y') }}</span>
                             <span class="read-more">Read more →</span>

src/Blog/templates/page/blog-resource/architecture/request-lifecycle-for-a-mezzio-based-application.html.twig

@@ -30,7 +30,7 @@
 
             <article class="article">
                 <div class="entry">
-<h3>Seamlessly Interconnected Middleware for Enterprise-Level Solutions</h3>
+<h2>Seamlessly Interconnected Middleware for Enterprise-Level Solutions</h2>
 
 <p class="mb-3">The request lifecycle is the sequence of steps that happen from the moment a user makes an HTTP request until the server sends back a response. </p>
 

src/Blog/templates/page/blog-resource/best-practice/svn-keywords-setup-in-php-ide-zend-studio.html.twig

@@ -62,7 +62,7 @@ cache
 <pre><strong>Name:</strong> bugtraq:url
 <strong>Propriety:</strong> http://www.dotkernel.net/view.php?id=%BUGID%</pre>
 For <strong>above</strong> Proprieties , apply <strong>only</strong> to project folder, <strong>NOT</strong> recursive
-<h3>Final step( below instructions are good <strong>only</strong> for <strong>svn:keywords</strong> )</h3>
+<h2>Final step( below instructions are good <strong>only</strong> for <strong>svn:keywords</strong> )</h2>
 &nbsp;
 
 Check the <strong>Apply property recursively to:</strong>

src/Blog/templates/page/blog-resource/dotkernel-api/content-negotiation-in-dotkernel-rest-api.html.twig

@@ -30,7 +30,7 @@
 
             <article class="article">
                 <div class="entry">
-<h1></h1>
+<h2></h2>
 
 <p class="mb-3">Content negotiation is an important aspect of RESTful APIs to make it possible for diverse systems to work seamlessly together. It's based on enabling clients and servers to agree on the format and language of data they exchange.</p>
 
@@ -75,7 +75,7 @@
 <li>or <strong>resource URI patterns</strong>.</li>
 </ul>
 
-<h4><a href="#http-request-headers"></a>HTTP Request Headers</h4>
+<h3><a href="#http-request-headers"></a>HTTP Request Headers</h3>
 
 <p class="mb-3">The HTTP request headers <code>Content-Type</code> and <code>Accept</code> are used to determine the data format that will be sent in the request and the response. There are several types to choose from. Here are some examples:</p>
 
@@ -99,7 +99,7 @@ Accept: application/json</pre>
 
 <p class="mb-3">If the <code>Accept</code> header is not present, the server gets to decide the format of the response.</p>
 
-<h4><a href="#content-negotiation-using-url-patterns"></a>Content Negotiation using URL Patterns</h4>
+<h3><a href="#content-negotiation-using-url-patterns"></a>Content Negotiation using URL Patterns</h3>
 
 <p class="mb-3">Below are a couple of ways to communicate a preferred data format.</p>
 

src/Blog/templates/page/blog-resource/dotkernel-api/dotkernel-api-1-0-0-released.html.twig

@@ -33,12 +33,12 @@
 <blockquote><p class="mb-3">Dotkernel API has come a long way since this post was created. <a href="https://www.dotkernel.com/headless-platform/version-7-adds-postgresql-native-uuid-and-php-8-5/" data-type="link" data-id="https://www.dotkernel.com/headless-platform/version-7-adds-postgresql-native-uuid-and-php-8-5/">Check out the newest version of Dotkernel API</a> to stay up to date with the latest functional and security features.</p>
 </blockquote>
 
-<h4><a href="https://github.com/dotkernel/api/releases/tag/v1.0.0">DotKernel API 1.0.0</a> was just released!</h4>
+<h2><a href="https://github.com/dotkernel/api/releases/tag/v1.0.0">DotKernel API 1.0.0</a> was just released!</h2>
 <p class="mb-3"> </p>
-<h5>What is DotKernel API?</h5>
+<h3>What is DotKernel API?</h3>
 <p class="mb-3">It is a <a href="https://github.com/zendframework/zend-expressive">Zend Expressive 3</a> application aiming to help developers quickly and efficiently develop an API.</p>
 <p class="mb-3"> </p>
-<h5>How does it work?</h5>
+<h3>How does it work?</h3>
 <p class="mb-3">Under the hood it uses the following libraries:</p>
 <ul>
 <li><a href="https://github.com/ezimuel/zend-expressive-api">ezimuel/zend-expressive-api</a>: - skeleton application on which this API is based on</li>
@@ -54,7 +54,7 @@
 <li><a href="https://github.com/swagger-api/swagger-ui">swagger-api/swagger-ui</a>: ^3.22 - for creating OpenAPI 3 documentation</li>
 </ul>
 <p class="mb-3"> </p>
-<h5>What does it offer?</h5>
+<h3>What does it offer?</h3>
 <p class="mb-3">Out-of-the-box, DotKernel API provides the following features:</p>
 <ul>
 <li>Secure authentication via OAuth2</li>

src/Blog/templates/page/blog-resource/dotkernel-api/dotkernel-api-client-side-authorization.html.twig

@@ -32,7 +32,7 @@
                 <div class="entry">
 <strong>This article covers the basic authorization of a Client application which use a backend built using </strong><a href="https://github.com/dotkernel/api" target="_blank" rel="noopener noreferrer"><strong>DotKernel API</strong></a>
 
-<h3>Authorization Request</h3>
+<h2>Authorization Request</h2>
 Client application users send a <strong>POST</strong> request to the backend containing the following JSON object:
 <pre>
 {
@@ -45,7 +45,7 @@ Client application users send a <strong>POST</strong> request to the backend con
 }
 </pre>
 
-<h3>Authorization Response</h3>
+<h2>Authorization Response</h2>
 If the credentials are correct, the <strong>API</strong> will return a <strong>JSON</strong> object containing the authentication data:
 <pre>
 {