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 1knT2D-0002ln-0p for pgsql-docs@arkaria.postgresql.org; Thu, 10 Dec 2020 20:59:33 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1knT2B-0003u6-Dr for pgsql-docs@arkaria.postgresql.org; Thu, 10 Dec 2020 20:59:31 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1knT2A-0003tz-DI for pgsql-docs@lists.postgresql.org; Thu, 10 Dec 2020 20:59:31 +0000 Received: from wout3-smtp.messagingengine.com ([64.147.123.19]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1knT23-0007fI-82 for pgsql-docs@lists.postgresql.org; Thu, 10 Dec 2020 20:59:30 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 5D3E191A; Thu, 10 Dec 2020 15:59:19 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Thu, 10 Dec 2020 15:59:19 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:subject:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=iD583IC9c5Y3le2il KIURaT1LyjhapYi6CwSh6DLmlk=; b=EPBZw3KiXRg5KN22nK6VCtUaQlH0YlM47 SjDRqa11mdhjZt/n6She/uxML8pfDgnLOa+JmkZZ+9szgpo9ZVdum2ZdccZWZQIC DpVcOO7EPeR0TGX64ovlX8pBJuMP3rOjC14Hbd6Na/3J82yp/e0g8GxCSngU0fcj szMLrQXIAyrePJAR1OPdRXKMBiVJ0Z9yehj5tdvv20vvlmm652XJgvGwldzgasM+ F4xIIhZAjEQdgrM5pbMU/+fmeTd9VAKPXREtIAtqYGgjcqTFpZJZ+612CWVz9At3 GeYGLU7R05hoFpy2/dy1Gj1QV6A7S/Ys1+5fBh8boekt1KIHjPBSg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrudektddgudeggecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpeffhffvuffkgggtuggjfgesthdtredttdervdenucfhrhhomheptehlvhgr rhhoucfjvghrrhgvrhgruceorghlvhhhvghrrhgvsegrlhhvhhdrnhhoqdhiphdrohhrgh eqnecuggftrfgrthhtvghrnhepvefgleevgeeujeeghfegteeghfegheeifeehheelteet ieduieeihffggfehffetnecukfhppeduledtrdelhedrudekrdejleenucevlhhushhtvg hrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrlhhvhhgvrhhrvgesrghl vhhhrdhnohdqihhprdhorhhg X-ME-Proxy: Received: from perhan.alvh.no-ip.org (unknown [190.95.18.79]) by mail.messagingengine.com (Postfix) with ESMTPA id 7923124005C; Thu, 10 Dec 2020 15:59:18 -0500 (EST) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id E9A032A1530; Thu, 10 Dec 2020 17:59:15 -0300 (-03) Date: Thu, 10 Dec 2020 17:59:15 -0300 From: Alvaro Herrera To: Steven Pousty Cc: pgsql-docs@lists.postgresql.org Subject: Re: The sub-categories do not have anchors on this page Message-ID: <20201210205915.GA16798@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2020-Dec-10, Steven Pousty wrote: > They certainly do at the top of the page, that's why I sent the second > email. I was hoping to have anchors down the page where that actual topic > is. The rational for this is, when I write a blog post, teach a class, help > someone on slack... I can give them the URL right to the section I want > them to read. This anchor would prevent just giving the url to the whole > page and telling them to search for it. Ah -- so what you want is to have something like an icon (typically a chain link icon) that appears next to the title, and points to itself? Many sites do that. I think it's a useful idea and we should consider it, but it's a modification that would be done to the tooling and so it'd affect the whole documentation, not just this page.