https://blog.pgxn.org/tags/site/Site2026-09-08T22:12:29ZThe PGXN MaintainersHugohttps://blog.pgxn.org/post/827227334118604800Inter-documentation and image links now work on PGXN2026-10-07T16:13:48Z2026-09-08T22:12:29ZDavid E. WheelerFrom the Department of It’s About Time: Inter-documentation and image links now work on PGXN.Way back in 2015, I opened a PGXN API issue to allow links between documents rendered by PGXN to work. In 2024 I followed up with another issue to enable relative links to images to work. I mean, everyone wants this, right? It’s how your favorite source code sit works.

Now so does PGXN. As of today, links between documents and to images work. Check it out in the newly-released chdb extension docs, which both link to the chdb and chdb_hook docs and to some nice benchmark graphs.

Or see the Apache Age docs, which includes not only documentation images but also decorative SVGs for the headers.

I’m gradually reindexing all of the extensions so that any other documentation with such links work work; it should be done by tomorrow. Then, at along last, your extensions can look their very best.

]]>https://blog.pgxn.org/post/4601750614It’s Finally Up: The New PGXN Site!2026-10-07T16:13:48Z2011-04-14T06:32:06ZDavid E. WheelerI’m pleased to announce that the new PGXN SITE went live last night. Some of the things it does:

  • Full text search of all documentation, distribution metadata and READMEs, extensions metadata, and users
  • list of the 56 most recent uploads
  • Find users by first letter of nickname (mostly so search spiders can drill down to all site content)
  • A tag cloud with the 56 most commonly-used tags (they’re all the same size and color right now because each one is used only once at the moment)
  • Pages for users (example)
  • Pages for distributions, with inlined README (example)
  • Browse unzipped distributions (example)
  • Pages for documentation (example)
  • Permalinks for extensions example)

The entire site is backed by the API Server, which is mainly composed of static JSON and HTML files read by the site back end from the local file system. So the site is quite fast. Please browse around, let me know what you think, and please report any bugs you find.

]]>I’m pleased to announce that the new PGXN SITE went live last night. Some of the things it does:

  • Full text search of all documentation, distribution metadata and READMEs, extensions metadata, and users
  • list of the 56 most recent uploads
  • Find users by first letter of nickname (mostly so search spiders can drill down to all site content)
  • A tag cloud with the 56 most commonly-used tags (they’re all the same size and color right now because each one is used only once at the moment)
  • Pages for users (example)
  • Pages for distributions, with inlined README (example)
  • Browse unzipped distributions (example)
  • Pages for documentation (example)
  • Permalinks for extensions example)

The entire site is backed by the API Server, which is mainly composed of static JSON and HTML files read by the site back end from the local file system. So the site is quite fast. Please browse around, let me know what you think, and please report any bugs you find.

There are a few more things left to do on my list:

  • Add pages for users who don’t yet have distributions on the network.
  • Convert the localization interface to gettext and solicit translations.
  • Document the API; might lead to some changes as I run across inconsistencies.
  • Add an Atom feed of recent releases.
  • Add aliases for $nickname@pgxn.org addresses, to forward to personal addresses; this way we can just publish pgxn.org addresses.
  • Write documentation on how to optimize distributions for optimal exposure on PGXN.
  • Consider changing the Permalink URL to something shorter. Suggestions?

If you’d liked to help out with any of these tasks, just let me know. Better yet, grab the source from GitHub and just hack!

Oh, and speaking of the source, I would really appreciate a code review or four. Although I have solicited advice on key questions fro people more knowledgeable than I (thanks Aristotle, Miyagawa, Andreas, Graham), the code is entirely my own. More eyes will be a huge help!

Tomorrow I’ll blog a bit about the architecture for the network. I’m quite happy with it.

]]>