Please consider improving the documentation and examples about log

[Lastique]

in most code examples, it is not mentioned what include files to use.

There is a link to the complete source code of every non-trivial code example below the example. The relevant headers are also listed at the beginning of every section, and those headers are also links to Reference documentation.

Can you be more specific which examples are lacking this information?

Consider using a tool like doxygen to autogenerate API documentation.

Doxygen is used to generate Reference documentation.

It took me a while searching the sources to figure out that the namespace src isn't correct, the correct one is boost::log::sources.

It's not incorrect, the namespace shorthands used in the documentation are defined here. The shorthands are used to reduce syntactical clutter in the code samples.

I could probably improve exposure of this information by moving it to the front page. This would require restructuring docs though.

Using a settings file was not documented at all.

It is.

I had to figure out how to do it based on the example code. There are a lot of strange things in this example that make no sense to me, as I am unfamiliar with the library and its APIs

The example demonstrates how to load the settings file and how adding attributes affect it. All examples are there to demonstrate this or the other feature or use case of the library, and users are free (and even expected) to compile and experiment with examples and see how the library behaves. Understanding what each line does requires one to read the documentation before that, though.

What the heck is pimpl

The term is the link right there in the text.

and why do I care?

Because it affects how attributes behave. It is also important to know if you're going to implement your own attribute. This information is literally what you're asking:

I'm here to understand how the library works.

Here, I was thinking "yes, finally, an explanation of that these things are"... and then it just completely fails again to explain what they are. What does it mean to "generate attribute values"? What are those? Why do I need them?

There is a section with basic term definitions as well as the design overview which are recommended to be read first in the How to read section I mentioned above. These sections give you understanding of how the library operates as a whole. With that understanding, it should be easier to understand the details given in the Detailed feature description.

I can give a few introductory words in the Attributes section that basically duplicate what is written on the pages I linked, but this will be just that - duplication, and it will not relieve the reader from reading those other pages anyway as they are necessary to understand how the library works.

In any case, thank you for your feedback.