-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New website UI #137
base: master
Are you sure you want to change the base?
New website UI #137
Conversation
By now it's usable, but not so great if anyone wants to see in a live environment. My plan is to finish, at least the first usable version at the end of the week, |
Codecov Report
@@ Coverage Diff @@
## master #137 +/- ##
==========================================
- Coverage 63.28% 63.00% -0.29%
==========================================
Files 65 65
Lines 1419 1419
==========================================
- Hits 898 894 -4
- Misses 521 525 +4 |
Home is finished on desktop. I'm moving to internal pages to make them usable on the new UI (and do some rewrites when it's applicable) and then move to mobile. There's no style for nav pills, paginations and tables yet. Feel free to give me feedbacks :) |
I have just a few fixes to do, but I think that it's easier to make this PR for a desktop version and, after merged, go to mobile. Since the mobile is wrong in some places on the current UI (menu, code block, some tables) and no one opened an issue, I think that most people don't really see the website on mobile... ¯\(ツ)/¯ |
Would you mind posting screenshots please ? |
I still need to fix Books (inside Docs), Donate, and History layouts (they are working, but not with the best visual). A "small" changelog before:
Problems that I faced on local env:
|
Very good work ! I will print this logo on a t-shirt ASAP when it is uploaded to the data repo 😍 |
I think that we can proceed with review and fixes, then wait for the new brand to become available (I hope that the end of this week) to update it and merge. We already finished the logo as a symbol itself, we're trying a few OSS typographies to match a better visual. Conflicting files are because I changed the path and the elements inside, but the content is the same. Edit: Can we deploy to a test environment with the actual server configs? My local has a lot of bugs (windows? hmmm -- yes, didn't install docker again :( )... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
mobile previews looks great !
Symbol (when there's no space to use the default logo, like favicons) There's another one to use in dark backgrounds, but is only the symbol with a circle behind it. We don't have the full logo for use in dark backgrounds yet, but I don't think that it's the main concern right now. The typography used was Montserrat, but I'll make the update with all the infos in the Brand Guide that we'll be made availiable later. I'll update that PR and the data repository with the new logos by the end of the day. |
Ok, all brand is updated. Just waiting for you to test and merge! :) |
JFYI: I don't how do you handle the conflicts and merge strategies, but I don't have access to either. |
@@ -1,3 +1,4 @@ | |||
<!-- TODO: May be removed after the redesign since it's part of header/navbar --> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TODO ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I left because I don't know if you want me to remove or let in there. I didn't find any other place that uses this component.
pmaweb/templates/index.html
Outdated
{{ item.date|date:"mm" }} | ||
</div> | ||
<div class="news-year"> | ||
<!-- TODO: Needs a if(item.date|date:'yyyy' == current_year) {display:none;} --> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
todo ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I left this as TODO because I don't know how to do this on Django (and that news block isn't working on my local machine).
The idea is to hide the year if it's the current one. I may leave it here so you can fix it later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added more comments, but all the diffs LGTM
I think you could add this repository as a remote and rebase onto latest commit to fix the conflicts
To be honest, I always have problems with the rebase, :( |
We can rebase or merge locally with resolving conflicts, maybe another or 2 review would be okay so I can proceed with a merge. |
…age + Fix css variables + Prepare for future dark mode
Co-authored-by: William Desportes <[email protected]>
Signed-off-by: Maurício Meneghini Fauth <[email protected]>
Hi @AdrianoCahete, I rebased your pull request and I also fixed an issue with the template include paths. |
('news', 'News'), | ||
('security/', 'Security'), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should keep the Security link at the main menu.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My first idea was to move "Security" to the "Support" submenu, but when I was implementing I saw that it will be adding more work than I was planning and move out for this. We can try to go back to this idea again.
Stated here:
Moved "Security" to the "Support" submenu. "Security" as a (main) menu gives the idea that the product has a lot of Security Flaws. If we have it on "Support", gives the idea for the people who search for some support that we have attention to security, but for the main public doesn't need to have that attention, because it's the default behavior (to design a safe system).
<button id="menu-handle" class="menuHandle navbar-toggler collapsed" type="button" data-toggle="collapse" | ||
data-target="#navbarSupportedContent" aria-controls="navbarSupportedContent" aria-expanded="false" | ||
aria-label="Toggle navigation" title="Menu"> | ||
<span class="fa fa-bars"></span> | ||
</button> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I probably broke this when rebasing.
<div class="sponsor-list"> | ||
<a href="http://www.trialpro.com/" class="link-external"><img src="{% static 'images/trialpro.png' %}" alt="TrialPro" /></a> | ||
<a href="https://www.vapehuset.se/" class="link-external"><img src="{% static 'images/vapehuset.png' %}" alt="Vapehuset" /></a> | ||
</div> | ||
|
||
<div> | ||
<a href="https://www.vapehuset.se/"><img src="{% static 'images/vapehuset.png' %}" alt="Vapehuset" /></a> | ||
</div> | ||
|
||
<div> | ||
<a href="https://www.4kdownload.com/"><img src="{% static 'images/4kdownload.png' %}" alt="4K Download" /></a> | ||
</div> | ||
|
||
<div> | ||
<a href="https://goread.io/"><img src="{% static 'images/goread.png' %}" alt="goread" /></a> | ||
</div> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That is broken as well after the rebase.
<div class="news-month" title="{{ item.date|date:'mmmm' }}"> | ||
{{ item.date|date:"mm" }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These date formats are wrong, see: https://docs.djangoproject.com/en/1.8/ref/templates/builtins/#date
<div class="row"> | ||
<div class="content"> | ||
|
||
<div class="col-md-6"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The layout here no longer has two columns. 😞
Yes, it is broken.
Maybe you forgot to load the test data:
|
I think you should add a section on the home page for the Software Freedom Conservancy logo. |
Co-authored-by: Maurício Meneghini Fauth <[email protected]>
I tried, but it cannot run on Windows ( I'm a little busy right now, but I'll try to fix that in the next weeks. |
Right aligned on the same line/row as the Sponsors, maybe? |
Could be a python3 issue instead you would probably need to use python2 |
I thought about a full width banner with the logo and some text. |
Sorry for my disappearance. I had a completely broken computer (and a completely new one!) and two new jobs in the past few months... I'll try to run the project again (and maybe make a PoC in another language too) as soon as possible! |
Fixes #92.