Bug Report

From the docs section Add favicon and metadata

Comment in code example states for "The doc prop contains some metadata about the page being rendered that you can use."

// The doc prop contains some metadata about the page being rendered that you can use.
const Wrapper = ({ children, doc }) => <React.Fragment>
  

Reading readme.md, the point "📓 Speaker notes" (the link is broken) is a feature that exists, no longer exists or a mistake?

Subject of the issue

When clicking a link in the documentation, the page flashes to light mode for a moment and then back t

Info

• Operating System:
• Node Version:
• Browser Name and Version:

Type

• bug
• feature request

For Bugs

Expected Behavior

Actual Behavior

How can we reproduce the behavior?

For Feature Request

What is the motivation or use-case for the fe

Before undergoing a substantial to docs or the codebase, please open up an issue to make sure it's a desired change.

I'd like to improve the navigation in these ways:

• If the user clicks on Read the docs on the homepage, he/she will be redirect to https://blocks-ui.com/docs. I'd like to redirect to https://blocks-ui.com/getting-started/ as the starting point for the documentation.
• High

Describe the bug

GitHub provides a few options when configuring a new repo like: license, .gitignore file, a README.md, and the Rennovate plugin. If you want to install any of these by default, which I usually do, then you get an error about the remote having newer content.

To Reproduce
Steps to reproduce the behavior:

1. Create a repo with a readme during the script
2. See the er

In order to make the Tailwind preset more approachable for people that already know Tailwind, we should:

• Font sizes should have the same aliases (e.g. lg = 2)
• Colors should be aliased to the same aliases * 100, e.g. purple.5 === purple.500
• Breaking change for a major version: Make the padding scale match Tailwind's

I recognize this is a special case so feel free to not support it!

I'm trying to get A-Frame (a webVR library) running within x0. It works with the development server:

Unfortunately after running x0 build docs --static

In /templates/tachyons, I'm not sure I understand what this means:

Be sure to include a link to Tachyons in your document:
<link rel='stylesheet' href='https://unpkg.com/tachyons@4.9.1/css/tachyons.min.css'>

What document?
The kit.config.js file

Thanks for help.
I find the doucment for mondrian 4 schema (https://mondrian.pentaho.com/head/documentation/schema.php#Schema_element), but the very import chapters (3.3) missing, and i cannot find any infromation about Dimensions key and Attributes. Its so different about mondrian 3. So where i can find some useful information about it. I search it in google but nothing helpful.

As of 2.2.0, mdx-loader:

• exports a readingTime object which can be used to add a medium-style estimated reading time
• supports specifying highlighted line ranges for code blocks, using the same syntax as Gatsby

This needs to be documented properly in the README.

Guide Request

Subject: Guide & example for running unit & integration tests on deployment

Additional Information

I'd love to see a clear guide, with examples, of unit & integration tests running on each deployment. There doesn't seem to be any mention of automated testing, (outside of bugbear) in the existing guides.

I was wondering if you guys would consider adding support for https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-transformer-documentationjs

That would make Hasura the perfect starter for almost any library that uses JSDocs which is probably almost all of them. All any dev would need to do is create the new starter inside the lib and you get instant perfect documentation autogenerat

Links don't work with a base path like on gh-pages, as seen here https://jxnblk.com/mdx-docs

• Add docs for how to handle publishing to gh-pages

I have a doc directory, with:

• blank index.mdx
• some docs in build.md

mdx-go renders the default page as:

Project Documentation
TOC

• <li href="//build.md"> build

I imagine that ./build.md or simply build.md was intended in the link target 🤔

Edit: actually, ./build or build is intended, because that renders markdown, while build.md shows raw file...

Wrong behavior

The shortcut to query work is to use Command+Q. However, this will quit the programme instead of query the word. Additionally, I cannot find the “Edit" Tab when I click "Tools" --> "Add-ons". How can I change the shortcut for the "query"?

When it happened

<img width="990" alt="screen shot 2018-10-18 at 5 05 45 pm" src="https://user-images.githubusercontent.com/33351735