“this can be achieved without Javascript?”
For a browser old of 30 years?
“this can be achieved without Javascript?”
For a browser old of 30 years?
On the screenshot of the T-shirt:
I think there are too much rounded buttons and rectangles, hiding the most important button: Download button.
Maybe use a unique color (background-color) for the Download.
@webDev first of all, your drafts look really good!!!
is somehow invisible. Personally, I prefer the “strict” separation of menus/footers from the actual content, but maybe I’m from old school
Yes thansk, I saw it.
I’m fine with dark-glass effect, but isn’t one superfluous? Why two buttons practically side by side?
Someone mentioned that F-Droid has only an android version. So, “Download F-Droid” is sufficient (imho).
Based on the F-Droid icon (shadow), I have changed the perspective of the button.
Personally, I prefer the sketched hand and not the real picture, but it’s a little detail.
You can maybe play around with my new mockup (only one download button and w/o hand):
Personally, I’m absolutely against including any third-party stuff. If so, then only locally. Though, there can be some downsides.
There’s a similar discussion at signalusers[dot]org:
@webDev Very nice looking!
Even more interesting that you used a tool like Inkscape to do this. Do you use it also for more final visuals or just for these very good looking initial drafts?
(…merging here)
I think dark orange would suit well 9 years old F-Droid : strength + endurance (?), versus blue ( cool + fresh ?).
@webDev , there are few I don’t find in your artwork :
android is now heavily focusing on multi screens : auto / tv … (and so should F-Droid ?)
vocal command emergence (no hands required)
reproducible-builds
(Back to orange,) F-Droid is not explicitly Gitlab dependent, but it seems there is no other “viable” solution to maintain the whole project. So orange could link to Gitlab without need of mentioning it (?). Also there should be somewhere a permanent “bridge” to encourage users to become Gitlab active members (especially for missing metadata ?) ?
UPDATE
TBC
Mobile (click to see full page)
Mobile menu
Desktop
Desktop menu
@shubhamtyagi thanks and agree. A download button at the bottom is important.
@hotlittlewhitedog, there are security and privacy reasons for blocking JS.
There is no DL button in the donate region, look closer ; ). I tried removing the rounded donate buttons but it made the pane look very cluttered, interestingly.
@fd-fan, sounds fair. I won’t include Font Awesome.
The problem with the distinct separation is it make the top message appear cramped.
@ggruber, inkscape is pretty great, despite a few issues, I plan to use it to the end, : )
@oF2pks, I like ur idea of using design motifs (in this case colours) to link F-Droid to Gitlab. The problem is blue is a good, calming colour for F-Droid. Keep in mind with your design that colours in different proportions can do different things. So an entire wall painted orange has a different effect than a few small elements in orange. I feel like over-hauling the logo is a bit outside the scope for this project. All I did is shapern a few bits and add a shine. What would be good in the future might be a design competition to develop a new robot. The new robot would need to get a 70% approval rating over the existing robot, to justify the change. As I said before though, you dont need to worry about the blue colour damaging your screen because F-Droid doesnt need to be on your screen, especially for a long period of time. If it really bothers you have you tried talking to the people who make that Amexia app? They might do a version in colours that are less damaging to screens. I’m interested in learning about this problem myself. Might you please provide a link to the scientific studies?
NEW NAV LINKS:
NEW CONTENT LINKS:
AFTER F-DROID PAGE IS DONE:
OTHER MINOR SITE IMPROVEMENTS:
For pages that are not the landing page, I am keen to keep the same layout (ie. content in the wider left column and news, donate, and latest content on the narrower column on the right). The top navigation bar, language and App Search functions may be updated to match this landing page.
‘Docs’ page (Docs | F-Droid - Free and Open Source Android App Repository)
Slight rework may be desirable:
‘Security Model’ page Security Model | F-Droid - Free and Open Source Android App Repository
EDIT: Wiki page (https://f-droid.org/wiki/page/Website_home/en-proposal)
@oF2pks The orange looks a bit brown I think (sorry).
And it might be that we have to (or want to) get away from GitLab in the future.
Finally, personally I would not understand that you are referring to reproducible builds (again, sorry).
I really like your ideas and work! I only think that it looks a bit too crowded, maybe take out some of the twirls or decrease the contrast? (just my personal opinion).
Maybe you also want to propose a redesign for the client? I tried to start something here but I am a developer, not a designer.
Thanks Hocuri, will reduce contrast (whiter items to grey, darker arcs will be lightened). Will also reduce arc and circle numbers, where possible. Adding this task to the TBC above.
The more creative designs means the more creative the business is means more customers automatically create lifelong relationship with business.
Hi Ashish, I although I rarely advocate lifelong relationships with things, except maybe stainless steel cookware, I feel that the more people using FOSS and privacy apps the better, for numerous reasons.
Hi folks,
I whipped up this “Tell a Friend” section based on the F-Droid wiki page that I wrote about in the last comment I made.
If people think it’s tacky and too “advertisey”, I don’t need to make it. But remember, that wikipage was translated into three languages and I think it could be valueable presented to users in this way, with a bit of updating because the page did have some old info.
Also I think we need a way to celebrate 10 years so just putting this out there for critique.
@webDev I think your designs are looking good! Are you also planning on implementing them? That’s the surefire way to make sure it gets built. I can review merge requests as time permits.
A couple things to think about:
I’m glad you have the same opinion.
In response to my concerns
webDev wrote:
@fd-fan, I’m unsure that the search page (search.f-droid.org) a good page to lead people to because it is so sparce. I think its better to have a search form on all pages This is the way the current site functions although I hope to improve the user experience. You’ll see in comment 47 (49th counting spam) I have added a “Find apps” form in three locations:
1)The top bar,
2) The top hamburger/three dot menu, and
3) the footer.
@hans, Yes I will be implementing it. I have a bit of learning to do about Markdown first as I’ve not used that before. Unfortunately, I don’t think that I am currently in a position to do the “Hugo transition” as I’m not familiar enough with the current setup. After I do the landing page I may be inclined to do the Hugo transition but intuition tells me that it probably won’t be easy.
@NicoAlt Hi mate, was doing some exploration of Markdown, this (https://www.staticgen.com/) is a list of static-site builders that build from Markdown. The “Hugo” build tool is listed and is shown to be written in Go. Does F-Droid allow Go built apps? I don’t actually know. If it doesn’t then we probably can’t use Hugo, by extension(?).
Hey @webDev,
Haha, yeah. F-Droid’s unique requirement is that software is free and open source, but don’t get confused with apps inside F-Droid and software used in its infrastructure. I’ve never heard of “Go built [Android] apps” and I imagine it would be a pain to build them. For the infrastructure, any language is fine. Only in case we have two equally qualified pieces of software, one written in python and the other one in some other language, we opt for the python one. But Hugo is really the best static site generator out there, so that’s the way we should go. Also note @hans’ comment on the issue linked in this topic some days ago:
Moving the blog only to Hugo via the news.f-droid.org site shouldn’t be a lot of work, since it is basically already running. Moving the whole f-droid.org site to Hugo is a project, perhaps not huge, but a chunk of work. It would very likely let us remove the limit on the number of languages. It would also likely greatly reduce the server specs required for generating f-droid.org.
This together with Hans’ last post here should give you all necessary information to get on speed. Thanks a lot for your work!
Overall, sounds like things are progressing in the right direction! I’d just like to add one comment about Javascript libraries and security. Most F-Droid contributors are not web developers, though some are. I’m not, for example. So I don’t have a good sense for how to evaluate Javascript libraries for security beyond just standard practice things like include as few deps as possible, and use libraries that have well maintained stable releases. If there is bad Javascript in the site, then an attacker can change the initial download link, e.g. the big download button on the main page. That can then be used to feed malware versions on a targeted basis, or other bad things.
You’re probably looking for Subresource Integrity, an underused security feature for frontend. That alone solves most dangerous holes in client JavaScript.
@Roboe that’s a nice feature for ensuring that the javascript files are delivered unmodified, but it won’t help at all if the original Javascript library has vulnerabilities or even malware in it. I’m talking about the latter case.
And for the record, we solve the issue of javascript sources being reliable by always sourcing them from our domain. No other domain is allowed, check the HTTP CSP.
I meant rather whether it was “considered” that the search results/list would also be adapted to the new design.