-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: seed docs script #231
base: main
Are you sure you want to change the base?
Conversation
Dependencies outside root package.json to resolve conflicts. Also the seed dependencies are not needed for other projects using Head Start. to do: - better link replacement in md files - add a partial listing all documents?
Deploying head-start with Cloudflare Pages
|
import { fromMarkdown } from 'mdast-util-from-markdown'; | ||
import type { Root } from 'mdast'; | ||
import { toHast } from 'mdast-util-to-hast'; | ||
import { hastToStructuredText, type HastRootNode } from 'datocms-html-to-structured-text'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Astro check in the CI lint job fails on this module. Not sure why it's not found. Locally I can verify it exists. Maybe it has to do with the "type": "commonjs"
in package.json
? But I can't change that to "module"
as then running DatoCMS migrations will fail 🤷 .
It's a bit of a non-issue. Astro check shouldn't even lint this file and just stick to src/
. But I'm unable to configure that. What I could do as a workaround is in the CI lint job, delete config/datocms/scripts/
before running npm run lint:astro
. What do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
patch available as PR: #241
Note
The functionality itself is ready. The only issue is a failing Astro check in the CI lint-code job. See comment. I could use some help resolving that issue.
Changes
docs/*.md
files.documentation
) and uses it as a parent page.Associated issue
Related to #27, though that issue is mainly about seeding required content.
How to test
npm run seed:docs
(you may want to switch to a new sandbox environment for this)./datocms-environment.ts
)Checklist
I have added a decision log entry if the change affects the architecture or changes a significant technology