I'm merging your two answers in one.
>> So I procrastinated for about one hour on removing the subtitle from our
>> canonical logo. This allowed me then to reuse it as such in the banner
>> and have the exact same version work on mobile as well. We're down from
>> 3 variations to 1!
>>
>> I pushed that in feature/smallCSSfixes.
>>
>> Tell me what you think.
>>
>> The ticket about removing the subtitle from the logo: #14835.
>> But I'll raise the issue on tails-project@ as well.
>>
>> And regarding your branch, I'm fine merging it once we agree on
>> something regarding the logo (or even before if you think it will be a
>> complicated discussion).
>
> I find it quite problematic to have this discussion now :( I really
> don't want this to stop us from launching our donation campaign. So
> let's please not do that.
Ok, so I'm backing off. It was pretentious to me to think that my
modifications to the logo would be easier to approve than yours :)
I push --force (yeah!) a new version of the branch to origin without
these changes.
> It's been way too complicated already to make
> some tiny CSS fixes. Not only is my build wiki setup problematic, but
> every time we start moving something somewhere, new issues come up, and
> ground discussions are ignited which makes it very very hard for me to
> keep my motivation when waiting and working for over three weeks to get
> some lines of CSS merged.
Yeap. As a workflow recommendation, it's good to always be careful about
what kind of changes can be controversial (hint: logo!), and keep an eye
on which branch is blocking which. Here for example you could probably
have move the more controversial (and not strictly necessary for the
donation campaign) changes in a separate branch.
CSS is notoriously painful to work with in the project because nobody
likes it, our CSS are super messy, ikiwiki is crap in this regard, etc.
It's shitty, I know...
>> So I procrastinated for about one hour on removing the subtitle from
>> our canonical logo. This allowed me then to reuse it as such in the
>> banner and have the exact same version work on mobile as well. We're
>> down from 3 variations to 1!
>>
>> I pushed that in feature/smallCSSfixes.
>>
>> Tell me what you think.
>
> I think it's nice BUT there needs to be more space on top and bottom.
> Stuff needs to breathe.. So please don't add a padding or anything,
> because this will break other stuff I did in the donation banner
> branch, but instead make the image slightly smaller.
>
> Now it's 100px in height and the the whole banner is 114px high. I
> think we need at least 10-15px on top and below, so the logo should
> not be higher than 90px.
>
> Also, what I find weird is that the USB stick is not horizontally
> aligned with the text. You see, the stick is higher than the T and
> lower too. I can live with this.
>
> But I can't live with the missing breathing space.
I'm backing off of this proposal, so I'll instead move these comments of
yours out to #14835 (and away from the donation campaign) and will work
on this more "at some point".
Still, I made a commit on top of your branch to remove the subtitle in
your logo_mobile.png which was the image that I found problematic and
that ignited the ground. After starting the discussion on #14835, I
understand that removing the subtitle in the banner is not very
controversial, so doing this on the mobile version for now is, I
believe, the minimal change that we can do to fix the original issue you
raised, and at the same time, avoid having too many versions of the logo
proliferate, and not introduce too small text.
Again, if this proposal is controversial for you, please ignore it and
merge your branch as of fd6c6b2d86 as soon as you want.
>> And regarding your branch, I'm fine merging it once we agree on
>> something regarding the logo (or even before if you think it will be
>> a complicated discussion).
>>
>> Still, I spotted one little detail (see attachment): in the Farsi
>> version the search box is much taller. I narrowed the problem down to
>> having a bigger line-height in the input field in there (34px instead
>> of 22px reported by Tor Browser). Then I couldn't see where this was
>> coming from... But I think we can ignore that, unless you find a
>> quick way of solving it.
>
> I cannot confirm that I see this. And I think you did not push your
> modification.
My modification was only on the logo and the Farsi bug was already
present in your branch (at least on my machine).
> Please note that in the donation banner branch I did some other
> modifications, like giving a unit to the line-height on body. Which
> was actually never taken into account... because of the missing unit
> :) ANd I think this fixes quite a lot of stuff.
Maybe that's it! Anyway, if you don't see it on your machine and since
it's a minor detail I think we can skip that and see what happens once
this branch is merged ;)
.%0A>%20>%20%0A>%20>%20I%20find%20it%20quite%20problematic%20to%20have%20this%20discussion%20now%20:(%20I%20really%0A>%20>%20don't%20want%20this%20to%20stop%20us%20from%20launching%20our%20donation%20campaign.%20So%0A>%20>%20let's%20please%20not%20do%20that.%0A>%20%0A>%20Ok,%20so%20I'm%20backing%20off.%20It%20was%20pretentious%20to%20me%20to%20think%20that%20my%0A>%20modifications%20to%20the%20logo%20would%20be%20easier%20to%20approve%20than%20yours%20:)%0A>%20%0A>%20I%20push%20--force%20(yeah!)%20a%20new%20version%20of%20the%20branch%20to%20origin%20without%0A>%20these%20changes.%0A>%20%0A>%20>%20It's%20been%20way%20too%20complicated%20already%20to%20make%0A>%20>%20some%20tiny%20CSS%20fixes.%20Not%20only%20is%20my%20build%20wiki%20setup%20problematic,%20but%0A>%20>%20every%20time%20we%20start%20moving%20something%20somewhere,%20new%20issues%20come%20up,%20and%0A>%20>%20ground%20discussions%20are%20ignited%20which%20makes%20it%20very%20very%20hard%20for%20me%20to%0A>%20>%20keep%20my%20motivation%20when%20waiting%20and%20working%20for%20over%20three%20weeks%20to%20get%0A>%20>%20some%20lines%20of%20CSS%20merged.%0A>%20%0A>%20Yeap.%20As%20a%20workflow%20recommendation,%20it's%20good%20to%20always%20be%20careful%20about%0A>%20what%20kind%20of%20changes%20can%20be%20controversial%20(hint:%20logo!),%20and%20keep%20an%20eye%0A>%20on%20which%20branch%20is%20blocking%20which.%20Here%20for%20example%20you%20could%20probably%0A>%20have%20move%20the%20more%20controversial%20(and%20not%20strictly%20necessary%20for%20the%0A>%20donation%20campaign)%20changes%20in%20a%20separate%20branch.%0A>%20%0A>%20CSS%20is%20notoriously%20painful%20to%20work%20with%20in%20the%20project%20because%20nobody%0A>%20likes%20it,%20our%20CSS%20are%20super%20messy,%20ikiwiki%20is%20crap%20in%20this%20regard,%20etc.%0A>%20It's%20shitty,%20I%20know...%0A>%20%0A>%20>>%20So%20I%20procrastinated%20for%20about%20one%20hour%20on%20removing%20the%20subtitle%20from%0A>%20>>%20our%20canonical%20logo.%20This%20allowed%20me%20then%20to%20reuse%20it%20as%20such%20in%20the%0A>%20>>%20banner%20and%20have%20the%20exact%20same%20version%20work%20on%20mobile%20as%20well.%20We're%0A>%20>>%20down%20from%203%20variations%20to%201!%0A>%20>>%0A>%20>>%20I%20pushed%20that%20in%20feature/smallCSSfixes.%0A>%20>>%0A>%20>>%20Tell%20me%20what%20you%20think.%0A>%20>%0A>%20>%20I%20think%20it's%20nice%20BUT%20there%20needs%20to%20be%20more%20space%20on%20top%20and%20bottom.%0A>%20>%20Stuff%20needs%20to%20breathe..%20So%20please%20don't%20add%20a%20padding%20or%20anything,%0A>%20>%20because%20this%20will%20break%20other%20stuff%20I%20did%20in%20the%20donation%20banner%0A>%20>%20branch,%20but%20instead%20make%20the%20image%20slightly%20smaller.%0A>%20>%0A>%20>%20Now%20it's%20100px%20in%20height%20and%20the%20the%20whole%20banner%20is%20114px%20high.%20I%0A>%20>%20think%20we%20need%20at%20least%2010-15px%20on%20top%20and%20below,%20so%20the%20logo%20should%0A>%20>%20not%20be%20higher%20than%2090px.%0A>%20>%0A>%20>%20Also,%20what%20I%20find%20weird%20is%20that%20the%20USB%20stick%20is%20not%20horizontally%0A>%20>%20aligned%20with%20the%20text.%20You%20see,%20the%20stick%20is%20higher%20than%20the%20T%20and%0A>%20>%20lower%20too.%20I%20can%20live%20with%20this.%0A>%20>%0A>%20>%20But%20I%20can't%20live%20with%20the%20missing%20breathing%20space.%0A>%20%0A>%20I'm%20backing%20off%20of%20this%20proposal,%20so%20I'll%20instead%20move%20these%20comments%20of%0A>%20yours%20out%20to%20#14835%20(and%20away%20from%20the%20donation%20campaign)%20and%20will%20work%0A>%20on%20this%20more%20%22at%20some%20point%22.%0A>%20%0A>%20Still,%20I%20made%20a%20commit%20on%20top%20of%20your%20branch%20to%20remove%20the%20subtitle%20in%0A>%20your%20logo_mobile.png%20which%20was%20the%20image%20that%20I%20found%20problematic%20and%0A>%20that%20ignited%20the%20ground.%20After%20starting%20the%20discussion%20on%20#14835,%20I%0A>%20understand%20that%20removing%20the%20subtitle%20in%20the%20banner%20is%20not%20very%0A>%20controversial,%20so%20doing%20this%20on%20the%20mobile%20version%20for%20now%20is,%20I%0A>%20believe,%20the%20minimal%20change%20that%20we%20can%20do%20to%20fix%20the%20original%20issue%20you%0A>%20raised,%20and%20at%20the%20same%20time,%20avoid%20having%20too%20many%20versions%20of%20the%20logo%0A>%20proliferate,%20and%20not%20introduce%20too%20small%20text.%0A>%20%0A>%20Again,%20if%20this%20proposal%20is%20controversial%20for%20you,%20please%20ignore%20it%20and%0A>%20merge%20your%20branch%20as%20of%20fd6c6b2d86%20as%20soon%20as%20you%20want.%0A>%20%0A>%20>>%20And%20regarding%20your%20branch,%20I'm%20fine%20merging%20it%20once%20we%20agree%20on%0A>%20>>%20something%20regarding%20the%20logo%20(or%20even%20before%20if%20you%20think%20it%20will%20be%0A>%20>>%20a%20complicated%20discussion).%0A>%20>>%0A>%20>>%20Still,%20I%20spotted%20one%20little%20detail%20(see%20attachment):%20in%20the%20Farsi%0A>%20>>%20version%20the%20search%20box%20is%20much%20taller.%20I%20narrowed%20the%20problem%20down%20to%0A>%20>>%20having%20a%20bigger%20line-height%20in%20the%20input%20field%20in%20there%20(34px%20instead%0A>%20>>%20of%2022px%20reported%20by%20Tor%20Browser).%20Then%20I%20couldn't%20see%20where%20this%20was%0A>%20>>%20coming%20from...%20But%20I%20think%20we%20can%20ignore%20that,%20unless%20you%20find%20a%0A>%20>>%20quick%20way%20of%20solving%20it.%0A>%20>%0A>%20>%20I%20cannot%20confirm%20that%20I%20see%20this.%20And%20I%20think%20you%20did%20not%20push%20your%0A>%20>%20modification.%0A>%20%0A>%20My%20modification%20was%20only%20on%20the%20logo%20and%20the%20Farsi%20bug%20was%20already%0A>%20present%20in%20your%20branch%20(at%20least%20on%20my%20machine).%0A>%20%0A>%20>%20Please%20note%20that%20in%20the%20donation%20banner%20branch%20I%20did%20some%20other%0A>%20>%20modifications,%20like%20giving%20a%20unit%20to%20the%20line-height%20on%20body.%20Which%0A>%20>%20was%20actually%20never%20taken%20into%20account...%20because%20of%20the%20missing%20unit%0A>%20>%20:)%20ANd%20I%20think%20this%20fixes%20quite%20a%20lot%20of%20stuff.%0A>%20%0A>%20Maybe%20that's%20it!%20Anyway,%20if%20you%20don't%20see%20it%20on%20your%20machine%20and%20since%0A>%20it's%20a%20minor%20detail%20I%20think%20we%20can%20skip%20that%20and%20see%20what%20happens%20once%0A>%20this%20branch%20is%20merged%20;)%0A>%20%0A>%20 "Nachricht beantworten")