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.
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 live in a proper timeframe?*
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.
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.
Taskboard:
Please setup Wekan asap and create todos which are currently spread out in
different mail threads. As I already wrote, I enjoy to do the UI und UX
part for IPFire and really want that IPFire will stand out from their
competitors 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 board will make us a lot more productive and transparent.
Best, Maurice
Hello,
I want to start a thread on the donation page. When I have been working
on it, I had a few ideas and discovered a few problems with the flow.
So I tried to change them, but am quite unsure if I came to the right
conclusions...
So this page...
https://dev.ipfire.org/donate
...is supposed to encourage people to set up a recurring donation to
the project. We benefit most from smaller regular donations than one-
time donations. Therefore the process should be quick and easy.
We have a few legal requirements which don't make this too easy for us
to design an effortless process. The main issue with that is the
address that we need. We need that to process payment and we will have
to store it for tax records.
This used to be a pop-up before and I moved this to the main box now
because of two reasons:
* We should be up-front that this is a requirement and not surprise
people with the pop-up
* I would like to have a pop-up that encourages people to change their
one-time donation to a monthly one and two pop-ups feel a little bit
annoying.
That makes the main box a little bit large, but I think that at least
it has all steps on it.
Then, I removed the payment methods. This is easier to ask that in the
backend and it would require some changes in the code there to make it
work. We also don't always offer all payment options. Hence it is good
that we know the amount and currency beforehand.
I kept the icons though and moved then underneath the donate button
because we should still show which payment options are potentially
available. Can we add a logo for SEPA here?
I am also considering to remove PayPal entirely. They are just a pain
to deal with and ridiculously expensive. Credit card and SEPA should
cover payments from anywhere in the world and easy and flexible.
After someone has gone through the process, they will receive an email
with a PDF document that contains the SEPA mandate if they have chosen
SEPA. In case of credit card, there won't be any emails.
The bank statements or credit card bill will have a link to the
accounting software to end any recurring donations. I have considered
sending a thank you email with a link, but people would loose it.
Sending an email every time we take a payment is very annoying.
Then, there is the pop-up to think about. I have no idea what that
could look like. It should be nice and ask if the user would prefer to
do a monthly donation of the amount that they have selected divided by
four. So we should make a suggestion and make it one click to make it
recurring. There should also be a "no thanks" option that just
continues with the one-time payment.
Potentially we won't show the pop-up for donations that are 10 EUR or
USD. It doesn't make too much sense to break them into smaller monthly
payments.
Does anyone have any ideas for a good wording?
Finally, I changed the split layout because it didn't feel natural to
me to either fill in one or the other side to pick an amount to donate.
Although there was a big "OR", I am personally happier with having
those aligned from top to bottom. Comments?
So that's it for now. I will hopefully find some time next week to
write the texts for that page and maybe others. It doesn't come very
natural to me, but I will give it a try. Hopefully we will be able to
tell what the final shape of the page is going to be.
Best,
-Michael
Hello,
I would like to ask a few questions about the static pages that we have. I am
not sure what I should do with them content-wise and I hope that a bit more
clarity about what they will look like might help.
So, we have one big page which is a bit special which is the features page:
https://dev.ipfire.org/features
This one is a bit special in that sense that it has a lot of content and even
needs a navigation bar. One of my initial thoughts was that it needs to be split
up, but since the design works so well and it is not supposed to be that long
the content needs to be shortened, screenshots need to be added and it should
basically become a redirector to the wiki where people find information that is
going more into depth.
But what do we do with the remaining content?
I tried to put everything onto a card and make it narrow (similar to the blog),
but that I guess only works for the legal page:
https://dev.ipfire.org/legal
Then we have Support & Community from the top navigation. Should that
potentially become one page? It has a lot of redundant information and probably
most of that should be on the wiki. I don't want to talk about development here
at all.
https://dev.ipfire.org/get-supporthttps://dev.ipfire.org/get-involved
Then we have the artwork page:
https://dev.ipfire.org/artwork
I guess that should only have the logos there. It is supposed to be a place for
the press to get it from. I am not even sure if it is linked anywhere but I
occasionally use it in an email.
Then we have the chat page:
https://dev.ipfire.org/chat
That content could potentially go to the community page.
Finally, we need error pages. At the moment we have this:
https://www.ipfire.org/does-not-exist
It does not transport any particular message. I just tells the user off which
isn't too nice. They could be a bit more creative, but at the same time they
should be simple to implement because they are not a priority at all.
The load-balancer we have in front of the web server also sends out error pages.
For that we would need something that is a small page and everything fits into
one single HTML file.
I would like to have an error page in the webapp for these:
* 400 - Bad Request
* 403 - Forbidden
* 404 - Not Found
The load-balancer should have a page for these error codes:
* 500 - Internal Server Error
* 502 - Bad Gateway
* 503 - Service Unavailable
* 504 - Gateway Timeout
Potentially this could all be the same page. The user doesn't need to know an
exact reason why the page isn't loading.
Best,
-Michael
Hello,
finally, I managed to get the new site online. I installed a new fresh web
server and migrated from nginx to Apache which was a little bit tricky...
The URL is the same one: https://dev.ipfire.org/
The blog is available at https://blog.dev.ipfire.org/
Please have a look around. I guess it is best to have an email thread for each
sub-page so that we can move them forward independently. This one is supposed to
be for the blog:
I cut many corners so far, but basically am quite confident that I implemented
the design a fair bit. I didn't pay much attention to the mobile viewports, yet.
So here is the list:
* The sidebar menu will be quite tricky to move to the top when the screensize
is reduced. Is there an alternative we can implement for now and replace this
later?
* I didn't use any of the icons, because I am not sure if there is a good way to
download them all in one go instead of having so many loose SVG objects around.
* I assumed that all headlines in the posts will have the same size (don't we
need any hierarchy here?) and just set h1, h2, ..., h6 to a fixed size. Was that
correct?
Here is the page with all the demo content:
https://blog.dev.ipfire.org/post/test
* Images seem to expand to full width :(
https://blog.dev.ipfire.org/post/introducing-the-ipfire-prime-box-by-founta…
* I have no design for an empty search result:
https://blog.dev.ipfire.org/search?q=sdhjkdh
* I assumed that the year pages should be a list of the posts without author
name clickable:
https://blog.dev.ipfire.org/years/2018
* The big donate button is in the base template and therefore appeared at the
top. I left it there for now because I thought it would be a good idea to have a
donate button on the blog. In the posts we often encourage people to donate.
Should we rather have the button at the bottom just like the LWL posts for posts
that we tag to have that button?
* Should also be a button for the RSS feed?
That's what I have so far. Please comment :)
Best,
-Michael