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

Make website components used in MDX files globally available #19036

Closed
tesseralis opened this issue Oct 26, 2019 · 2 comments · Fixed by #20685
Closed

Make website components used in MDX files globally available #19036

tesseralis opened this issue Oct 26, 2019 · 2 comments · Fixed by #20685
Assignees
Labels
help wanted Issue with a clear description that the community can help with.

Comments

@tesseralis
Copy link
Contributor

tesseralis commented Oct 26, 2019

Summary

Make website components used in MDX files globally available through gatsby-plugin-theme-ui.

Motivation

The only way to import components in MDX is to use relative paths, which breaks when pulling in content from translation repos.

Components to make global

  • LayerModel
  • HorizontalNavList
  • EmailCaptureForm
  • APIReference

In addition, there are several components imported in contributing/docs-and-website-components.md which are only ever used as a demonstration that they can be imported. This isn't as high priority. There's also the examples in the "data-fetching" page.

Already globally available

  • GuideList
  • EggheadEmbed

Related Issues

@gatsbot gatsbot bot added the type: question or discussion Issue discussing or asking a question about Gatsby label Oct 26, 2019
@tesseralis tesseralis changed the title How to deal with relative paths in MDX in translated pages? Convert relative paths in MDX docs to absolute ones Oct 29, 2019
@tesseralis tesseralis changed the title Convert relative paths in MDX docs to absolute ones Convert relative paths in MDX docs to package references Oct 29, 2019
@tesseralis tesseralis added type: feature or enhancement and removed type: question or discussion Issue discussing or asking a question about Gatsby labels Oct 29, 2019
@tesseralis tesseralis changed the title Convert relative paths in MDX docs to package references Move components in www to their own package Oct 29, 2019
@tesseralis tesseralis changed the title Move components in www to their own package Move components in www used in MDX files to their own package Oct 29, 2019
@tesseralis tesseralis added the help wanted Issue with a clear description that the community can help with. label Nov 8, 2019
@Qovaros985
Copy link
Contributor

@tesseralis, could I work on this issue?

@tesseralis
Copy link
Contributor Author

@Qovaros985 sure, go ahead if you still want to!

@tesseralis tesseralis assigned 1qk1 and Qovaros985 and unassigned 1qk1 Dec 5, 2019
Qovaros985 added a commit to Qovaros985/gatsby that referenced this issue Dec 10, 2019
Qovaros985 added a commit to Qovaros985/gatsby that referenced this issue Dec 10, 2019
Qovaros985 added a commit to Qovaros985/gatsby that referenced this issue Dec 10, 2019
Qovaros985 added a commit to Qovaros985/gatsby that referenced this issue Dec 11, 2019
Qovaros985 added a commit to Qovaros985/gatsby that referenced this issue Dec 11, 2019
Qovaros985 added a commit to Qovaros985/gatsby that referenced this issue Dec 11, 2019
@tesseralis tesseralis changed the title Move components in www used in MDX files to their own package Make website components used in MDX files globally available Jan 16, 2020
tesseralis added a commit to gatsbyjs/gatsby-pl that referenced this issue Feb 26, 2020
For whatever reason, this page was not properly synced. This is a problem because this page contains relative imports that cause the build to break when sourced from a translation repo: gatsbyjs/gatsby#19036

Sync this page manually by just copy-pasting it from the main repo.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Issue with a clear description that the community can help with.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants