Hello, On Sun, 2018-06-17 at 23:02 +0200, Maurice Gesswein wrote: > Hi, > > I changed the LWL related article to it's main color "indigo". I added the missing viewports with just a part from one article. Since Viewport S and XS has no Sidebar I reused the same solution with the dropdown menu within the header bar as at the Features page. yes, that looks more sweet to me :) > I'll provide a sample page with all text formatting asap. All formattings (size, lineheight, padding) will be same on all viewports to keep it simple. I will need to check again with Sven where he is at. We still have a little bit of stuff to do on the donation page before we can start implementing this. So anything design-wise that needs to be done before we can start working on the blog? Best, -Michael > Best, > Maurice > > On Wed, Jun 13, 2018 at 11:40 PM Michael Tremer <michael.tremer(a)ipfire.org> wrote: > > Hi, > > > > On Wed, 2018-06-13 at 22:29 +0200, Maurice Gesswein wrote: > > > Hey, > > > > > > I'm happy that you like it :) > > > > > > I added an additional version with a modified sidebar based on your feedback: https://zpl.io/bPYLNk6 > > > > Great! > > > > > I added a "Featured" link where tagged articles will show up as a list view or as full articles. Up to you. The years got a headline. I added a "Lightning Wire Labs" link plus the red lightning logo as an indicator that this is something special. The lightning appears also next to the headline of a LWL article and the headline color use the same green as the LWL blog. There is also a button at the bottom which points you to the LWL page. > > > > This works great I think. Not sure if it needs the extra link for LWL > > articles because they won't be that many. But I really like the > > highlighted post, because I want to make it clear that this is > > something else and not IPFire. But it is close enough to be of interest > > for the users. > > > > Should it be green and not indigo (which is the primary LWL colour)? I > > just made the website look really bright and colourful and fun. The > > blog got the green but maybe the brand colour is better? > > > > > Is it possible to include a article from another blog and show it with the correct text formatting? > > > > I hope. Unfortunately we use two different things to format them. The > > IPFire blog uses textile and LWL uses markdown. But there is some > > rendered HTML coming out of it in an RSS feed which I wanted to parse. > > That should work, but embedded things are always a bit of a struggle. > > Let this be my problem :) > > > > > What do you think? > > > > I think this is a very creative and intuitive solution I couldn't have > > come up with myself. It looks fun. It is easy to use. Crystal clear and > > a clean design. Focusses on the content. Just great! > > > > Best, > > -Michael > > > > > Best, > > > Maurice > > > > > > On Wed, Jun 13, 2018 at 12:02 PM Michael Tremer <michael.tremer(a)ipfire.org> wrote: > > > > Hello, > > > > > > > > great hearing from you! > > > > > > > > On Wed, 2018-06-13 at 00:23 +0200, Maurice Gesswein wrote: > > > > > Hey Michael, > > > > > > > > > > > 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. > > > > > > > > > > The contrast is high enough for a very good reading experience. The same > > > > > bgcolor and copy text color is used on the homepage, feature and donate page > > > > > as well. > > > > > > > > Unless you changed this now, I have no idea what I meant by this. Now, the > > > > background is white I personally find this a bit easier to read from. But maybe > > > > I am going blind... > > > > > > > > > But I did a next version which uses the same layout as the Features > > > > > page. https://app.zeplin.io/project/58cb0217f2317d48c7a802f2/dashboard?seid=5b > > > > > 0dc889d80aa1886ae77309 > > > > > > > > > > Still work in progress! Further viewports will follow. > > > > > > > > This looks really clean & tidy! Our users will love it! > > > > > > > > > > Is there a reason that I have missed why this should all be merged together? > > > > > > > > > > It's not a good user experience if one single "service" (the IPFire > > > > > application) has a different navigation (header) for each subdomain. Mirror, > > > > > downloads, planet, talk, forum, etc are only reachable from the footer of the > > > > > mainpage or by typing the URL directly. I would expect the same navigation on > > > > > all pages. This would make it a lot easier to navigate and find things > > > > > faster. > > > > > > > > > > For now I kept the Planet navigation but I merged the content of > > > > > ipfire.org/news and planet.ipfire.org. In my opinion ipfire.org/news should > > > > > now redirect to planet.ipfire.org. Than we would have only one destination for > > > > > the announcements. > > > > > > > > I absolutely agree. This is the way to go. Since it is a blog now, we can move > > > > everything into it. Before, I didn't feel right that the release announcements > > > > where on the "planet". But since it is going now, this is a lot better and > > > > easier. > > > > > > > > > If I didn't miss something the blog owns 5 different kinds of pages: > > > > > All articles > > > > > Article list view (e.g. Hottest posts and 2018) > > > > > > > > I think the "Hottest Posts" could get a redefinition. This is just a list > > > > ordered by clicks and I think it would be better if we just mark a few posts > > > > like the release announcements as "starred" and then people can just go through > > > > the most important posts without scrolling through the longer years. > > > > > > > > I am also not sure if we need the years, but what else would be a good way to go > > > > back in history? > > > > > > > > > Single article > > > > > Posts of a single user > > > > > Search results > > > > > > > > I am also thinking about adding "featured" posts from somewhere else. For > > > > example the lightning wire labs website has a tiny blog now: > > > > > > > > https://www.lightningwirelabs.com/blog > > > > > > > > Many of these articles are IPFire-related and I would like to list on the IPFire > > > > blog as well. So how would we make (visually) sure that people recognise these > > > > as a post from somewhere else? Would we load the entire post into our blog or > > > > just the first paragraph and then send people over to the original blog? > > > > > > > > > If you agree with all of that my next steps will be providing the missing > > > > > viewports and a text formatting sheet. > > > > > > > > Yes I do :) > > > > > > > > Best, > > > > -Michael > > > > > > > > > > > > > > Best, > > > > > Maurice > > > > > > > > > > > > > > > On Wed, May 30, 2018 at 1:19 PM Michael Tremer <michael.tremer(a)ipfire.org> > > > > > wrote: > > > > > > 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=5b > > > > > > 0dc8 > > > > > > > 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