From: Michael Tremer <michael.tremer@ipfire.org>
To: ipfire-artwork@lists.ipfire.org
Subject: Re: [IPFire Artwork] Blog aka Planet
Date: Wed, 30 May 2018 12:19:19 +0100 [thread overview]
Message-ID: <f28a17f561ee9c5106a4526ac736ba836ffb5ab9.camel@ipfire.org> (raw)
In-Reply-To: <CAPxcDEvhbLenmZ4Az+tTv4Xb14Xty8Rt+5jmMFgJ062tp72zQQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2317 bytes --]
Hey Maurice,
thanks again for moving this forward.
On Wed, 2018-05-30 at 00:04 +0200, Maurice Gesswein wrote:
> Hey folks,
>
> just want to let you know that I'm alive and added WIP (Work In Progress.
> Sven, please don't start with coding yet) Screens of the Blog at Zeplin
> - https://app.zeplin.io/project/58cb0217f2317d48c7a802f2/dashboard?seid=5b0dc8
> 89d80aa1886ae77309
This looks good.
One comment about my first impression: Isn't it a bit dark when the background
isn't white? I don't find it bad or anything, just unexpected.
> I discovered 4 different locations where a blog article appears:
> https://planet.ipfire.org/
> https://planet.ipfire.org/post/ipfire-2-19-core-update-120-is-available-for-te
> sting
> https://www.ipfire.org/news/ipfire-2-19-core-update-118-released
> https://downloads.ipfire.org/release/ipfire-2.19-core120
> Did I catch them all or are there more?
No, I think that is all.
But I would suggest to remove the new article on the download page. That makes
it very long to scroll and nobody is looking for that content there anyways. We
should rather have a link to the news article and that keeps the page cleaner
and we can make it serve only one purpose: Downloading the right file.
> My goal is to provide only one version of an article which can be used for
> each destination. Which is already almost the case.
Yes, the code that generates the HTML out of the markup just generates one
version. However, this is quite confusing with headline sizes and so on now. It
doesn't fit too well at the moment.
> For the future we should think about merging all those separated subdomains
> into one piece of website with a new navigation structure. I don't think they
> need to be technically merged together. Just one single navigation which can
> handle lots of links should do the trick.
We can get rid of downloads.ipfire.org. The initial purpose of that was to have
some sort of an archive with all historic downloads, but that can as well be
realised on the main page.
I think blog.ipfire.org should be an extra subdomain so people see what
something is about only by looking at the URL.
Is there a reason that I have missed why this should all be merged together?
Best,
-Michael
>
> Best,
> Maurice
next parent reply other threads:[~2018-05-30 11:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPxcDEvhbLenmZ4Az+tTv4Xb14Xty8Rt+5jmMFgJ062tp72zQQ@mail.gmail.com>
2018-05-30 11:19 ` Michael Tremer [this message]
[not found] <CAPxcDEtGq-7SK6oSABRZv=WqOQvKwA5SzNqNgVoFzsryE1NeqQ@mail.gmail.com>
2018-06-13 10:02 ` Michael Tremer
[not found] <CAPxcDEuR7=pNfcAZwK9dLG-BRxKck9twCg7hw=E-dEas=6c7eA@mail.gmail.com>
2018-06-13 21:40 ` Michael Tremer
[not found] <CAPxcDEs--sfWM7bLDcAJW_oc=6-+wzBOgZD0cz4eiE=EUsrCww@mail.gmail.com>
2018-06-17 21:06 ` 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=f28a17f561ee9c5106a4526ac736ba836ffb5ab9.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