Fire Emblem: Fortune’s Weave review – VNHS Mirror

WHAT IT DOES. Three parts. The first script is the table:
each entry is keyed by the primary category slug that appears
in the story address (current-events, viewpoints, athletics,
packlife, entertainment, el-espejo, digital-media,
photo-gallery-2, games). word is the text to show, with a
vertical bar wherever the color should switch; the first
piece is red, the next gray, then red again, which is how
news|feed and arts|&|culture get their two tones. editor is
the name printed after Editor:, and page is where the word
links. To change an editor, change the name here; to add a
section, add an entry in the same shape. The style block
hides the header row this element sits in (the mirror-hdr
marker tells it which row), sets the word at 50px Montagu
Slab bold, red #ea1700 and gray #aeaeae with putty #a9a795 on
hover, and the editor line at 16px light white. On desktop
(980px and up) the label sits in the band at the left edge,
centered vertically; below 980px a second copy is placed
under the header instead. The last script does the work: it
reads the page address, pulls the category slug out of it (or
matches the address against the page entries when the reader
is on a section page, or takes the slug after /category/ on a
category archive page, the list the VIEW ALL button opens),
finds the band (the tallest header element without an image,
or whatever selector is set in MIRROR_LABELS_BAND), and
builds the label. If an older category-page widget has
already placed a label, the script moves that label into the
band instead of making a second one. It also loads the light
weight of Montagu Slab for the editor line. EDITOR NAME is a
placeholder waiting for a name.
============================================================ */

WHAT IT DOES. The SNO video element cannot carry bold tags in
its caption, so this does it after the page is built. The
first script is the settings: selectors is where to look
(.embed-caption is the video caption; add
.sno-story-photo-caption and .photocaption, separated by
commas, to treat photo captions the same way), marker is the
character that ends the lead-in, and maxChars is how far into
the caption that marker may be. The style block sets the
lead-in to weight 700, which has to be said outright because
captions are weight 200 and a plain bold tag inside a 200
would only reach 400. The last script looks at each caption,
and if a colon appears within the first 60 characters and is
followed by a space, wraps everything up to the colon in
bold. A colon inside a time such as 3:45 is skipped because
no space follows it; a caption with no colon, or one whose
colon comes later than 60 characters, is left alone.
============================================================ */

WHAT IT DOES. In the story the writer types the marker
{BROADCAST CREW} on its own line, then one crew member per
line as Name: Role, then {/BROADCAST CREW}. Curly braces, not
square ones: WordPress strips square-bracket tags before the
page goes out. Several people who share a role can go on one
line separated by commas, and each gets a row. After the
role, an optional vertical bar and a photo address supplies a
mugshot by hand, and a second bar and a web address makes the
name a link. The first script is the settings: tag is the
marker word, photoSize is the mugshot size in pixels, and
heading is the title printed above the rows; leave nothing
between its quotes to drop the title. The style block draws
the block the way the contributor box is drawn: a 1px #aeaeae
rule across the top with 15px under it, the heading in
Montagu Slab 800 at 24px in #aeaeae, then the rows at 13px
Work Sans with the name in 600 caps, the role in 300, a 45px
round photo and 1px #dbdbdb rules. The last script finds the
marker in the story text, turns the lines between the markers
into rows, and for each name asks the site for the staff
profile with exactly that title; when it finds one it uses
the profile photo and links the name and photo to the staff
page. A name with no staff profile shows white initials in a
dark circle and no link. The markers are read without regard
to case, and if the closing marker is missing only the
paragraph that holds the opening marker is used, so nothing
below it is swallowed.
============================================================ */

WHAT IT DOES. SNO prints the contributor photo first and the
name inside the text column, which CSS alone cannot reorder.
This script finds each contributor block on a story page and
moves the photo to sit right after the name line. Section 6
of the custom CSS does the rest: it floats the photo left at
five lines of text deep and lets the bio wrap beside and
under it. Each block is marked once it has been moved so the
script never moves it twice. If this script is removed, the
box still works; the photo simply sits beside the name
instead of under it.
============================================================ */

WHAT IT DOES. The SNO related-story element prints a photo and
a headline, and a teaser only when the element was built with
one. This block looks at every related-story block in the
story body. If the block already holds a teaser it is left
alone. Otherwise, for each headline in the block, the script
reads the story number out of the headline link (the number
in the web address, such as 233193), asks the site for the
teaser of that story, cleans it (tags removed, the bracketed
dots WordPress adds removed, cut to the word limit with three
periods added if it ran long) and writes it in as a paragraph
with the class relatedteaser, the same class SNO uses, so the
custom CSS styles both the same way. The settings line has
one number, words, the most words a teaser may run; a custom
teaser of 30 to 45 words is never cut. A block whose headline
link has no story number, or whose story cannot be read, is
left as it was.
============================================================ */

