Should we optimize for searching or browsing?¶ Documentarians may have to determine whether users search or browse for content of interest. What you decide may influence how to focus your resources: SEO and search tools or navigation aids. The resolution to this may depend on your users and what they’re looking for… and also your product interface. Some users, those who frequently search online for content, may prefer to search through your documentation (for example, spending 70% of their time on search and 30% navigation). Other users may prefer to use your site’s navigation system (for example, 30% search and 70% navigation). Nonetheless, some documentarians assume that searching is the primary method that all users rely on. Some indicate that it’s important to have both methods available for the users to select what they want to do. Information architecture (IA) helps a docs team to develop content in a structured and comprehensive manner. A navigation methodology can implement the IA of the documentation system. So, if your team has developed a structure for the content, you can use it as a navigation device for your readers. As one person indicated: No documentation should be random pages of text. Readers use the structure to learn relationships between different features, use cases, or topics. Searching and browsing are complementary actions. The method used by any one person may depend on different factors and users may use both. Offer the best of both to satisfy your readers. Search-related resources Search platform tips for documentation websites (WTD Newsleter) Making documentation discoverable in search engines (WTD video) Search engine optimization (SEO) for documentation (WTD page) Information Foraging (Nielsen Norman Group) Navigation- and IA-related resources Many articles available from Nielsen Norman Group Building navigation for your doc site: 5 best practices (WTD video) Complete Beginner’s Guide to Information Architecture (UX Booth) How To Make Sense of Any Mess (book by Abby Covert)

One key motivation for Latticework was how wonderful it feels to stumble upon a past moment of shining clarity, to point and revel. We want to be able to carry those moments with us, to see them all at once when we’re lost, and to use them as landmarks as we navigate our messy notebooks. We’ve used Latticework to do this in small ways so far, and we’re excited to see how our upcoming projects might feel different with its extra affordances.

here are badges for progress, statistics that keep users motivated, and also a clear menu that helps to navigate the application easily.

Marking an issue as as a subtask of another. Having task lists in a description is a great start, but it doesn't help (AFAIK) navigating from child back up the chain to parent. Creating umbrella issues is a very common way to track the top-level focus areas for a release.

What we call the "super sidebar" will contain all the elements that pertain to moving around GitLab

There will no longer be a top bar

🌟 Highlight words as they are spoken (karaoke anybody?). 🌟 Navigate video by clicking on words. 🌟 Share snippets of text (with video attached!). 🌟 Repurpose by remixing using the text as a base and reference.

As powerful as search can be, studies5 have found that in manysituations people strongly prefer to navigate their file systemsmanually, scanning for the information they’re looking for. Manualnavigation gives people control over how they navigate, with foldersand file names providing small contextual clues about where to looknext.6

In Tonga, astronomers are called Tiaborau and are members ofnavigator families that hold chiefly ranks.

Verbesserte Suche und Navigation

Webinar ATD Research: Bridging the Skills Gap

clocks from the fourteenth century onwards, how far this was itself a symptom of a new Puritan discipline and bourgeois exac

In whichever group you choose, you can make your note private by choosing “Only Me”. For more information on how this works, see our help article: Who can see my annotations?

Persistent navigation drawers can toggle open or closed. The drawer sits on the same surface elevation as the content. It is closed by default and opens by selecting the menu icon, and stays open until closed by the user. The state of the drawer is remembered from action to action and session to session. When the drawer is outside of the page grid and opens, the drawer forces other content to change size and adapt to the smaller viewport.

For dynamic routes, such as our src/routes/blog/[slug].svelte example, that's not enough. In order to render the blog post, we need to fetch the data for it, and we can't do that until we know what slug is. In the worst case, that could cause lag as the browser waits for the data to come back from the server. We can mitigate that by prefetching the data. Adding a sveltekit:prefetch attribute to a link... <a sveltekit:prefetch href="blog/what-is-sveltekit">What is SvelteKit?</a> ...will cause SvelteKit to run the page's load function as soon as the user hovers over the link (on a desktop) or touches it (on mobile), rather than waiting for the click event to trigger navigation. Typically, this buys us an extra couple of hundred milliseconds, which is the difference between a user interface that feels laggy, and one that feels snappy.

