From: Michael Tremer <michael.tremer@ipfire.org>
To: ipfire-artwork@lists.ipfire.org
Subject: [IPFire Artwork] Relaunching the ipfire.org website
Date: Sun, 12 Mar 2017 15:35:26 +0000 [thread overview]
Message-ID: <1489332926.10391.65.camel@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2128 bytes --]
Hello everyone,
this list has been inactive for quite a while and I am guilty of not getting
much done what I promised before (apologies), but finally we are getting on with
a few things.
Since Daniel sent out a tweet which asked for help to implement the new website
design, Sven got in touch and me and him had a brief call where we talked about
how he can contribute to that. Luckily, there were not many questions and we are
almost ready to go.
I created a copy of our website repository for him, provided him with an account
and access to the database.
I also gave him links to the designs that Maurice did and he is fairly
optimistic that we will be able to implement everything very quickly.
Step one would be to get a copy of the website running on his development
machine.
Step two is updating everything to Bootstrap 4. It is still under development
but I have used it for some projects and it is stable enough and this is
probably the right time to update.
Step three is then modifying the CSS that is there to match Maurice's styleguide
(it seems that a few things are still missing there, but I hope that we will be
able to figure that out easily).
Step four would be to update the front page.
Step five is to update the features page.
And at that point we see how it goes and if it makes sense to push it out or if
we update the download page and the others right away. There are no designs for
those available, yet. Depending on Maurice's time and availability we will see
what is a good schedule for everything.
Then I would also like to update some of the content on the pages. This is not
necessarily tied to the design because this is nothing major. I just think that
we should update some of the texts and we should also update and add more
screenshots of the web user interface.
So as you can see this is a lot of work and needs many people who help us out
here. Hence I would like to welcome Sven on the team and I hope that everybody
else is helping him out where ever necessary.
Looking forward to hearing from all of you.
Best,
-Michael
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
reply other threads:[~2017-03-12 15:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1489332926.10391.65.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