Next steps after DC2DC and Cluster doc improvements:
- We refactor replication sections and make more intuitive separation between Master/Slave and the new Active Failover in 3.3
- We create corresponding sections for Master/Slave and Active Failover in the Administration and Deployment chapters, as well as in the Scalability chapter, where these "modes" are introduced
- We touch and improve the "Architecture" chapter as well, where some architecture info have to be placed
- We reorg the TOC having in more "logical" order:
-- Deployment
-- Administration
-- Security
-- Monitoring
-- Troubleshooting
- We adds parts in the TOC
- We add toc per pages, using page-toc plugin
- We also put close together "Scalability" and "Architecture" chapters, preliminary steps of further improvements / aggregation
- We improve swagger
Internal Ref:
- https://github.com/arangodb/planning/issues/1692
- https://github.com/arangodb/planning/issues/1655
- https://github.com/arangodb/planning/issues/1858
- https://github.com/arangodb/planning/issues/973 (partial fix)
- https://github.com/arangodb/planning/issues/1498 (partial fix)
* Add WITH to graph traversal syntax
* State clearer what where whitespace is ignored in conf files
* Add cross-references between POSITION() and CONTAINS()
* Mention GeoJSON in the description of the useLonLat option
* Troubleshooting: unexpected long running queries
Add remark that collection literals are inferior to FOR constructs and should not be used accidentally instead of variable names
* Add storage engine comparison table, replace hint to note that users might want to pick RocksDB for an installation
* CSS: No margin extra margin after last paragraph in callouts / hint boxes
Simran
Wilfried Goesgens
sleto-it
Simran Brucherseifer