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,

#62 我的环境

期望行为

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

当前行为

yaml出现错误

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

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

Hi, Matt. Not sure if a tutorial request is allowed here. First of all, thanks for creating the Responsive Bar Charts with Bokeh, Flask and Python 3 tutorial, it was really insightful! I was wondering if you're planning to do a flask + flask_bootstrap and multiple bokeh plots tutorial ~ this is something that I

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

After setup my blog (BlogEngine.net 3.3.8.0 on IIS 8.0) to use https I cannot publish anymore a post. Neither I cannot re-add my blog after remove it.

When I try to do, I receive this error

Open Live Writer

Can't connect to your blog service:
Network Connection Error - Error attempting to connect to blog at:
http://www.myDomain.com

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

Currently several places (notably the compiler plugins) open the source_path directly. Let's use Post.source() instead.

This is part of getting to a place where #2659 is doable.

As per https://docs.aws.amazon.com/acm/latest/userguide/acm-regions.html, ACM has a restriction that requires certificates to be created in the us-east-1 region in order to be used with CloudFront:

To use an ACM Certificate with Amazon CloudFront, you must request or import the certificate in the US East (N. Virginia) region. ACM Certificates in this region that are associated with a CloudFr

https://github.com/daptin/daptin/blob/aa77b35feeb48557b42a13b7a05fb291eb1e562a/docs_markdown/docs/features/enable-data-auditing.md#L1

This issue was generated by todo based on a todo comment in aa77b35feeb48557b42a13b7a05fb291eb1e562a. It's been assigned to @artpar because they committed the code.

There should be a docpress init command to build a default skeleton.

├── docs
│   ├── example.md
│   └── README.md
├── .gitignore
└── README.md

Where README.md can be the actual docpress readme or a bootstrap, .gitignore the actual docpress gitignore, docs/README.md a short TOC and docs/example.md a markdown cheat sheet or a bootstrap.

docs/README.md

* [d

Summary

I found unnecessary spaces are in "AVAILABLE OPTIONS" in help page. I attached the screenshot about this.

What is expected

I think extra spaces should be deleted.

How to reproduce

1. Run scotty -h command

Versions

soctty version: 1.10.2

Following the README.md to set .env as follows:

HEADLESS_CMS_GITHUB_TOKEN=examplekey123abc
HEADLESS_CMS_TWITTER_CONSUMER_KEY=examplekey231abc
HEADLESS_CMS_TWITTER_CONSUMER_SECRET=examplekey321abc
HEADLESS_CMS_TWITTER_ACCESS_TOKEN_KEY=examplekey231abc
HEADLESS_CMS_TWITTER_ACCESS_TOKEN_SECRET=examplekey321abc

When running npm start I still get:

> headlesscms@2.0.0 s

Description

When adding url links in Ghost CMS, you are forced to enter them as absolute paths, e.g. https://ghost-cms.com/welcome/ to link to the welcome post. These links don't work anymore in the gatsby site, as they should be served from the siteUrl, e.g. https://gatsby-ghost.com/welcome/.

You can see the issue also in the demo. Goto the bottom of the demo [welcome page](https://gatsb

There's currently a thread on HN discussing tech/software tooling options for the visually impaired [fn1]. I think it would be fantastic if Usesthis could collect a section of interviews in this context, by inviting users with different kinds of challenges (and feature this section prominently on the navbar).

If you're looking for suggestions to kick things off, T.V. Raman might be interestin