Hi folks many thanks for your great work.

Describe the bug

Date and datetime can be improperly persisted.

To Reproduce

• Add the following section to a config file

  - name: test
    label: Tests
    create: true
    folder: "content/_tests"
    fields:
      - name: title
        widget: string
      - name: date
        widget: date
        format: YYYY-MM-

A small pet peeve of mine is that the --ssl option enables TLS, not SSL. I accept that the tech world uses these related but different terms interchangeably, but I'd rather be more correct by default.

To do:

1. Replace the existing --ssl option with --tls.
   a. Note that this enables "TLS/SSL" in the documentation so it doesn't confuse people.
   b. The short option -S could stay th

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,

Prerequisites

• I am running the latest version. (up upgrade)
• I searched to see if the issue already exists.
• I inspected the verbose debug output with the -v, --verbose flag.
• Are you an Up Pro subscriber?

Description

It would be great to add regex capabilities to redirects like so:

redirects: {
  "/folder/:slug(regexhere)": {
    "location": "https

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

Right now we can create custom configuration based on presets, however I think it would be worth allowing custom presets also.
This would mean opening up the Preset interface so for example a framework could maintain their own Preset file and users can then use the preset, just by pointing

Could the generated docs be moved to a separate repo? The CI could then commit to that separate repo to keep them updated...

I was working through setting up detekt in a sample Android project, and ran into some odd/confusing behavior. This occurred with version 1.6.0, but also seemed to occur if I tried older versions as well.

I set things up in my root level project as per the instructions here, and applied the plugin to my mai

https://owais.lone.pw/blog/webpack-plus-reactjs-and-django/

For one 'loaders' is changed to 'rules'

Then:

$ ./node_modules/.bin/webpack --config webpack.config.js
Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.
 - configuration.resolve has an unknown property 'modulesDirectories'. These properties are vali

The analyzer warns correctly, but the documentation for SCS0007 only has guidance for XmlReader and XmlDocument. The warning also appears for XmlPathDocument/XPathNavigator, which is also insecure by default on .NET version prior to 4.5.2. https://github.com/OWASP/CheatSheetSeries/blob/master/cheatsheets/XML_External_Entity_Prevention_Cheat_Sheet.md#xpathnavigator has guidance on an example fix

I am trying to evaluate adapting ArduinoMenu to run under Mongoose OS, and am looking at a two stage implementation plan:

1. get it running on Linux (with a very generic serial input and output device, similar to the Blink or Button examples). I want to do this so I can quickly get the menus going, and make sure I really understand what's going on.

2. move it to Mongoose OS (with an ILI9341

Crawler stops on 404 or 405

Simple instructions are missing how to use the app with a proxy server like nginx or apache and how to turn it into a self-starting systemd-service.

Hi! We have such directories names in our static website /public/doc/changelog/0.18
And when serve-handler handles requests we have 404 for such pages.
I found reason - there is false-positive extname checking here https://github.com/zeit/serve-handler/blob/master/src/index.js#L610
But I'm not sure how it should be resolved. Maybe this check can follow next one (where handles cleanUrl)

GitDocs routing transforms 'index.md' into '/index' thus the user must write [Index](/index) when cross-referencing docs. This means links do not work when on GitHub. We have extensive docs written with GitHub routing in mind, so if switching to GitDocs we would have to change all of our links and we would lose links on GitHub. Why has GitDocs a routing system that is incompatible with GitHub ?