WHAT IT DOES. SNO prints poll results in the order the writer
typed the choices, with a share after each one, such as 42
percent and 10 votes in parentheses, and a bar under it. It
does not sort them or say which choice is ahead. This block
watches every poll box on the page. Each time SNO writes or
changes the results, the script reads the vote count (and the
share) in each row, moves the rows so the most votes come
first, and puts the class mirror-poll-top on the first row
(and takes it off the others). The custom CSS reads that
class and sets the choice in bold. Rows are moved only when
their order has to change, and the Vote button stays below
them. Before a vote no row has results, so the choices stay
in the order the writer gave them and nothing is marked; a
tie keeps the order the writer gave. The settings line has
one value, cls, the class name, which has to match the name
used in section 26 of the custom CSS.
============================================================ */

WHAT IT DOES. In the story the writer types {TRANSCRIPT} on
its own line where the transcript starts (after the lead
paragraphs, so they keep the story font) and {/TRANSCRIPT}
on its own line where it ends. Curly braces, as with the
crew tag. The script finds the tag, removes it from the
page, and wraps everything between the two tags in a box
with the class mirror-transcript, which the custom CSS
styles. If the closing tag is missing, the box runs to the
end of the story text and stops at the first story element
(a photo, video, pull quote and so on), so nothing else is
swallowed. Inside the box it also looks at the start of
every line: when a line begins with a speaker name and a
colon, after an optional time stamp in square brackets, and
the name is not bold yet, the script makes it bold and gives
it the same color as the other names in that transcript. A
speaker name is up to four words, either all capitals
(TACHIN, NIA TACHIN) or each word capitalized (Nia Tachin).
The tag is read without regard to case. The settings line
has two values: tag is the tag word, and boldNames set to
false turns off the automatic bolding.
============================================================ */

WHAT IT DOES. Two jobs. First, on a section page (viewpoints,
athletics, packLIFE, arts and culture, el espejo, broadcasts,
multimedia, newsfeed) the script looks the page address up in
the H1 table above, which already pairs each section page
with its category, and adds a link after the last row of
widgets pointing at /category/ followed by that category, the
page that lists every story in it. The button wording comes
from the H1 table too, so the viewpoints page reads VIEW ALL
VIEWPOINTS CONTENT and the arts page VIEW ALL ARTS & CULTURE
CONTENT. A new section page needs only an H1 entry to get its
button. Second, wherever a story list widget already shows
SNO’s own ‘view all’ link, the script rewrites those two words
the same way, using the category in the link address. If a
page already has a widget link, no page button is added, so
there is never a pair. Category archive pages get no button,
since it would point back at the page itself. The settings
line has four values. text is the wording, with {name}
standing for the category name. names overrides the name for
a category, for example names:{‘current-events’:’NEWSFEED’}.
pages ties a page address to a category when the page is not
in the H1 table, for example pages:{‘/sports/’:’athletics’}.
addButton set to false turns off the page button and leaves
only the rewording of widget links.
============================================================ */

WHAT IT DOES. The script reads the story number from the page
(the snopostid class SNO puts on the story body), asks the site
for that story through the WordPress REST interface at
/wp-json/, takes its first tag, then asks for the newest
stories with that tag published in the past 365 days, leaving
out the current story and every story linked from a related
story element in the story body (it reads the story numbers out
of those links, so a story a reader has already been offered is
not offered twice; the list refills with the next newest
story), and writes a box: the heading, linked to the tag page,
and one card per story with the thumbnail first (the medium
size of the featured image, which section 31 shows as an 85px
square), then the headline, then the date as Nov 6, 2026. No
byline and no teaser; the teaser setting turns one on, and then
the WordPress excerpt follows the date, with its tags and
trailing dots stripped and cut at a word near teaserMax
characters. Where the box goes, in order: if the page has an
element with the id mirror-tag-stories, the box fills it (that
is the one line of HTML for a Custom HTML widget, and H9 hides
that widget title and writes its own heading); otherwise, if
the story has a sidebar that is showing (SNO hides it on
phones), the box goes in at the top of the sidebar, above the
widgets already there; otherwise it goes directly under the
story text, above the comment bar. SNO story list widgets
cannot take the placeholder and cannot read the tag of the
story a reader is on, so a widget made to do this job should be
removed or replaced with the Custom HTML widget; section 31
hides any SNO story list widget left in the story sidebar. A
story with no tag, or a tag with no other stories inside the
year, gets no box, and a widget holding the empty placeholder
is hidden. The settings line has nine values: text is the
heading, with {tag} standing for the tag name, printed in
lowercase; count is how many stories; maxDays is how far back
to look, 365 for a year; teaser set to true adds the teaser
under the date; teaserMax is the teaser length in characters;
skipRelated set to false lets related story element stories
back into the list; placeholder is the id to look for; sidebar
set to false keeps the box out of the sidebar; auto set to
false stops the script from placing the box itself when no
placeholder exists. The widget line to paste is a div with id
mirror-tag-stories and nothing inside it.
============================================================ */