Bug report

Describe the bug

When running next using Yarn 2 and visiting a page in the browser that doesn't exist, the 404 error page never shows up. Instead it loads forever ("waiting on localhost...") and then eventually errors with ERR_EMPTY_RESPONSE.

But the terminal shows that the page was compiled:

[ event ] build page: /next/dist/pages/_error
[ wait ]  compiling ...

Summary

Our docs relating to GraphQL sometimes have CodeSandbox samples where viewers can edit their query. However, these pages are represented in the markdown as raw iframes and are quite ugly:

<iframe title="A basic query" src="https://7118

If you use a shortcode in a content file in order to embed a read time estimation for that content file within itself, the estimation always comes back as 0. This is probably because the parser hasn't finished converting the document by the time it gets to the read time estimation so it can't actually get an estimate for it. This is supported by the fact that, when embedding a read time estimation

Motivation

The instructions for OpenSuse are incomplete, for Leap 15.1 at least. The command

sudo zypper install -t pattern devel_ruby devel_C_C++

does not install ruby-devel (only ruby2.5-devel):

Contents :
S | Name

Check List

Please check followings before submitting a new feature request.

• I have already read Docs page
• I have already searched existing issues

Feature Request

New to Hexo and finding some inadequacies in some of the documentation.

• Under Helpers List Tags (and other list_ helpers) the "style"

Operating system: Any
Last upstream commit (run git log --author="Robert Lord" | head -n 1): commit cf29f6786c288b6111239b8e8b211f8ae2fbc4c3
Browser version(s): Any
Ruby version (run ruby -v): ruby 2.3.3p222 (2016-11-21 revision 56859) [x64-mingw32]

We started seeing either an 'undefined' or a blank space in our page titles, as some of the headers have nested html, and the Slate

Feature request

palette.style should be renamed since it's not only relevant to colors.

See config.styl.

I'm considering switch to mkdocs from sphinx, but cannot solve the navigation issue.
This is a sample built with sphinx + recommonmark+ readthedocs theme+ readthedocs host
readthedocs theme should support

1. multi-level nav
2. clickable index links/page
3. auto-generate TOC with sub-leve

Greetings, thank you all for your work on pelican! It's a wonderful tool and I'm a user since many years!

This issue is related to #2349. I'd like to suggest an improvement in documentation and awareness of the STATIC_URL and STATIC_SAVE_AS parameters, which might lead to a better utilization of this feature for external static domains/origins. In [the current 4.2.0 docs](https://docs.getp

Is your feature request related to a problem? Please describe.
I am using react-static to create a site that is hosted out of S3. I want to be able to use object versioning to track changes to the objects over time, but I can't do that with the main JS file, as it has a hash code in the middle. I am guessing that this is used for cache busting, but S3 already has robust etag support built in,

On the website if I use all the snippets like below, the layout plugin is not working, it just transpiles the markdown to HTML, without the layour wrapper.

index.js

var Metalsmith  = require('metalsmith');
var collections = require('metalsmith-collections');
var layouts     = require('metalsmith-layouts');
var markdown    = require('metalsmith-markdown');
var permalinks  = requir

Seems like main variables are missing on the middlemanapp page, like

current_page

not sure what the other ones are because of lack of documentation

Summary

Add a site AMP version.

Basic example

Nuxt.js has an example: https://github.com/nuxt/nuxt.js/tree/dev/examples/with-amp
Gatsby AMP Plugin: https://www.gatsbyjs.org/packages/gatsby-plugin-amp/

Motivation

The AMP Project support is very important to accessibility and Google's Pagerank. So, it could will be awesome had this support in Gridsome.

This is not documented anywhere and happens silently, even when using debug

#62 我的环境

期望行为

yaml格式和properties格式的代码应该正常显示

当前行为

yaml出现错误

properties代码出现错误
<img width="867" alt="WX20191019-022128

Hi;

I hope it's a feature request and not a bug report
I try to apply design.background but at the item level
and the code won't let me add more than one [design.background]

this is work

widget = "slider"
weight = 11
[[item]]
  title = "Left"
  content = "I am left aligned :smile:"
  [design.background]
    gradient_start = "#0000F9"
    gradient_end = "#86007D"

Assemble's highly modular nature makes it difficult to discover methods that are added via mixins or inheritance. For example, .use and .define are provided by Base and implicitely added through Templates.

It would be a huge help to have some basic, generated JSDocs that incorporate all of the default packages. JSDoc provides the @mixinand [`@mix

Feature Request

Is your feature request related to a problem? Please describe.

The Preact Section in the readme, as they are out of date. Preact v10 has a proper hydrate method now. PR: preactjs/preact#1802.

Describe the solution you'd like
Update the

Documentation issue

Summary

The get_taxonomy() function documented here and implemented here isn't documented.

From the tests [here](https://github.com/getzola/zola/blob/1972e58823417

wintersmith build -h lists options, including --clean.
it also states all options can also be set in the config file.

turns out that not all options can be set; for example clean is not honoured (see #149).

the wording of the help text should be updated to reflect that some, but not all, options can be set. ideally those that are cli-only should have an indicator.

https://github.com/phenomic/phenomic/blob/master/packages/preset-react-app/docs/getting-started/5.md

When we tell people to add this section to their component after the list, it creates two nodes that are not contained. It is a ul and a div.

We should somehow mention that you need to surround the two in a div before adding that extra snippet to Older Posts, because react will only l

Currently, it is only possible to link to an already existing page of the site.
When using publii as a standard (i.e. non-blog) site creator, this totally breaks the flow : while writing a page, you think to something you want to link to as a new page, yo must save/close your page, create the new one, save it, go back to the first page, create the link and keep going.

It would be very convenie

It seems strange that a project whose purpose is to build documentation itself has such poor documentation. The DocFX tool and concept seem very cool and flexible; however, there is apparently no official documentation describing the architecture of DocFX--what each concept means, how they relate, etc. (documentation about the d

Description

With the release of library dynaconf version 2.0, the quokka installation broke.

Then we must change the version of requirements.txt

dynaconf>=1.0.0,<=1.2.1

Reference

Dynaconf 2.0.0

Add Saber to this page (https://codesandbox.io/s/):

This is how VuePress got added there, it should be similar for Saber.

After that, we should also display the sandbox on