Daniel Rudolf

My apologies for this late response @aferrop! Unfortunately my time is very limited lately and I still haven't had time to make the changes necessary to Pico's website to support...

> The `pico-theme.yml`'s meta-headers section doesn't seem to support arrays for having multiple levels of depth. Not sure whether this is an oversight or by design. The use case I'd...

> I'd almost wonder if it'd be better to just _standardize_ on lowercase names and convert all the keys to lowercase at runtime. I honestly don't care that much about...

My apologies for this late response @stefanocpp! Unfortunately my time is very limited lately and I still haven't had time to make the changes necessary to Pico's website to support...

What do you mean by "how to make them appear here"? The Travis failure is unrelated to your changes, see https://github.com/picocms/Pico/commit/7c1e8897170e1ec2853fc29c694e8bae0a1d51a2

Looks like you edited files in multiple branches. This pull request is the [`stefanocpp-ita-1` branch](https://github.com/picocms/Pico/compare/master...stefanocpp:stefanocpp-ita-1), but you also edited files in the [`stefanocpp-ita` branch](https://github.com/picocms/Pico/compare/master...stefanocpp:stefanocpp-ita) and [`master` branch](https://github.com/picocms/Pico/compare/master...stefanocpp:master).

I just added PHP strict typing, passing an array to Pico's `markdown` Twig filter will now cause a fatal error. Apart from that I can't really think of additional checks....

What's the sense about marking only visible/loaded entries anyway? Due to infinite scrolling, you can never be sure which entries are actually marked when you're not at the end of...

> In order to clear up this uncertainty, we will need the past contributors to confirm if they are fine with licensing their contribution under GPL 3 or later Yes,...

Yeah, sounds reasonable to me :+1: :smiley: