The open graph meta tags allow better presentation when sharing a web page on social media. Also, adding this meta tags will improve SEO optimization of the page.

The basic meta tags are:

• og:title -> the title of the page, or the content itself, e.g.:
  <meta property="og:title" content="The Rock" />

• og:url -> canonical url of this page, e.g.:
  <meta property="og:url" content="http://www.imdb.com/title/tt0117500/" />

• og:image -> url of an image of 1:1 or 1.91:1 aspect radio, ranging from 600x315 to 1200x1200. This image file will be shown as a thumbnail when sharing the page on social media, e.g:
  <meta property="og:image" content="http://ia.media-imdb.com/images/rock.jpg" />

• og:type -> a list of possible types is available at http://ogp.me/#types. A first version of the implementation could limit this value to 'website' and 'article', e.g:

<meta property="og:type" content="article" />
<meta property="article:published_time" content="2018-04-19T19:56:45+00:00" /> <!-- date time in ISO 8601 format -->
<meta property="article:modified_time" content="2018-04-19T19:56:45+00:00" /> <!-- date time in ISO 8601 format -->
<meta property="article:section" content="Technology" />  <!-- we could assume upper level channel of this content -->
<meta property="article:tag" content="technology,3d printing,etc" />  <!-- a list of tags for this article -->

<meta property="og:type" content="website" /> <!-- Home page and non article pages could have only this type tag -->

Open graph validation could be made here: https://developers.facebook.com/tools/debug/

Schema.org is a standard to enhance websites with meta information. Search engines could read this information to automatically detect the content of a website.
One common form to write schema information is using JSON-LD format, where a script tag is inserted at the head tag of the page, like this:

<!-- Schema data -->
<script type="application/ld+json">
{
	"@context": "http://schema.org",
	"@type": "LegalService",
	"name": "Giane Marize Barroso",
	"url": "https://gmbarroso.adv.br",
	"image": "https://gmbarroso.adv.br/android-chrome-512x512.png",
	"contactPoint" : [
		{
			"@type" : "ContactPoint",
			"email" : "[email protected]",
			"telephone" : "+55 (11) 2847-4740",
			"contactType" : "customer service",
			"url": "https://gmbarroso.adv.br",
			"areaServed": ["BR"],
			"availableLanguage": ["Portuguese"]
		}
	]
}
</script>

A feature that allows the user to input a global JSON-LD tag content (as a string) will enhance SEO optimization for his/her website.
Due to the huge domain for schema.org, it would be almost impossible to insert JSON-LD in a form other than string.

When it has a folder with same name of alias, the alias doesn´t work.

I would like to suggest a site icon generation feature for Shiohara. Each browser handles site icon presentation its own way, therefore, its hard to manage all possibilities.

• The most common icon declaration are:

<link rel="shortcut icon" href="/favicon.ico" type="image/x-icon">
<link rel="icon" href="/favicon.ico" type="image/x-icon">

Where possible icon sizes are:
Recommended 16x16, 32x32, 48x48
Optimal 16x16, 24x24, 32x32, 64x64

• Android and iOS can use more hi-res images, since a webpage could be added to the phone or tablet home screen. Several formats can be found at official documentations:

<link rel="apple-touch-icon-precomposed" sizes="57x57" href="apple-touch-icon-57x57.png" />
<link rel="apple-touch-icon-precomposed" sizes="114x114" href="apple-touch-icon-114x114.png" />
<link rel="apple-touch-icon-precomposed" sizes="72x72" href="apple-touch-icon-72x72.png" />
<link rel="apple-touch-icon-precomposed" sizes="144x144" href="apple-touch-icon-144x144.png" />
<link rel="apple-touch-icon-precomposed" sizes="60x60" href="apple-touch-icon-60x60.png" />
<link rel="apple-touch-icon-precomposed" sizes="120x120" href="apple-touch-icon-120x120.png" />
<link rel="apple-touch-icon-precomposed" sizes="76x76" href="apple-touch-icon-76x76.png" />
<link rel="apple-touch-icon-precomposed" sizes="152x152" href="apple-touch-icon-152x152.png" />
<link rel="icon" type="image/png" href="favicon-196x196.png" sizes="196x196" />
<link rel="icon" type="image/png" href="favicon-96x96.png" sizes="96x96" />
<link rel="icon" type="image/png" href="favicon-32x32.png" sizes="32x32" />
<link rel="icon" type="image/png" href="favicon-16x16.png" sizes="16x16" />
<link rel="icon" type="image/png" href="favicon-128x128.png" sizes="128x128" />

• For Windows 8 and newer versions, an website could be pinned to the start menu. Custom meta tags are required for this functionality:

<meta name="msapplication-TileImage" content="mstile-144x144.png" />
<meta name="msapplication-square70x70logo" content="mstile-70x70.png" />
<meta name="msapplication-square150x150logo" content="mstile-150x150.png" />
<meta name="msapplication-square310x310logo" content="mstile-310x310.png" />

• In addition, for Windows 8 and newer versions, meta application-name will display the site's name on the tile, and also, its possible to choose a tile background color.
  In my opinion, a tile color select funcionality has low priority. Application name value could be the configurated site name at Shiohara's home screen:

<meta name="application-name" content=""/>
<meta name="msapplication-TileColor" content="#FFFFFF" />

To conclude, a single 310x310 image file could be used to generate a 64x64 .ico file and several png files according with the specs above. Also, the required link/meta tags could be generated automatically.
Developers usually rely on third-party applications to manage icon library and link/meta tags. It would be great if Shiohara had this functionality embedded to its core.