Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1olsTw-0001I0-Ts for pgsql-docs@arkaria.postgresql.org; Fri, 21 Oct 2022 13:54:41 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1olsTv-0003tJ-Pl for pgsql-docs@arkaria.postgresql.org; Fri, 21 Oct 2022 13:54:39 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1olsTv-0003tA-3U for pgsql-docs@lists.postgresql.org; Fri, 21 Oct 2022 13:54:39 +0000 Received: from wout4-smtp.messagingengine.com ([64.147.123.20]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1olsTn-0003X5-Qd for pgsql-docs@lists.postgresql.org; Fri, 21 Oct 2022 13:54:37 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id 3CABA32007CF for ; Fri, 21 Oct 2022 09:54:30 -0400 (EDT) Received: from imap46 ([10.202.2.96]) by compute5.internal (MEProxy); Fri, 21 Oct 2022 09:54:30 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nielsbom.com; h= cc:content-type:date:date:from:from:in-reply-to:message-id :mime-version:reply-to:sender:subject:subject:to:to; s=fm2; t= 1666360469; x=1666446869; bh=pyuAehnLoqrZBb8aBG2RWUBIo8D7FiHxjNX Vo8tqChM=; b=DhlX99wKZWT+L6hHYX952rAQOq5oHfOT2GAc3UWT5w+7CU2wzBx VkGCbjnCeaL0WLOL2pkA014naNk4JamyquP4gbvpAkUkyXks+pNaeNfMx7FNYdtC 2U2ehkOzQU3mNw48gT8Vw6FmGxa3N79zQ0W8XQiQ1suxm55cTFd3SXOm5Sd+vh6e ysayZj/1jCjtzrYUUwumCgwBue/gE66D+uRCAVK/68GvndgDmmu3tcTPCyTrCt+8 LVBmmr/xwkdvnuoKKkc2cyZBS4l5lQrBlnGMh/94fqdOnReUyx3O41D9LXNkqwDI 3ewvHPDEpZ2rKlmIGrL1M01tDQE4nfJ5fKg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:message-id:mime-version :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1666360469; x= 1666446869; bh=pyuAehnLoqrZBb8aBG2RWUBIo8D7FiHxjNXVo8tqChM=; b=K ZUnZLBgFvZMG/UC/GySh9oERCkxLWYmXNP1baK7zWyguO4WmS+8lbHG8S3Zlr+0z AUPzfYC8LZCCLY36topJatHuQb5keK6GNw9v+mU2sX255RNDAlBma6l1Rp9vHtLk CCIZqy8+whIfvAuF9wT2F/J+CZN9TJkA9b+Ns/ZMELi8iVS/L2s8e5Y3d8WaNKvS mbhmjZNCqulWv08JjpiuOJZiOPOGEDmbLglqNpc0KaKOFjkAuLy3Dd18Lsf2wtI7 ZEmKaFEcJ5J5uHUUg4X1cAqTgfjvpENFpoISRoEhwFAwVKBDjGKpZQZ1mSUTuVIe JOK0EnISLlnt3ZNK8BUNw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrfeelkedgieekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfffhffvufgtsehttdertd erredtnecuhfhrohhmpedfpfhivghlshcuuehomhdfuceonhhivghlshesnhhivghlshgs ohhmrdgtohhmqeenucggtffrrghtthgvrhhnpeegudeiudeuheeuteekheehgeffudffge duuedvffegleegtdelhfekhfeljeefveenucffohhmrghinhepphhoshhtghhrvghsqhhl rdhorhhgpdhphihthhhonhdrohhrghdpmhhoiihilhhlrgdrohhrghdpghhithhhuhgsrd gtohhmnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhep nhhivghlshesnhhivghlshgsohhmrdgtohhm X-ME-Proxy: Feedback-ID: id93146a5:Fastmail Received: by mailuser.nyi.internal (Postfix, from userid 501) id 6A08A2A20080; Fri, 21 Oct 2022 09:54:29 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.7.0-alpha0-1047-g9e4af4ada4-fm-20221005.001-g9e4af4ad Mime-Version: 1.0 Message-Id: Date: Fri, 21 Oct 2022 15:54:07 +0200 From: "Niels Bom" To: pgsql-docs@lists.postgresql.org Subject: Usability ideas: text width and headers that are links Content-Type: text/plain List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi! I have 2 small ideas to improve the usability of the PostgreSQL documentation. I'm looking at v15 (1) mostly. Idea 1: Give the text width of the main content a max width. Idea 2: Each h3 and h4 element should be a link pointing to the nearest parent section with an id. This makes deeplinking to specific parts of a page easier. This prevents people from having to scroll to the top, find out which table-of-content-link they have to click to get the deeplink of where they wanted to link. This is actually quite a common pattern. See the Python docs (2) and the Mozilla docs (3) as examples. The pattern on those sites is even a little nicer by showing an icon on hover. I've created a user script (4) to do this in my browser. You can test it with the Tampermonkey browser extension. I'd <3 to hear your thoughts. Cheers, Niels 1: https://www.postgresql.org/docs/15/index.html 2: https://docs.python.org/3/library/stdtypes.html#dictionary-view-objects 3: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/reduce#description 4: https://github.com/nielsbom/tampermonkey_scripts/blob/main/scripts/postgresql.org.js