v4 notes

[stancl]

Writing down notes to mention in v4 docs, so that we can clean up the issues here.

• Mention that there will be multiple connections open (= that the central connection remains open) Should warn developers this package might cause 2 db connections per request/process #162
• Mention using Artisan::call('tenants:run', ...) Add to Docs... #120
• spatie/laravel-backup integration (not tested) notes for spatie/laravel-backup #101
• Write a guide for integrating Scout Tutorial for scout integration #72 (PR open)
• --skip-failing on tenant migrations, Document using --skip-failing on tenants:migrate #73
• Media library integration Using this package with spatie media library #78
• Mention that Horizon works on the central domain Horizon dashboard /horizon redirects to /app #75
• Rename cached lookup to cached tenant lookup Rename cached lookup to cached tenant lookup #64

[ianrobertsFF]

Overhauling the docs in general would be a good idea, there's plenty of stuff in the v3 docs that are still missing/todo.

Understandable not updating those now given that v4 is coming, but ideally v4 shouldn't release with similar "see v3/v2 docs" or "TODO", etc.

[stancl]

Yeah, v4 docs will be rewritten from scratch

[abrardev99]

Can we make headings clickable in v4? It's actaully just wrapping them in a tag. I see almost all headings have the id attribute so that we can use id in href.
I think it makes sense to copy documentation links to a specific page and then a specific heading. Like in Laravel documentation, headings are clickable, and the URL appends with #some_heading.

Note It's a small change. We can ignore it, but it's good UX as almost all docs site has this, and it's kind of become muscle memory.

[stancl]

Yeah, I'd add a clickable # in front of the headings. Like Laravel docs: https://laravel.com/docs/9.x/installation#laravel-and-docker

Usually the # is clickable and the heading isn't, but I see that in Laravel docs they are both clickable, and it's probably better UX.