docs: add Omarchy, Laradock and Sail landing pages - #1541
Merged
Conversation
Omarchy has become the distribution developers are actually talking about, and it ships a finished desktop with no web stack at all, so someone arriving there has to solve the PHP side themselves. The new page covers that gap: the Arch prerequisites that are not defaults, crun and nss, the systemd-resolved without NetworkManager case that the lerd0 dummy interface handles, why the tray autostarts there because Omarchy launches Hyprland through uwsm, and the bar widget. Laradock had no page despite being the thing a lot of people are trying to leave. There is no automated importer for it, stacks vary too much to migrate blind, so the page documents the manual path instead: dump from the Laradock database container, move the project out from under APP_CODE_PATH_HOST, then link, env and db:import. Sail already had the importer documented under usage, but nothing that answered why you would move in the first place, and the entry pointing there from Getting Started dropped the reader into a different sidebar. It gets a sibling page to the other migration guides that links onward for the flag reference. The Getting Started sidebar had grown into a flat list of eleven items with no relationship between them. It is now grouped into Start here, Platform guides and Coming from another tool, with the existing labels kept so nothing that is already indexed changes. The section index follows the same shape.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Three pages we did not have, aimed at people searching for the problem rather than for lerd.
Omarchy is the distribution developers are actually talking about right now, and it ships a finished Arch and Hyprland desktop with no web stack at all, so the PHP side is the one thing left to solve on a fresh install. The page covers the Arch prerequisites that are not defaults there, crun and nss, the systemd-resolved without NetworkManager case that lerd0 handles, why the tray autostarts because Omarchy runs Hyprland through uwsm and would not on bare Hyprland, and the Glance bar widget.
Laradock had nothing, despite being the stack a lot of people are actively trying to get out of. There is no automated importer for it and there should not be, Laradock setups vary too much to migrate blind, so the page documents the manual route: dump from the Laradock database container, move the project out from under APP_CODE_PATH_HOST, then link, env and db:import. It keeps the honest case for staying, per project database major versions, which is the one thing lerd does not do.
Sail had the importer documented under usage but nothing explaining why you would move, and the Getting Started entry pointing at it dropped the reader into a different sidebar. It now has a sibling page to the other migration guides and links onward for the flags.
The Getting Started sidebar had become a flat list of eleven unrelated items. It is now three groups, Start here, Platform guides and Coming from another tool, and the section index follows the same shape. Existing labels and every URL are unchanged, so nothing already indexed moves.