pnpm refuses a git dependency inside another package by default
(blockExoticSubdeps), so an app could not install v0.8.0. vue-seo-layer
is now a peer dependency (^0.2.0) and a development dependency pinned
to v0.2.0; apps list vue-seo-layer#v0.2.0 next to the layer.
- package.json version 0.8.0, README install line #v0.8.0 (L4 CR-01)
- Upgrading from 0.7: the HTML sitemap pages, the catch-all rule and
seo.htmlSitemap.overCatchAll (L4 WR-04), the post page's article meta
and the path-form listing segments
- the link:../vue-seo-layer dependency stays until the release swap
- post, index, category, tag and author pages render <SeoBreadcrumbs>
at the top of their content while journal.breadcrumbs is on (default);
false leaves the trail to the site's layout, the BreadcrumbList data
is unchanged
- JournalPagination renders <SeoPagination class-prefix="journal-pagination">
with the journal's labels: the same class names, plus page 1, the last
page, gap items, aria labels and head rel prev/next, with links in the
CMS's pagination form
- with vue-seo-layer's seo.pagination.form 'path' the module registers
<listing>/<segment>/:page routes (journalPagedRoutes), and the listing
pages read the page from the :page param or ?page (pageFromRoute)
- the category pillar text renders on page 1 only, the description on
every page; an h1 in it becomes h2 while the category row's
content_h1_to_h2 is on (absent counts as on)
- JournalPostCard: the title link is the card's only anchor; the image is
no longer a link and the separate read-more link is gone; the whole card
stays clickable through a CSS stretched link with the focus ring on the
card; prop headingLevel (2 | 3, default 2)
- related posts keep their h2 and render their cards at h3; JournalPostList
passes headingLevel through
- smoke checks headings=strict (one h1, no skipped level) and cardlinks=N
on every fixture page; expectation files for postTitleTag forced to h1
and p (the documented two-h1 and no-h1 consequences)
BREAKING CHANGE: .journal-post-card__more and the image link
(.journal-post-card__image is now a div) are removed from post cards.
- renderJournalBody runs the UI-SPEC L7 order on the sanitized body:
h1 demotion, the CMS phrase auto-links, the outbound rules and lazy,
async images, with vue-seo-layer's autolink, applyOutbound and
imageAttrs; PostBody feeds it the page's resolve answer (autolinks,
autolink_max, outbound, url) and the seo.links.newTabHint option
- the sanitizer keeps a link rel of only nofollow, sponsored and ugc
(the Blog Editor's link form, as the Journal plugin's policy does);
target is never kept, the outbound rules add it
- editor-corpus.json copied again from sm-journal-plugin (link-rel and
image-decorative entries)
- smoke:ssr script; expectations for auto-links, both new-tab modes and
the hint switched off
- extend vue-seo-layer (link dependency during development) and drop
@nuxtjs/seo: the page head, canonical and the one JSON-LD graph come
from the CMS resolve answer; the post's own title, excerpt and image
apply only while there is no CMS answer
- remove the journal sitemap source and the copied shared purge route,
library and plugin (the SEO layer serves POST /api/__site__/cache/purge);
the deprecated POST /api/__journal__/cache/purge keeps working
- post title is h1 while the Journal API reports content_h1_to_h2 on
(or absent) and p.journal-post__title while off; journal.postTitleTag
('auto' | 'h1' | 'p') overrides it; body h1 headings are demoted to h2
while the setting is on (gateJournalHtml/sanitizeJournalHtml demoteH1)
- journal.breadcrumbs option and post-title CSS tokens
- smoke harness: count=, header=, noheader= and resolves lines; the
fixture API also answers the SEO resolve and site endpoints
BREAKING CHANGE: the layer no longer installs @nuxtjs/seo (no
nuxt-site-config, nuxt-schema-org, robots or sitemap module, no
/api/__sitemap__/journal source, no useSiteConfig()); apps take their
head, sitemaps and robots from the SEO plugin through vue-seo-layer.
- journal.routes.search (off by default) registers journal-search, the
results page for ?q= in the API's relevance order (no sort is sent),
server-rendered with a Polish-aware result count.
- JournalSearchBox: an icon button and a WAI-ARIA combobox with debounced
?fields=suggest suggestions, stale answers dropped, query words marked
ignoring diacritics; a plain GET form without JS.
- The module keeps the search path out of the route cache and the sitemap
and marks it noindex, follow.
- Client: suggestPosts and the fields option; useJournalLinks.searchLink.
nuxt-site-config copies every NUXT_SITE_* variable into the public site
config, so NUXT_SITE_CACHE_PURGE_TOKEN reached every page's payload as
cachePurgeToken (and NUXT_SITE_CACHE_ALLOW_PROXIED as cacheAllowProxied).
- The purge settings move to runtimeConfig cachePurge.token
(NUXT_CACHE_PURGE_TOKEN) and cachePurge.allowProxied
(NUXT_CACHE_PURGE_ALLOW_PROXIED), outside that prefix.
- The old siteCache.* names keep working for one release: a non-empty
new token wins, either allowProxied flag turns it on, and one
deprecation warning per process names the variables (never a value).
- The shared Nitro plugin server/plugins/site-cache-purge.ts strips
cachePurgeToken and cacheAllowProxied from nuxt-site-config's stack on
site-config:init, so a site on the old names leaks nothing either; it
does nothing without nuxt-site-config.
- The shared lib, route and plugin and tests/sitePurge.test.ts are
byte-identical in vue-journal-layer, vue-menu-layer and vue-faq-layer,
with three sha256 pins.
- README: new names, the deprecation, the stripping and the advice to
rotate a token ever set under the old name.
- runtimeConfig.siteCache.allowProxied (NUXT_SITE_CACHE_ALLOW_PROXIED, default
false) lets the shared purge route accept a request that came through a
TLS-terminating proxy; the bearer token is then the only gate
- shared lib, route and spec stay byte-identical across the three layers,
with updated sha256 pins and two new sitePurge specs
- version 0.5.0
- server/lib/siteCachePurge.ts and the route, byte for byte from
vue-faq-layer (sha256 pinned in tests/sitePurge.test.ts)
- runtimeConfig.siteCache.purgeToken (NUXT_SITE_CACHE_PURGE_TOKEN) and the
'/api/__site__/**': { cache: false } route rule
- /api/__journal__/cache/purge, app/utils/siteCache.ts and
journal.cachePurgeToken unchanged, documented as aliases for one release
- version 0.4.0
- node --test over routes, client (fake fetcher, include_empty=1),
pagination, htmlGate (Go FormatHTML parity cases), sitemap, seo and
pl/en i18n parity
- package script test and a Testing line in the README
- author pages resolve slug or login and canonicalise to the slug
- tag pages, per-page SEO meta and canonicals that keep ?page=N
- sitemap source pages the API and builds locs from journal.routes
- /rss.xml proxies the API feed with x-forwarded-for
- neutral README; version 0.1.0
- journal module registers the Journal pages at journal.routes paths
- typed anonymous-GET client, html gate, SSR x-forwarded-for forwarding
- fixture API, built-server SSR smoke and git-tag install check
