"FAKE - F# Make" is a cross platform automation system, mainly used for builds and releases. Due to its integration
in F#, all benefits of the .NET Framework and functional programming can be used, including
the extensive class library, powerful debuggers and integrated development environments like
Visual Studio or MonoDevelop, which provide syntax highlighting and code completion.
We recommend Visual Studio Code with the Ionide extension for best FAKE tooling support.

The new DSL was designed to be succinct, typed, declarative, extensible and easy to use.

The industry movement towards "DevOps" and "infrastructure as code" leads to the fact that reproducible builds and automation becomes more and more important for basically every project.
Question is: Why do we build our automations in "old" and error-prone scripting languages like bash, cmd or powershell instead of a full featured language with IDE support, static typing and compile-time errors?
We believe there are different answers to that:

The build/release process starts very simple, often with a single command. Setup a C# project or installing dependencies feels like overkill

People use/depend on external systems and deeply integrate into those.

Lack of awareness of other options

FAKE addresses the problem in the following ways:

It builds on top of a fully featured statically typed and productive language (F#) with several IDE options.

It lowers the entry point by working on top of script files. No project file or dependencies besides the fake runner.

Remove dependencies from the CI/CD system while providing full integration. Make features available locally.
With FAKE you can choose and switch between multiple system easily while having almost native integrations.

Some of the documentation talk about FAKE packages and some about FAKE modules.
Strictly speaking there is no difference and both are usually tied to a particular NuGet package.
The confusion arises as F# talks about modules (static classes) and usually a FAKE NuGet package contains a single F# module.
So the term module should be used for code fragments while package for NuGet packages.

Yes indeed! You can just use all the different FAKE packages, like Fake.Core.Environment. The API reference will list the NuGet package you need to install right at the top.
Some/most of the FAKE-APIs will complain about a missing context, to initialize one you can use