public inbox for ipfire-artwork@lists.ipfire.org
 help / color / mirror / Atom feed
From: Sven <sven.hoehn@posteo.de>
To: ipfire-artwork@lists.ipfire.org
Subject: [IPFire Artwork] Questions for the CSS based on the mockup and technical question related to Server and GIT
Date: Tue, 28 Mar 2017 22:32:45 +0200	[thread overview]
Message-ID: <DA553174-DD94-46C8-BD20-3440DAE720D6@posteo.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 1169 bytes --]

Hello,
I have some questions:

What is the base-font size? 16px (SM) or 20px (M)?

It is okay if I use rem for the font-size? (It’s the default in bootstrap).

How we handle the headings do we use h1-h6 with given sizes or are the sizes defined via classes 4xl-xs?
(Keine Ahnung ob das so zu verstehen ist. Also meine Frage ist ob wir für die Überschriften die Schriftgrößen bei H1-H6 definieren oder wir die Größen über Klassen festlegen also 4xl-xs?)

What are the fallback fonts? Ubuntu, “Helvetica Neue”, Arial, sans-serif?

The grid is the default Bootstrap Grid (12 columns) with a padding of 24px instead of the default 30px?

Do we use the color naming from the Zeplin Project or a semantic color naming like brand-primary, brand-info etc.?

If I create a note file for myself, do I also put this file on git?

How often do you want me to submit the work, is once a day enough?

I’m not familiar with the Python webserver it is better to serve less files (like in HTTP) or more small files (like in HTTP/2)?

Can I remove all the HTTP prefixes in the template file and put only //. At the moment both methods are used.



             reply	other threads:[~2017-03-28 20:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-28 20:32 Sven [this message]
     [not found] <CAPxcDEvJ82Aq_OpMRZeK3BNUv7nCo1bRzGDMD1y=jzNhUs8zPA@mail.gmail.com>
2017-03-29 11:54 ` Michael Tremer

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=DA553174-DD94-46C8-BD20-3440DAE720D6@posteo.de \
    --to=sven.hoehn@posteo.de \
    --cc=ipfire-artwork@lists.ipfire.org \
    /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