First nothing, then the infinity wars. You know; the miracle of the fallacy à la generality.

Satisfy the keepers of the gate. Officially verify ownership of your property, uh, website. Put the verification code from their web mastery tools into the configuration file (config.yaml, config.json, config.toml).

---
params:
  search:
    verification:
      google: randomString
      bing: randomString
      yandex: randomString

Resource abuse is not good — cache responsibly. In the configuration file (config.yaml, config.json, config.toml) set the cache expiry time. The default is 12h (12 hours) for remote fetches and -1 (forever) for assets, images, and modules. The time scales are seconds (s), minutes (m), and hours (h). Turn off a cache by setting a max age of 0.

---
caches:
  assets:
    dir: :resourceDir/_gen
    maxAge: -1
  images:
    dir: :resourceDir/_gen
    maxAge: -1
  getcsv:
    dir: :resourceDir/caches
    maxAge: 12h
  getjson:
    dir: :resourceDir/caches
    maxAge: 12h
  getresource:
    dir: :resourceDir/caches
    maxAge: 12h
  modules:
    dir: :resourceDir/caches
    maxAge: -1

This message is pinned for reasons unknown. For a quick start guide, @default might be able to help you. The #docs explain what we are currently capable of doing. Warning: This micro blog is remarkably experimental, don’t hurt yourself.