[IPFire Artwork] Bootstrap 4.1
maurice.gesswein at ipfire.org
Mon Jul 30 23:03:59 BST 2018
We are all interested in the best possible outcome.
*Sven*, for which parts of the IPFire Website did you need to override a
lot of defaults and made the code pretty complex? I assume the following:
- Always fullscreen background-image at the top of the page
- Burger menu which slides in from the left
- Left sidebar at the e.g. Features page and Blog
- Especially in smartphone viewport
- Main navigation (top bar)
Should we use the default BS component for those parts? Are there anything
What about the "responsive fluid" layout instead of the adaptive layout (BS
default)? Should we switch to adaptive? Would this make it significant
simpler and more compatible?
*Michael*, thanks for Wekan.
I am a little bit lost regarding what is so bad about this. It is not
> pixel-perfect but I did not consider this to be a huge step back.
I see tons of minor and a couple of major things who broke. I could just
point you to Zeplin and say "please compare and fix it" ;) Every pixel is
documented there. But I think the primary goal of the website has changed a
bit. That's why I suggested to use default BS components.
On Mon, Jul 30, 2018 at 5:32 PM Michael Tremer <michael.tremer at ipfire.org>
> On Sun, 2018-07-29 at 00:52 +0200, Maurice Gesswein wrote:
> > Hey all,
> > I'll try to make it fast and direct. No negativ criticism or rude
> meanings are
> > included and I really enjoy to be part of the IPFire project.
> Please say what you need to say. We are all interested in the best possible
> outcome. Review of what has been done so far is important to make us
> better as a
> > As we all know since the upgrade to BS4.1 tons of UI related things
> broke or
> > changed back to default behaviors at the new IPFire Website. Are we
> willing to
> > go the extra mile again to customize BS to the UI-design I designed or
> do we
> > want to switch to the default BS theme, just do some adjustments and be
> > in a proper timeframe?
> I thought this would be the better path in the long-term. We will just be
> to import CSS fixes from Bootstrap and we have it all customized to what we
> Maybe I broke more as I intended and maybe this wasn't the best path to
> roll the
> website out as soon as possible. But at least I think this is the best way
> forwarding thinking long-term.
> As I said before, I haven't been polishing the mobile viewports too much
> yet and
> I severely broke the background image. Oops :) I wanted to collect some
> and then I will sort them out all in one go.
> > To be honest, I don't want to spend time and energy to think about how to
> > merge the status quo of dev.ipfire.org to the planned new website
> design with
> > a lot of QA work I actually already did.
> Anything else that you suggest?
> I am a little bit lost regarding what is so bad about this. It is not
> perfect but I did not consider this to be a huge step back.
> > Brainwork for the future:
> > When it comes to the WUI of IPFire, please think very careful if you
> want to
> > use BS as well. I prefer to go with CSSGrid and e.g. React if you want
> to have
> > something unique, modern and very mobile friendly.
> Yes, it looks like Bootstrap is kind of a large framework for things like
> Customizing it is possible, but only within a certain range.
> > Taskboard:
> > Please setup Wekan asap and create todos which are currently spread out
> > different mail threads. As I already wrote, I enjoy to do the UI und UX
> > for IPFire and really want that IPFire will stand out from their
> > some day, but I don't want to do a lot of orga stuff. A bit of orga
> stuff on
> > my side is totally fine and expected. Please support me in that. Such a
> > will make us a lot more productive and transparent.
> It's up: https://wekan.ipfire.org/
> You can register and then I can give you admin rights or what ever is
> needed to
> create the items that you need.
> > Best, Maurice
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the IPFire-Artwork