-
Notifications
You must be signed in to change notification settings - Fork 43
Restructure docs, stage 2 #3116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
78e4d8b
to
b0194f5
Compare
RedirectsApp server
Tooling
Data model
Indexes
Sharding
Triggers
Transactions
Storage engines
Replication
|
b0194f5
to
37579a5
Compare
4df2ff7
to
ad22191
Compare
9e93b73
to
b5a23ba
Compare
3deeb0e
to
4155632
Compare
That's an impressive work! However, I've got one concern about repeating headings in different top-level sections. We have Replication and Sharding in How-to, in Concepts, and in Administration. This already affects the search: when you type "sharding", you get three results with the same heading. This may be confusing. Moreover, I'm not sure how this will affect SEO. Perhaps we can think of more specific headings. |
4175260
to
f2a597f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
For some reason the |
* Remove redundant Authentication page
Move the content to different chapters, save some content for the Concepts section. * Tutorial on pokemons (Creating application): How-to * Developing with IDE, Cookbook recipes: How-to * Module installation and reload: Admin guide * Module contribution: Dev guide * Create a Tooling section in the Reference chapter * Move console tools to the Tooling section * LuaJIT tooling: Reference/Tooling * Concepts: early draft
* Overview & Architecture -> Concepts * Quick start -> How-to * Sharding administration -> Administration
* Remove unused examples from 2019 Also remove unused files from conf.py exclusions * Fix some build warnings * Move some replication guides to Administration - Monitoring a replica set - Reseeding a replica - Recovering from a degraded state - Resolving replication conflicts * Split repl_sync and repl_leader elect to Concepts and How-to * Format by style guide * Fix heading levels * Move 'Server startup with replication' to Internals * Move orphan status to internals * Move Replication internals translation
f2a597f
to
8a57851
Compare
Resolves #2987
Resolves #2805
Rebase this often!
Plan:
https://www.notion.so/tarantool/Tarantool-CE-c075d0db9ce24893beca704c145ae501#a89e84e55afe45f091df87be9a32a884
(internal document)
Move Access control to Administration (1sp)
Create new Concepts section
Application server -> Concepts, How-to, other sections (5sp)
Data model -> Concepts, How-to, Reference (5sp)
Indexes -> Concepts, How-to (3sp)
Sharding -> Concepts, Administration, Reference, How-to (5sp)
Replication -> Concepts, other sections (5sp)
Fill the new Concepts section with all the necessary info (audience: product teams, analysts) (1sp)
Replace links where needed (1sp)
Add links to Overview (1sp)
Transfer translations (1sp)
Add redirects (1sp): https://github.com/tarantool/tarantool.io/pull/1296