Resolve Next.js build warning and Contentlayer validation errors#559
Open
ericsandu wants to merge 2 commits into
Open
Resolve Next.js build warning and Contentlayer validation errors#559ericsandu wants to merge 2 commits into
ericsandu wants to merge 2 commits into
Conversation
Migrate assets from deprecated 'static/' to 'public/' and update contentlayer.config.ts for subdirectories and new document types. Signed-off-by: Eric Sandu <eric_andrei.sandu@stud.acs.upb.ro>
Convert frontmatter from TOML to YAML and add required fields (title, description, publishedDate, authors) to meet schema requirements. Signed-off-by: Eric Sandu <eric_andrei.sandu@stud.acs.upb.ro>
ericsandu
force-pushed
the
ericsandu/fix-contentlayer
branch
from
a71df81 to
991ee02
Compare
Contributor
Author
|
The linter errors seem to be caused by jscpd finding duplicate fields because of the YAML blocks used in the documentation files, due to the template sort of structure that is used in them. Should the documentation be left as is or updated to avoid identical phrasing across guides? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR fixes Next.js deprecation warnings and Contentlayer validation failures preventing site
builds for a couple .md.
Assets have been moved from
static/topublic/per Next.js standards.The Contentlayer has been configured to enabled recursive blog search (
**/blog/) and added anOthertype for root-level pages, fixing directory mismatch errors for some olderI've added the missing
enableTocto the schema which was found in two .md files (privacy.md,imprint.md)10 posts have also been converted from TOML to YAML and have had standardized required metadata added to them (
description,publishedDate,authors).