@@ -241,7 +241,7 @@ All of the generated message types have instances of
241241[`Generic`](https://pursuit.purescript.org/packages/purescript-generics-rep/docs/Data.Generic.Rep#t:Generic),
242242[`NewType`](https://pursuit.purescript.org/packages/purescript-newtype/docs/Data.Newtype#t:Newtype).
243243
244−### Examples
244+### Usage Examples
245245
246246The __purescript-protobuf__ repository contains three executable *Node.js*
247247programs which use code generated by __purescript-protobuf__. Refer to these
@@ -256,6 +256,11 @@ for further examples of how to use the generated code.
2562563. The Google
257257 [conformance test program](https://github.com/xc-jp/purescript-protobuf/blob/master/conformance/Main.purs)
258258
259+The [Protobuf Decoder Explainer](http://jamesdbrock.github.io/protobuf-decoder-explainer/) shows an
260+example of how to use this library to parse binary protobuf when we don’t
261+have access to the `.proto` descriptor schema file and can’t generate code
262+to read messages.
263+
259264### Interpreting invalid encoding parse failures
260265
261266When the decode parser encounters an invalid encoding in the protobuf input