Hypertext imposes no overarching structure at all, content objects connect only through associative links, forming a web rather than a hierarchy. It's flexible and scalable, which makes it useful when an organization doesn't yet know what content it will create, as with wikis and knowledge bases. But that same flexibility is a weakness: without a clear structure, people can become lost, unable to find their way back to something they've already seen. In most cases, hypertext supplements a site's primary structural pattern rather than serving as the whole architecture.
A linear sequence sits at the opposite extreme: an ordered series of pages or steps that users move through in order, with a clear beginning, middle, and end. It suits limited-scope content like surveys, wizards, tests, and tours, where the user must generally follow the same path. A well-designed sequence needs a consistent title for the whole sequence, a subtitle identifying the current step, a visible list of steps showing progress, and clear Next and Previous controls, and it should be avoided whenever a sequence isn't genuinely necessary, since imposing one on content that doesn't require it just frustrates users.
Hypertext trusts the user to find their own path. A linear sequence assumes there's only one path worth taking. Choosing the wrong one for your content creates exactly the opposite problem you were trying to solve.
1: Hypertext. Patients exploring freely, following their own interests, and moving between related articles across topics is exactly the associative, web-like browsing that hypertext supports.
2: Linear sequence. A required order, a defined set of steps, and a clear endpoint, booking the first appointment, is precisely what a linear sequence is built for.
Swapping these would create real problems, not just a mismatched feel. Structuring the wellness library as a linear sequence would force patients through a fixed order of articles, including many they have no interest in, just to reach the one they actually want, directly undermining the free exploration that makes the library useful in the first place. Structuring onboarding as hypertext would let patients wander into any step in any order, potentially skipping required medical history or consent forms entirely and reaching the appointment booking step without having completed them, a compliance and safety failure, not merely an inconvenient user experience.This pairing illustrates why structural pattern choice isn't a stylistic preference, it encodes real constraints about what the content actually requires from the user, and getting it backwards can create consequences well beyond a clunky interface.