Link to Slack dead, is Slack still used?
Hi, On https://www.postgresql.org/list/pgsql-docs/ under the "Quick links" on the left I see this link https://postgres-slack.herokuapp.com/ but that app seems to be offline. Is Slack used by the PostgreSQL docs community? If so: can somebody please update this link? If no: shall we remove that link? Have a good one, -Ni
[PATCH] fix dead link to Homebrew
Hi, This is the first time I'm doing open source version control with patches so please tell me if I can improve something. I found a dead link on this page: https://www.postgresql.org/download/macosx/ Cheers, -Ni homebrew_dead_link.patch Description: Binary data
Re: Link to Slack dead, is Slack still used?
On Fri, Jul 14, 2023, at 17:16, Douglas A. Whitfield wrote: > Looks like this is the https://postgresteam.slack.com/signup#/domain-signup The link you gave only allows access to people who have an @pgtreats.info email address. It should be possible to generate an invite link for any domain. It’s good to know that those are often capped to either n signups or valid for m amount of time. Could you please generate an all-domains invite link if you have permission to? > > > On Fri, 14 Jul 2023 at 08:49, Douglas A. Whitfield > wrote: >> Yes, we still use slack, but as for who has access to update that page, I do >> not know. I may be able to invite you though. I have a customer call in just >> a few minutes, but I'll see if I can figure out the invites once I get a >> free minute. >> >> >> On Fri, 14 Jul 2023 at 07:10, Niels Bom wrote: >>> Hi, >>> >>> On https://www.postgresql.org/list/pgsql-docs/ under the "Quick links" on >>> the left I see this link https://postgres-slack.herokuapp.com/ but that app >>> seems to be offline. >>> >>> Is Slack used by the PostgreSQL docs community? >>> If so: can somebody please update this link? >>> If no: shall we remove that link? >>> >>> Have a good one, >>> >>> -Ni >>> >>>
Re: Link to Slack dead, is Slack still used?
On Fri, Jul 14, 2023, at 20:27, Douglas A. Whitfield wrote: > In any case, it looks like you already got an invite from someone based > on the message I got when I tried to invite you. > I didn’t get an email, but I’m in after trying again. Thanks!
Usability ideas: text width and headers that are links
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
Re: Usability ideas: text width and headers that are links
On Fri, Oct 21, 2022, at 17:42, Jonathan S. Katz wrote: > Hi, > > Thanks for the suggestions. Comments inline: > > On 10/21/22 9:54 AM, Niels Bom wrote: >> 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. > > Why? Can you please provide examples? Screenshots are OK. Setting a max-width on regular textual content is good for readability, which in turn increases accessibility. See this W3C a11y documentation (1) and an a11y page by the US government (2) for more detailed info. Using the CSS max-width property makes narrower sizes possible (for smaller screens) but sets an upper limit. The newer `ch` unit in CSS is a good-enough approximation of the average width of a character. I've seen 66ch as the "ideal" width for regular text. For the docs code examples need to have enough width too of course. But we can have those be wider than their containing element if need be. 1: https://www.w3.org/WAI/tutorials/page-structure/styling/ 2: https://accessibility.digital.gov/visual-design/typography/ > >> 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. > > This has been on my backlog for awhile, i.e. to have the hovering > "anchor holders". I'll try to move it up on the list. Cool! I could help if you want to. > > Thanks, > > Jonathan > > > Attachments: > * OpenPGP_signature
