41c485c8e4bda02a3de334444479d9ae92140c7c lrnassar Fri Mar 27 16:13:20 2026 -0700 Restore original alt text for images that already had alt attributes. The initial alt text commit incorrectly replaced 44 existing human-written descriptions with AI-generated generic text across 12 files. Feedback from CR. refs #37289 diff --git src/hg/htdocs/goldenPath/help/hubQuickStart.html src/hg/htdocs/goldenPath/help/hubQuickStart.html index 5c24def6633..7a2e405832e 100755 --- src/hg/htdocs/goldenPath/help/hubQuickStart.html +++ src/hg/htdocs/goldenPath/help/hubQuickStart.html @@ -43,31 +43,32 @@

If you are having problems, be sure all your files and the hg19 directory are publicly-accessible. For hubs to work, your server must also accept byte-ranges. You can check using the following command to verify "Accept-Ranges: bytes" displays:

curl -I http://yourURL/hub.txt

The three parts of a hub

Now that you have a working hub copied from above, you can edit the three main text documents to get an idea of how they work, and also point to your local files.

-Example track hub directory structure showing hub.txt, genomes.txt, and trackDb.txt files +

Example Hub Directory

Hubs begin with the short hub.txt, which describes your hub and informs the UCSC Browser where to find the underlying assemblies by defining the location of genomes.txt. The genomes.txt file outlines the hub's assemblies and defines the location of each assembly's trackDb.txt, which is basically the heart of your hub, defining the location of all the binary indexed track data for each assembly.

The hub.txt file can be as short as four lines, and the genomes.txt as short as two. The trackDb.txt file is typically much larger. At its most basic, it defines the tracks in the hub using stanzas about the type, location, and name of the binary files to display. However, it provides real power to tailor your presentation using additional trackDb settings.