ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Taco Hoekwater <taco@elvenkind.com>
Subject: Re: New logo proposal
Date: Tue, 29 Jan 2019 17:26:19 +0100	[thread overview]
Message-ID: <f31c1803-99b3-871e-70ca-45ce48159be7@xs4all.nl> (raw)
In-Reply-To: <2A093B57-4D12-490C-9D29-0D61D82DA23D@elvenkind.com>

On 1/29/2019 11:32 AM, Taco Hoekwater wrote:
> Hi Paul,
> 
> Nice idea, and I actually like the multi-color version although it is a
> bit too informal for some uses (but could be nice for the wiki).

which brings us to the wiki ... which still needs a bit more fancy css ...

> It would be more coherent if the color of the squares and the color of
> the letters trailed each other around the 7 options in the writing order
> for the word “CONTEXT” (C = orange+blue, O = blue+green, N = green+red
> etc.) But perhaps that is not what you wanted?
> 
> On the blue logo I tried a little experiment myself, using the
> colors of http://group.contextgarden.net:
> 
> 
> 
> WDYT?
> 
> Side note: I like what gitlab does with the logo in the circle crop
> for its project icon. I believe it would be neat if that could be
> formalised into the logo itself, but a simple circle crop does not
> quite look right, and more advanced options like distorting the actual
> squares are outside of my inkscape knowledge. And it may not look
> that good in the end, anyway …
> 
> I’ll be pleased to replace the current green logo on the wiki with
> your multi-color one, assuming there is a some agreement and no
> strong objections.
> 
> Best wishes,
> Taco
> 
> 
>> On 29 Jan 2019, at 00:18, Paul Schalck <schickele@web.de 
>> <mailto:schickele@web.de>> wrote:
>>
>> Dear ConTeXt users and developers,
>>
>> I want to submit a new ConTeXt logo to you (link to GitLab project):
>>
>> https://gitlab.com/schickele/new-context-logo
>>
>> I made this logo in February 2018. At the time, I was planning to do 
>> some video tutorials on ConTeXt (still work in progress), and I wanted 
>> a nice looking visual clue for the thumbnails. Recently, I made a few 
>> minor tweaks and thought it would be the right time to put it out there.
>>
>> The logo comes in two different layouts (hexagonal and horizontal), 
>> and each layout comes in two color variations (multicolored and blue).
>>
>> The hexagonal layout is borrowed from the unofficial ConTeXt logo that 
>> has been around for some time. I like the idea of a clean geometrical 
>> form, and the hexagon reminds me of chemistry formulas -- one of the 
>> many application fields of ConTeXt.
>>
>> The seven colors have mainly an esthetic purpose. They also denote the 
>> flexibility of ConTeXt. I've added a monochromatic blue version 
>> because shiny, saturated colors are not suitable for every case, and 
>> blue is strongly associated with ConTeXt to me. Blue is also a 
>> reminder of Mark IV and LuaTeX.
>>
>> The letters are set in Din17 EF, which I've licensed. I like its 
>> simple shapes combined with a round and soft touch. It avoids 
>> consciously the very connoted Computer Modern and can be seen as a 
>> modernized and also Europeanized interpretation of the TeX tradition.
>>
>> This logo is just a humble proposal. Perhaps it is of some use to 
>> someone. It could also make someone else want to create and share his 
>> or her logo -- that would be great.
>>
>> I'm using ConTeXt since 2006/07 for almost everything that contains 
>> text: letters, presentations, invitations, résumés, certificates, 
>> manuals, reports, flyers, university papers, book typesetting, 
>> exercise sheets, song sheets, and I'm still amazed by how powerful, 
>> flexible and reliable it is. Thanks to the whole community -- and 
>> particularly to the Dutch wizard -- for making this possible!
>>
>> Greetings from Leimen, Germany
>>
>> Paul Schalck
>> ___________________________________________________________________________________
>> If your question is of interest to others as well, please add an entry 
>> to the Wiki!
>>
>> maillist : ntg-context@ntg.nl / 
>> http://www.ntg.nl/mailman/listinfo/ntg-context
>> webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
>> archive  : https://bitbucket.org/phg/context-mirror/commits/
>> wiki     : http://contextgarden.net
>> ___________________________________________________________________________________
> 
> Taco Hoekwater
> Elvenkind BV
> 
> 
> 
> 
> 
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
> 
> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
> archive  : https://bitbucket.org/phg/context-mirror/commits/
> wiki     : http://contextgarden.net
> ___________________________________________________________________________________
> 


-- 

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2019-01-29 16:26 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-28 23:18 Paul Schalck
2019-01-29 10:32 ` Taco Hoekwater
2019-01-29 16:26   ` Hans Hagen [this message]
2019-01-29 17:30   ` Alan Braslau
2019-01-30 12:50   ` Willi Egger
2019-01-30 15:14     ` Thomas A. Schmitz
2019-01-30 16:34     ` mf
2019-01-29 10:42 ` Clyde Johnston
2019-01-29 11:44   ` Floris van Manen
2019-01-29 11:52     ` Hans Hagen
     [not found]       ` <01CB743F-2750-42C8-B8A6-0C09E6DAF5CB@klankschap.nl>
     [not found]         ` <0fb9e8d6-3a4d-cb4a-8f9f-017e08c827f0@xs4all.nl>
     [not found]           ` <9D47C6C4-D5C3-4EA0-8220-6D33BD1E84C6@klankschap.nl>
2019-01-29 14:31             ` Hans Hagen
2019-01-29 16:25   ` Hans Hagen
2019-01-31 20:14 ` Henri Menke
2019-01-29 18:58 Paul Schalck
2019-01-30  9:10 ` Floris van Manen
2019-01-30  9:15 ` Floris van Manen
2019-01-30  9:20   ` Taco Hoekwater
2019-01-30  9:31   ` Taco Hoekwater
2019-01-30 15:02     ` Hans Hagen
2019-01-30 15:32       ` Arthur Reutenauer
2019-01-30  9:34   ` luigi scarso
2019-01-30 10:09     ` Floris van Manen
2019-01-30 20:04       ` Henning Hraban Ramm
2019-01-30 10:11 ` Procházka Lukáš Ing.
2019-01-30 15:02 ` Alan Braslau
2019-01-30 13:00 Paul Schalck
2019-01-30 18:51 ` Lars
2019-01-30 20:11 ` Henning Hraban Ramm
2019-01-30 19:57 Paul Schalck
2019-01-30 22:06 ` Hans Åberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f31c1803-99b3-871e-70ca-45ce48159be7@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --cc=ntg-context@ntg.nl \
    --cc=taco@elvenkind.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).