public inbox for ipfire-artwork@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: ipfire-artwork@lists.ipfire.org
Subject: Re: [IPFire Artwork] Website: Feature page
Date: Fri, 11 Mar 2016 18:23:56 +0000	[thread overview]
Message-ID: <1457720636.6973.187.camel@ipfire.org> (raw)
In-Reply-To: <CAPxcDEttrdO50Esnx_XQrsESNO-WXXerOOqoe3q7szsWmERtDA@mail.gmail.com>

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

Hi,

On Thu, 2016-03-10 at 23:35 +0100, Maurice Gesswein wrote:
> Hey folks,
> 
> I'm very sorry for my late absence. But now I'm able to show you a
> suggestion for the feature/about page :)

Don't worry. I am also still catching up with so many things and didn't
really find the time yet to implement the captive portal stuff. I have
started though. More on that in an other email.

> I'm aware of all the missing content. That screenshot should give you
> a first impression.
> 
> The TOC (table of content) on the left side should be sticky and
> doesn't disappear while you scroll down.
> Example: http://getbootstrap.com/getting-started/#download

Yeah the content is quite outdated. I am not too happy with this at the
moment.

Do you think it is a better idea to have one single long page or
multiple sub-pages?

I like the one long page approach better. We should have shorter texts
there to keep attention of the reader. If we have sub-pages this won't
look like much.

> Since there are a lot of top level points and the list becomes quite
> long you may consider to reorganize it. Personally I like it the way
> Bootstrap does it by using more sub-level points and only show them
> if the parent point is selected. That would save us a bit of space.
> If the browser window is not high enough you don't see the last
> couple of points.
> 
> As always - designs for the mobile views will follow.
> 
> Let me know your thoughts or concerns.

Great as always :)

> 
> Best,
> Maurice

Best,
-Michael

       reply	other threads:[~2016-03-11 18:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAPxcDEttrdO50Esnx_XQrsESNO-WXXerOOqoe3q7szsWmERtDA@mail.gmail.com>
2016-03-11 18:23 ` Michael Tremer [this message]
     [not found] <CAPxcDEsL7BhiS-JoOh2qnoMbw6Y5iQpSmCXY8dFyPYw550VtAw@mail.gmail.com>
2016-03-13 14:19 ` 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=1457720636.6973.187.camel@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --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