You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Changes made to the websites field in the speakers json make both contributing and browsing the site confusing.
E.G.: When watching "Henri Tremblay"'s profile on the website, we can now see the following:
Web
Web
Web
@henri_tremblay
while before, each website was clearly specified.
EasyMock
Objenesis
Blog
@henri_tremblay
To me, this change only helps the technical side, unless it's a way for you to force speakers to only specify one "Web" entry.
In that case, we should clean the existing json to force only one entry per category, as an example.
IMO, previous format was better, and it was easy to distinguish websites technically, parsing the URL.
The text was updated successfully, but these errors were encountered:
I used the "Web" as a catch all while I was trying to rewrite the JSON document in a better format. And also because when I started to rewrite the baggers page I started replacing web icons with nice logos like web.png, linkedin.png, github.png so it was easier to have a consistent naming.
I agree that's a bit restrictive though. May be we should try to open more website types, like:
Blog
Pro
OSS
I can also deal with that and solve the rendering issue on my end with some javascript and fallback to web.png any time I can't recognize a given website type.
Changes made to the
websites
field in thespeakers json
make both contributing and browsing the site confusing.E.G.: When watching "Henri Tremblay"'s profile on the website, we can now see the following:
while before, each website was clearly specified.
To me, this change only helps the technical side, unless it's a way for you to force speakers to only specify one "Web" entry.
In that case, we should clean the existing json to force only one entry per category, as an example.
IMO, previous format was better, and it was easy to distinguish websites technically, parsing the URL.
The text was updated successfully, but these errors were encountered: