Skip to content
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

Path to Docusaurus 3 #4560

Draft
wants to merge 9 commits into
base: main
Choose a base branch
from
Draft

Path to Docusaurus 3 #4560

wants to merge 9 commits into from

Conversation

akeller
Copy link
Member

@akeller akeller commented Nov 1, 2024

Description

This is my mess. You can join me here, or tackle things piecemeal. Related to #2719.

When should this change go live?

  • This is a bug fix, security concern, or something that needs urgent release support.
  • This is already available but undocumented and should be released within a week.
  • This on a specific schedule and the assignee will coordinate a release with the DevEx team. (apply hold label or convert to draft PR)
  • This is part of a scheduled alpha or minor. (apply alpha or minor label)
  • There is no urgency with this change and can be released at any time.

PR Checklist

  • My changes are for an already released minor and are in /versioned_docs directory.
  • My changes are for the next minor and are in /docs directory (aka /next/).

@akeller akeller added the d3 Path to Docusaurus 3 label Nov 1, 2024
@akeller akeller self-assigned this Nov 1, 2024
Copy link
Contributor

github-actions bot commented Nov 1, 2024

👋 🤖 🤔 Hello! Did you make your changes in all the right places?

These files were changed only in docs/. You might want to duplicate these changes in versioned_docs/version-8.6/.

  • docs/self-managed/modeler/web-modeler/configuration/configuration.md

You may have done this intentionally, but we wanted to point it out in case you didn't. You can read more about the versioning within our docs in our documentation guidelines.

@akeller
Copy link
Member Author

akeller commented Nov 4, 2024

In the API spec .mdx files, it looks like <div>'s are opened but not closed.

Error: MDX compilation failed for file "/Users/amara/Projects/post-86/camunda-docs/versioned_docs/version-8.6/apis-tools/zeebe-api-rest/specifications/unassign-a-user-task.api.mdx"
Cause: Expected a closing tag for <div> (39:548-39:553) before the end of paragraph
Details:
{
"column": 1,
"message": "Expected a closing tag for <div> (39:548-39:553) before the end of paragraph",
"line": 39,
"name": "39:1-39:553",
"place": {
"start": {
"line": 39,
"column": 1,
"offset": 2630,
"_index": 0,
"_bufferIndex": 0
},
"end": {
"line": 39,
"column": 553,
"offset": 3182,
"_index": 1,
"_bufferIndex": -1
}
},
"reason": "Expected a closing tag for <div> (39:548-39:553) before the end of paragraph",
"ruleId": "end-tag-mismatch",
"source": "mdast-util-mdx-jsx"
}

This was referenced Nov 4, 2024
@@ -70,7 +70,7 @@
"jest": "^29.6.4",
"lint-staged": "^14.0.1",
"playwright": "^1.32.2",
"prettier": "3.0.0",
"prettier": "2.8.8",
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Apparently, prettier went to the past...

@akeller akeller mentioned this pull request Nov 5, 2024
9 tasks
@akeller
Copy link
Member Author

akeller commented Nov 6, 2024

The deploy tag produces a different issue, the version of Node is old. That's not what I get on my local machine, instead I experience this:

Screen.Recording.2024-11-06.at.2.17.17.PM.mov

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
d3 Path to Docusaurus 3
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant