Usability Team

About

Configuration

EM

Install

Log

"HelveticaNeue" / "Helvetica Neue" / Helvetica / Arial …
to become more condensed?

I like the idea too.

But we need to adjust the bodytext font too. (Jens)

"HelveticaNeue" / "Helvetica Neue" / Helvetica / Arial … (Felix)

Helvetica fonts in a nutshell http://www.myfonts.com/fonts/adobe/helvetica-neue/

But I am not a font advisor myself...

I think we a 100% free font with a good char. support.
Helvetica Neue is sadly not free - and by default, only
on Macs available. I will try to come up with a suggestion.

Greez Jens

Hey Jens, anything new with the fonts?
WOuld like to get this feature into 6.0 to at least make the backend a bit different from the previous versions.

@see
http://typo3.org/the-brand/style-guide/the-typo3-layout-rules/
What about using the same typography as on typo3.org?

Patch set 1 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/20654

For a backend of a CMS the font choice is a tricky thing. A font needs a few characteristics:
- each glyph must be easy distinguishable from others; especially 0oO, Il1, etc. (old-style figures are often a problem)
- it must be readable at relatively small font sizes; a large x-height such as in Verdana helps
- it must be optimized for screens (not everybody has retina displays); see glyphs like ({[]}),.;:
- it must have enough glyphs to use in all BE languages

Taking into account that not all every OS has the same render engine (Apple and Microsoft support TrueType hinting, but Linux doesn't because of patent issues) we should probably select a font for each OS that meets the demands. Rather than looking at a nice design or a style guide, it's more important that BE users can actually read what is displayed. They shouldn't have to guess whether it says l10n or I10n or l1On, etc.

Maybe we can find a suitable web font on www.fontsquirrel.com that has a suitable license, readable glyphs and renders well on various devices?
For serif fonts Gentium is a nice free font with loads of Unicode characters. http://scripts.sil.org/cms/scripts/page.php?item_id=Gentium

Hi,

first of all, sorry that I didn't proceeded this topic any further - as I promised.

Right now I don't think we found a solution. And beside of "Arial" instead of
"Verdana", I don't see any further information at the cur. TYPO3.org Layout.
And I don't find a description of how the bodytext should be like in the "CD-Manual".
Here? http://typo3.org/the-brand/style-guide/the-typo3-font/ Or where? :)

But I have to say, that I would be fine with just Arial and Share in the Backend.
What do you think? :)

Greez Jens

Patch set 2 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/20654

I really like the idea to replace Verdana with Arial - as a system font there should be no problems anywhere on the world.
Shall we add support for Helvetica/Helvetica Neue — if available on system?

To define typography; line-heights and spacings I would like to prepare an empty style-guide extension.
Is that a good start?

Please, please let us get this done for 6.2 since the style will accompany us for several years :)

Patch set 3 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/20654

Patch set 4 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/20654

Absolutely.

Typographie without padding/margins will be complicated.
Could you define new typographie for the body?

P / ~13-14px
H1 / ~24px
H2 > H3 between

Table-Texts and Module+Menu with page tree.

Patch set 5 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/20654

Patch set 6 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/20654

TYPO3 Backend Styleguide (alpha)
Created the spark for a backend module styleguide. —

https://github.com/7elix/TYPO3.CMS.Styleguide
http://typo3.org/extensions/repository/view/styleguide

Lots of styles need to be defined.

Nice. ;)

Before hand I would like to see content been addad in the wikl Backend_Styleguide.
Maybe we could kickstart this at the next RL Meeting.

Greez Jens

Felix: Please don't refer to issues from the Usability team tracker in our commit messages. Workflow should be:

Discuss with the UX/Design guys here. Once approved, create a related issue in the TYPO3 CMS tracker, holding a reference to the UX-issue. The implementation and commit should then refer to the TYPO3 CMS issue number.

Other than that, we still have the issue of checking the LICENSE of the Share font, if it is allowed to simply include it in our GPLv2 product, as I have mentioned in the review process.

I've opened an issue in the Licesing Team (#48420) in order for them to figure it out. I guess it won't be a problem.

Meanwhile, I guess this issue can be closed too, as the "Styleguide" discussion is getting a bit off-topic. ;)