Grep instructions append may need a visible header

BNAndras · May 25, 2026, 5:37pm

Grep in Go on Exercism transitions abruptly from the end of the instructions to the instructions append. Without a visible header, the append seems like it’s related to the flags specifically, but it’s covering track-specific details for the entire exercise. Perhaps there should be a “Go-specific Instructions” header or something for the append along those lines?

IsaacG · May 25, 2026, 6:08pm

Want to PR one?

BNAndras · May 25, 2026, 6:28pm

Sure. Would it be worth doing a sweep through all the appends and making sure there’s no abrupt transitions like the one here? I don’t think we necessarily need an extra header in every case.

glennj · May 25, 2026, 6:45pm

Recall that every markdown file needs a level 1 header, but the L1 header for the append files are ignored.

BNAndras · May 25, 2026, 7:31pm

Yeah, I’m thinking something like this append on the Arturo track.

github.com

exercism/arturo/blob/f9e9bb7fb633eb9611c700e5ec4da28e33f2b5c6/exercises/practice/etl/.docs/instructions.append.md?plain=1#L3


      
          # Instructions append
          
          ## `Print` does not quote string values
          
          This exercise involves manipulating numeric scores.
          #[a: 1]` and `#[a: "1"]` are not the same:
          
          ```arturo
          inspect #[a: 1]
          ; [ :dictionary
          ;        a  :        1 :integer
          ; ]

IsaacG · May 25, 2026, 8:18pm

I did a batch PR => Ensure all `instructions.append.md` use an H1 and H2 by IsaacG · Pull Request #3140 · exercism/go · GitHub

I suspect something similar would be helpful in other tracks, too.

IsaacG · May 25, 2026, 11:23pm