As you can see at the screenshot there are some width issues with the repository title.
One option is to move the repo description down near the owner (either above or below). Not sure how that would look.
isn't there a way to set a limit for the width?
I think the location of the description is good. A solution could be to set a padding of like 10 to 15 pixels on both sides and expand the text view down?
@RolfKoenders :+1: Yep that'd work nicely! Is there a character limit for repository descriptions?
@andrewda After trying it with different characters, there is no actual limit on how much you can insert/save. Github is only showing 347 characters before it cuts it of "Loru..."
Alright, then does it make sense to have the text view expand dynamically? Or should we chop it off at a certain point?
I think we should decide on a limit. 1/3 of my iPhone 6(s) Plus screen is filled with the repository description with 347 characters.. Thats to much i think?
Yep I agree (though I don't think there are many repos with huge descriptions). Maybe add an ellipsis after the word before the text reaches ~150 characters?
So we can definitely add some padding on the sides (and we probably should) but super long descriptions can still look funky.
In the list screen long descriptions look fine in my opinion:

But in the repo screen this can be a problem:

So I think we should:
Looks good for me, and cutting after some kind of characters seems fine.
@housseindjirdeh That sounds like a decent solution!
Hi there, I've made some changes to the description style in repo screen, mainly according to what @housseindjirdeh suggested. Looking forward to hearing your feedback 馃槈
@Antondomashnev I haven't checked it yet, but does your PR fixes this issue? It looks like it, except the 150 character limit.
@RolfKoenders yeah, instead of 150 characters limit I introduces the number of lines limit, I think it's better, so if we change the font size of something there will be still 5 lines and maybe less than 150 characters.
Thanks for your awesome fix @Antondomashnev - this is good to close :)
Most helpful comment
Thanks for your awesome fix @Antondomashnev - this is good to close :)