DVSiteSeo class

What dartvel.seo said about the site as a whole, carried in the manifest so a server can use it.

A build reads the pubspec and writes these into the shell's head. A server then renders a route over that shell, and dvSeoApply replaces the whole marked block -- so anything the render is not given is not merely left alone, it is removed. Without this the web-server target served every page with no description, no image and no site name, which is worse than the shell it started from and looks fine in a browser.

These are a floor, not an override. A page that resolved its own description keeps it; a page that resolved nothing falls back here rather than to nothing.

Constructors

DVSiteSeo({String? name, String? description, String? image})
const

Properties

description → String?
final
hashCode → int
The hash code for this object.
no setterinherited
image → String?
Relative is fine; it is made absolute against the site's URL where it is written, because a link preview fetches it with no base.
final
isEmpty → bool
no setter
name → String?
og:site_name -- the site, not the page. Distinct from the shell's <title>, which is the homepage's title and only looks like a name.
final
runtimeType → Type
A representation of the runtime type of the object.
no setterinherited

Methods

noSuchMethod(Invocation invocation) → dynamic
Invoked when a nonexistent method or property is accessed.
inherited
toJson() → Map<String, Object?>
toString() → String
A string representation of this object.
inherited

Operators

operator ==(Object other) → bool
The equality operator.
inherited

Static Methods

parse(Object? section) → DVSiteSeo