Improve doxygen docs

README.md

@@ -1,7 +1,7 @@
 # Rapid YAML
 [![MIT Licensed](https://img.shields.io/badge/License-MIT-green.svg)](https://github.com/biojppm/rapidyaml/blob/master/LICENSE.txt)
 [![release](https://img.shields.io/github/v/release/biojppm/rapidyaml?color=g&include_prereleases&label=release%20&sort=semver)](https://github.com/biojppm/rapidyaml/releases)
-[![Documentation Status](https://readthedocs.org/projects/rapidyaml/badge/?version=latest)](https://rapidyaml.readthedocs.io/en/latest/?badge=latest)
+[![Documentation Status](https://readthedocs.org/projects/rapidyaml/badge/?version=latest)](https://rapidyaml.readthedocs.io/latest/?badge=latest)
 
 [![PyPI](https://img.shields.io/pypi/v/rapidyaml?color=g)](https://pypi.org/project/rapidyaml/)
 [![Gitter](https://badges.gitter.im/rapidyaml/community.svg)](https://gitter.im/rapidyaml/community)
@@ -51,7 +51,7 @@ ryml is written in C++11, and compiles cleanly with:
 * Intel Compiler
 
 ryml's API documentation is [available at
-ReadTheDocs](https://rapidyaml.readthedocs.io/en/latest/).
+ReadTheDocs](https://rapidyaml.readthedocs.io/latest/).
 
 ryml is [extensively unit-tested in Linux, Windows and
 MacOS](https://github.com/biojppm/rapidyaml/actions). The tests cover
@@ -239,7 +239,7 @@ level API for accessing and traversing the data tree.
 
 The following snippet is a very quick overview taken from quickstart
 sample ([see on
-doxygen](https://rapidyaml.readthedocs.io/en/latest/group__doc__quickstart.html)/[see
+doxygen](https://rapidyaml.readthedocs.io/latest/group__doc__quickstart.html)/[see
 on github](samples/quickstart.cpp). After cloning ryml
 (don't forget the `--recursive` flag for git), you can very easily
 build and run this executable using any of the build samples, eg the

doc/Doxyfile

@@ -957,6 +957,9 @@ INPUT                  = \
                          ../ext/c4core/src/c4/charconv.hpp \
                          ../ext/c4core/src/c4/format.hpp \
                          ../ext/c4core/src/c4/base64.hpp \
+                         ../ext/c4core/src/c4/std/string.hpp \
+                         ../ext/c4core/src/c4/std/string_view.hpp \
+                         ../ext/c4core/src/c4/std/vector.hpp \
 
 # This tag can be used to specify the character encoding of the source files
 # that doxygen parses. Internally doxygen uses the UTF-8 encoding. Doxygen uses
@@ -2495,6 +2498,8 @@ PREDEFINED = \
            "C4_MUST_BE_TRIVIAL_COPY(cls)= " \
            "C4_NO_INLINE= " \
            "C4_NO_UBSAN_IOVRFLW= " \
+           "C4_NODISCARD= " \
+           "C4_NORETURN= " \
            "C4_PURE= " \
            "C4_REQUIRE_RW(ty)=ty " \
            "C4_RESTRICT= " \

doc/doxy_main.md

@@ -10,25 +10,7 @@
     * @ref doc_node_type
     * @ref doc_tree
     * @ref doc_node_classes
-  * For serialization/deserialization:
-    * See @ref sample_scalar_types for when the type is scalar (a leaf node in the YAML tree, containing a string representation): 
-      * See examples on how to @ref sample_to_chars_scalar
-      * See examples on how to @ref sample_from_chars_scalar
-      * See the sample @ref sample::sample_user_scalar_types
-      * When serializing floating point values in C++ earlier than 17,
-        be aware that there may be a truncation of the precision with
-        the default to_chars implementation. To enforce a particular
-        precision, use for example @ref c4::fmt::real, or call
-        directly @ref c4::ftoa or @ref c4::dtoa, or any other method
-        (remember that ryml only stores the final string, so nothing
-        prevents you from creating it). See the relevant sample: @ref
-        sample::sample_float_precision.
-    * See @ref sample_container_types for when the type is a container (ie, a node which has children, which may themselves be containers).
-      * See the sample @ref sample::sample_user_container_types
-    * ryml does not use any STL containers internally, but it can be
-      used to serialize and deserialize these containers. See @ref
-      sample::sample_std_types for an example. See the header @ref
-      ryml_std.hpp and also the headers it includes.
+  * For serialization/deserialization, see @ref doc_serialization.
   * @ref doc_tag_utils - how to resolve tags
   * @ref doc_callbacks - how to set up error/allocation/deallocation
     callbacks either globally for the library, or for specific objects