Allow regular posts' js features in published pages

Contribute Feature

AI-generated summary

Canapin advocates for enabling most or all JavaScript features available in regular posts on published pages, citing a better user experience for reading content like image viewers, interactive footnotes, and table of contents. They reference previous discussions on the topic and explain their use case: publishing public software guides on a private instance, where these features would enhance readability and reader experience.

1

This has been discussed widely across various categories, and users have asked for certain features specifically to be enabled in published pages[1][2][3][4], but my wish is that most if all js features users have access to in regular posts should be available for published pages.

It would create a way better user experience to have features such as the image viewer, dates, interactive footnotes, table of contents, etc… When reading a published page.

I suppose there’s a good technical reason why all those features are unavailable for published pages, and I reckon this is not a very commonly used feature, but well, here’s my voice anyway. :slight_smile:

My use case of page-publishing is that I have a private instance, which I sometimes use to publish public software guides. These guides would look and read better if I had access to those features, and would benefits the readers’ experience.

  1. Image Lightboxing and arrowkey control for Published Pages ↩︎

  2. Adding DiscoTOC to Published Pages ↩︎

  3. Does Mermaid work in published pages? ↩︎

  4. Image Lightboxing and arrowkey control for Published Pages ↩︎

2 Likes
Page Publishing CSS