To me it seems that this paragraph has no connection to the associated example on the page.

https://purescript-deku.netlify.app/core-concepts/collections#groups-of-groups

While I played around with SSR I wondered if static text could be included in the rendered HTML - I used text_, but I think it's basically the same as in the example:

The reason I ask is that the content of elements affects the arrangement/location of the elements - so if static/constant text could be included in the HTML this would reduce changes during hydration.

Hi, I'm just reading through the documentation in dark mode and I noticed a styling issue.

The right hand "On this page" nav shows headings, with sub-items indented under them. In light mode, these are black, and light blue when viewing. In dark mode, I'm guessing they're supposed to be white and light blue when viewing; but instead they start off as black, but once they're highlighted in blue as viewed, then they revert to white.

At first I thought that there were different styles for read vs. unread headings, and there was an oversight with the dark mode unread style, but I can't see a visible distinction in light mode so I'm guessing it's a subtler bug of some sort.

I've been reading the documentation on Chrome on iOS, and eventually the app gets into what I'm guessing is an infinite loop: nothing is responsive (though pages are still scrollable), and even when I press to refresh, the browser hangs forever with a loading bar, without unloading the page. I have to close the tab and reopen the page in a new tab.

I haven't been able to find a specific trigger for this. It happens intermittently, but seems to happen eventually—after reading through a couple of pages or so.

In Core concepts/collections

A Content Security Policy should be implemented in every opportunity for better site security. For what should be obvious reasons, style-src: unsafe-inline is never recommended. However, the documentation has a number of instance of showing off inline CSS, style_, etc. which will likely require unsafe-inline. This could be seen as "out of scope" for the project, but when enticing users into features, they should be reminded of the any negative trade-offs when present. Technically you can use nonces, but this wildly complicates a build when the simpler option is to just use external CSS.

type Poll a = forall b. Event (a -> b) -> Event a
type SampleOnRight a =
  Event a -> (forall b. Event (a -> b) -> Event a)

Should be

type Poll a = forall b. Event (a -> b) -> Event b
type SampleOnRight a =
  Event a -> (forall b. Event (a -> b) -> Event b)

This change would aid in readability and also just look nicer.

• ... → … / …
• ' → ‘ + ’ / &lsquo + ’
• " → “ + ” / &ldquo + ”

Given there is text in what looks like French possibly with accented characters, there is a precedence to not be limited to ANSI characters. Elements like <q> may also be appropriate.

(I’d push for ∷, →, ∀, but don’t wanna push my luck 😛)

Documentation:
https://purescript-deku.netlify.app/functional-reactive-programming/event-miscellany#events-aren't-monoids

Code:
https://github.com/mikesol/purescript-hyrule/blob/aaff88c817803bcd583386ed91e0c9b835b7cc8c/src/FRP/Event.purs#L199