If you belong to private Teams, Free or Basic, your Teams will be listed in the left navigation on all Stack Exchange sites. Currently, they appear only when you are visiting Stack Overflow. If you don’t belong to any teams, there will be a prompt to start a team, which can be minimized.

In other words, once you've used Maybe you cannot hit nil with a missing method. This is remarkable because even &. doesn't save you from omitting || "No state" at the end of the computation. Basically, that's what they call "Type Safety".

Another solution is using the Safe Navigation Operator &. introduced in Ruby 2.3 which is a bit better because this is a language feature rather than an opinionated runtime environment pollution

in this post, we’ll look at how to use this as the basis for an accessible dropdown navigation element that can be opened equally well by keyboard users tabbing through the page, and mouse users hovering on the nav item

You should default to the most permissive option imo and there really is no reason to check anything until you really need to If it were left to me I'd just use optional chaining, as it also eliminates the need for no-ops

Directives like ng-if="info.report.revenue" sort of work in Angular if info.report is undefined, in that the ng-if becomes false. But the Svelte equivalent {#if info.report.revenue} throws an error. For now we're using lodash get in places where we need to and looking forward to Svelte support for optional chaining.

By default, bookdown merges

We can treat navigation as a first-class concept, even encoding state transitions in links.

handle?.destroy?.()

Vertical navigation needs to scroll and “stick” to the screen so that users don’t lose it. Often vertical navigation works well on a single page design

The space used by vertical navigation might be more valuable for other content.

One thing is certain when it comes to navigation trends, users and designers seem to be fed up with completely hidden styles and demand options that work in similar formats on desktops and mobile devices. This might be one of the reasons a vertical pattern is trending.

The common theme is that many hamburger icons open into vertical sliding navigation.

One more word of advice when thinking about vertical navigation: Don’t be tempted to cram it too full of elements just to fill up the depth of a standard-resolution screen. White space is totally acceptable – and even highly recommended – as a design tool in this format.

Non-traditional navigation styles can be a fun way to break up some of the same old design patterns.

If you’re designing any similar type of filtering nav I definitely recommend studying Amazon’s strategy.

Amazon has dozens of categories for every search term. This means they need a way to present refined search features without overcrowding the page. Vertical navigations just make sense because they can tuck away to the side while still being fully accessible.

a fantastic UI design with vertical nav links on product search pages.

A left navigation is faster and more efficient for users to scan. In just three visual fixations, users scan six items in the left navigation compared to the three items scanned in the top navigation. The left navigation also facilitates a vertical scanning direction that is natural for people

A top navigation conserves more vertical page space than a left navigation. With a left navigation, the navigation links occupy the left column of your page. This shrinks and narrows the content area of your page, which means you will have less space for your content. A top navigation, however, uses minimal vertical space, which allows you to occupy the content area of your page with content only.

TypeScript 3.7 implements one of the most highly-demanded ECMAScript features yet: optional chaining

Learn About the Case Learn About the Book Learn About the Context

The Case

her post about the Norman dispute

About

Documents, Objects, and Images

History of Woman Suffrage

Frontier Settlement

Grid view List view

Collection Abraham Lincoln historical digitization project (133) + - Genre books (128) + - songs (document genre) (128) + - sheet music (5) + - Creator Holmes, John (1) + - Hulbert, F. R (1) + - Lewis, Alonzo (1) + - Street, Alfred D (1) + - Watts, J. H (1) + - Subject Political campaigns--United States--History (128) + - Presidential candidates--United States--History (128) + - Presidents--United States--History (128) + - United States--Politics and government--History (128) + - Query(-) "Tippecanoe Song Book"

Page Image

Home Primary Source Materials Media Special Topics About

Pages

Documents

All Primary Sources (4128) Full Text Primary Sources (2699) Secondary Sources (525)

Browse Document Projects and ArchivesDocumentsFull Text SourcesBibliographyPeopleSocial MovementsChronologySubjectsBook ReviewsTeaching ToolsBack Issues

Recent Additions

Home Subjects States Time Periods Primary Source Types Map All Collections

Search

Star-hopping I start thinking about how I navigate the blogs, how I navigate Twitter, how I smile when I click on recognisable avatars.