Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rKRFK-002fM5-GD for pgsql-www@arkaria.postgresql.org; Mon, 01 Jan 2024 22:58:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rKRFJ-00DQUw-4G for pgsql-www@arkaria.postgresql.org; Mon, 01 Jan 2024 22:58:57 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rKRFH-00DQUo-GJ for pgsql-www@lists.postgresql.org; Mon, 01 Jan 2024 22:58:56 +0000 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rKRFD-00DHEd-Ns for pgsql-www@lists.postgresql.org; Mon, 01 Jan 2024 22:58:54 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 7915F5C0158; Mon, 1 Jan 2024 17:58:49 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Mon, 01 Jan 2024 17:58:49 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm1; t=1704149929; x=1704236329; bh=mX22w4Jn+231NdEZW1MiGp3dOvIHxtD1loSa8ZvT+BI=; b= XfcfRg0TzKVz7q8IE4RkuXc5f4vI8g690mBBdWCZs865ytixehI4q6/qjKYBNblL 3StfFt+CUwL11cl61X/OzNnV3jtnnCkhd8iJiTRhdaDRu8wHPzzrCLV1FSkEZSZ3 +O/twtqzgNrTEpGsvwyt/qRNSh+JMB2uKh6H+pWd6Hvm4eX0iycHgEHNW4OKcCo1 xStaBCxzddu5Xjqp33oGqJwuj4fRpUXKu2phOJdwYzZaV7iZR1eRf+xYq+ciNnvI 4VUTPrrmpVTCcJB3g6Iig4dH1xt6KqkiEYWpiVmt9SVA8A2U2TEjQ/dq+X1LO9hn 2CIe/On1U4eq803STebWGw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1704149929; x= 1704236329; bh=mX22w4Jn+231NdEZW1MiGp3dOvIHxtD1loSa8ZvT+BI=; b=b Q1bVBTEwAEn4tFym8HSuEccX1xIiv7tdJv1E1XL9kcdgIBg/1QYhMzfNFFLTqfbc GYBygUdHxGW/XsZWDdceiYmqFKtisSbjCPwG7bBqpdHV8MtFoyZfee+DbZnPEcET 7w+zAH6dZoNBgCb513yPlmlvXOFVWr0241X1i6pmzZpsP9YNxz8Emtg1nHakFYpL 2DfGkBfy57RUp9o+5e0Cm6WR3Y3xsuq9uGpPhok6qm9+dFGHh2rbCemfZVW8QAgZ m9hPLnMzl3KHLeRthyYBvVQBUpCl+RqmLq+cYG1imTVx7NM/Dcgu87S9IVbqpFGg 0HMTN5R+jT6lq8gL6KcGA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrvdeguddgtdeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvvehfhfgjtgfgsehtjeertddtvdejnecuhfhrohhmpeetughr ihgrnhcumfhlrghvvghruceorggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtg homheqnecuggftrfgrthhtvghrnhepveehueffgefhieejffekvedttdfggfeuveduudev geeigfejudelfeeggfeiieetnecuffhomhgrihhnpehpghignhdrohhrghenucevlhhush htvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrughrihgrnhdrkhhl rghvvghrsegrkhhlrghvvghrrdgtohhm X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 1 Jan 2024 17:58:48 -0500 (EST) Message-ID: Date: Mon, 1 Jan 2024 14:58:47 -0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Describing Postgres as "object-relational" on the home page To: "Karl O. Pinc" , "Jonathan S. Katz" Cc: Benjamin Scherrey , pgsql-www@lists.postgresql.org, Vik Fearing , Bruce Momjian , Tom Lane References: <20231226131047.493259f8@slate.karlpinc.com> <20231228135446.3ba508d5@slate.karlpinc.com> <20231231114052.30eccee6@slate.karlpinc.com> <20240101134459.0d23672b@slate.karlpinc.com> Content-Language: en-US From: Adrian Klaver In-Reply-To: <20240101134459.0d23672b@slate.karlpinc.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 1/1/24 11:44, Karl O. Pinc wrote: > On Sun, 31 Dec 2023 14:40:49 -0500 > "Jonathan S. Katz" wrote: >> I don't really follow what you're suggesting here. > > The suggestion here is to first, change the "object-relational" sentence > as has been discussed. (Then, tl,dr; use a interactive "word cloud") > But instead of coming up with wording describing functionality, > workloads, etc., to simply say "PostgrSQL does lots more stuff." on > the home page and link that to a page with nothing but keywords. > The keywords can be linked to descriptions or project pages, > or not. > > That way nobody has to write sentences, and more importantly, nobody > has to maintain much when there's a new hot technology or > figure out what's important enough to put on the home page. Just add > a new keyword to the keywords page. (Especially labor free if > the keyword page is a pg wiki page.) > > To extend this idea, just a list of keywords is not engaging. > Categorizing the keywords by attaching one or more tags to each opens > up possibilities for interaction and alternate ways to view the > keywords. In particular the user can find keywords by tag and so > keywords need not be categorized in a fixed fashion. > This would likely only be interesting if the keywords were linked to > somewhere so that after getting a relevant set of keywords > the reader could follow the links to find information or tools. Please no, this is just another version of word salad. > > In addition to tabular views, the https://pgxn.org sort of view, > a "word cloud", provides a useful overview. In this presentation all > tags are displayed on a single page but the visual presentation > emphasizes those tags that are more important (e.g., occur > with more frequency) by displaying them in a larger font. > In this view, clicking on any tag shows its associated keywords > to facilitate exploration. > (From an implementation perspective it might be simplest if each > keyword was also a tag, so that there's no need to make a distinction > between tags and keywords when searching.) I actually find that visually distracting and more to the point not that useful. When I go to a site I am looking for something that will scratch my itch, not what is popular. A search box and a table of contents generally is all I need. -- Adrian Klaver adrian.klaver@aklaver.com