[fedora-websites] #385: I don't like fade-out feature at
flocktofedora.org
by fedora-badges
#385: I don't like fade-out feature at flocktofedora.org
------------------------+-----------------------
Reporter: rluzynski | Owner: webmaster
Type: defect | Status: new
Priority: minor | Milestone:
Component: General | Keywords:
Blocked By: | Blocking:
------------------------+-----------------------
When I hover my mouse over a section of the text at flocktofedora.org site
the neighboring sections fade out, get white or blurred and unreadable.
That's even worse if I hover the mouse pointer over the area with no text:
in such case all neighboring sections fade out. I guess the intention was
to emphasize the text under the mouse pointer but personally I don't like
this effect. I don't tend to keep the mouse pointer over the text I'm
currently reading. Instead I tend to keep it away, usually close to the
right scrollbar. Also think about the touchscreen devices: if you touch a
screen (for example to scroll the content) and it is interpreted as mouse
hover a part of the screen fades out which you don't want.
My suggestion is to fade in the hovered text rather than fade out the
neighboring text. In order to let the text be faded in it must be faded
out by default but really slightly faded out, for example background
#eeeeee foreground #111111, and fade in to background #ffffff foreground
#000000.
--
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/385>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance
7 years, 1 month
[fedora-websites] #406: Cloud Atomic as default and some layout
changes for getfedora.org
by fedora-badges
#406: Cloud Atomic as default and some layout changes for getfedora.org
------------------------+-----------------------
Reporter: robyduck | Owner: webmaster
Type: task | Status: new
Priority: major | Milestone: Fedora 25
Component: getfedora | Keywords:
Blocked By: | Blocking:
------------------------+-----------------------
So, we need to start working on that soon, the Cloud WG will change their
default option do Atomic. This means we need to rewrite the brochure page
for Cloud and change also the download page(s). I'm not sure if we want to
keep Docker, but for now let's assume we will keep it as it is now.
Other than that, and working with the Design team (thank you duffy), we
will change not only the Logo, but also our index page. These changes will
lead to changes also on all the other pages, I'll resume here the major
points:
* main logos on the index will get some JS, see a fiddle here:
http://run.plnkr.co/plunks/X5HMPdUBvJL3Yjoi9ekm/
* The header should be bootstrap reverse if you scroll down. Means, it
will have the same background as the jumbotron when you get to the page,
and become white (or black, need to test it out) when you scroll down.
* Menu points should use anchors to scroll down to the menu point the user
wants to go. Arrows should show this function to the end user. Obviously
we want to keep it usable, so if you want to scroll down the page you can
still do that.
A mockup for the Atomic brochure page is here:
https://raw.githubusercontent.com/fedoradesign/nextweb-
assets/master/Mockups/Brochure%20Site/brochure-mock-atomic_WIP.png
You can read through a post with some feedback here:
https://lists.fedoraproject.org/archives/list/design-
team(a)lists.fedoraproject.org/thread/3F62JSC6ZW5PXC4EUHK5DTUEN55XMCUH/
Mairín will come up with more mockups, as our thought was to replace also
the (horrible? probably yes) banner we show on the bottom when we get out
a new release.
If all works fine, and as we probably won't have any Atomic images for
prerelease, this task should go into production for F25 final release.
Keep in mind we need to change/check/update/whatever our scripts and
variables.
--
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/406>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance
7 years, 5 months
[fedora-websites] #405: Prepare websites for F25 Alpha release
by fedora-badges
#405: Prepare websites for F25 Alpha release
-----------------------+-----------------------
Reporter: robyduck | Owner: webmaster
Type: task | Status: new
Priority: major | Milestone: ASAP
Component: General | Keywords:
Blocked By: | Blocking:
-----------------------+-----------------------
We are starting a new release cycle (Alpha release is planned for august
23th), and we will have some important changes. I'm not sure how the state
of art is of the new media downloader, and also if it also should serve
prerelease images; in case we need to rewrite all our major download links
(see #384)
On the other hand we should finalize alt.fedoraproject.org (see
https://alt.stg.fedoraproject.org) with subpages for secondary arches.
Would be nice to get it done and start with F25 Alpha.
The other stuff needs to be tested very well, we had a lot of errors for
F24 final release because the paths changed heavily and we couldn't know
that. Please refer to the actual final release to see how things changed
in the meanwhile.
Atomic has become a chapter for itself, we should get soon in touch with
cloud WG to see what they are planning and how they want to get out the
two week images this time. The most probable scenario is that we won't
have atomic images for prerelease again.
* Create F25 Alpha branch
* update globalvariables to F25 Alpha
* Add Alpha banner
* Check all Download links and paths
* Add CHECKSUM files to static/checksums and verify that the paths are
correct.
* Add EC2 AMI IDs for Alpha. Our script is working also for prerelease,
but let's add them also manually to globalvar.py, just to be sure.
* Check and eventually fix checksum paths in all verify pages
* Update Alpha Image sizes and pre_cloud_composedate in
./build.d/globalvar.py. Verify they are right in Cloud images and Docker
image.
* Update the new POT files and push them to Zanata
--
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/405>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance
7 years, 6 months
[fedora-websites] #274: UEFI consistency warning
by fedora-badges
#274: UEFI consistency warning
--------------------------+-----------------------
Reporter: immanetize | Owner: webmaster
Type: enhancement | Status: new
Priority: critical | Milestone: Fedora 21
Component: get.fp.o | Keywords:
Blocked By: | Blocking:
--------------------------+-----------------------
Please add a prominent warning advising users to be consistent in their
usage of UEFI or CSM (BIOS) style installation when booting multiple
operating systems. Whether by misconception, firmware quirks, poor media
creation tools, or accident, users have been consistently reporting issues
with booting their Windows installations after installing Fedora. I have
observed that a significant number of these issues relate to the user
"disabling UEFI" to install Fedora, then discovering that their UEFI
installation of Windows no longer boots. Browse through
ask.fedoraproject.org for Windows related questions, and you'll see how
prevalent these issues are.
There is documentation under development to further explain the issues
involved, but it would be hugely beneficial to have a simple warning to be
consistent displayed when the Fedora image is downloaded. Maybe in
download-splash?
--
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/274>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance
7 years, 6 months
[fedora-websites] #241: Change docs link to redirected one to prevent hard release number usage
by fedora-badges
#241: Change docs link to redirected one to prevent hard release number usage
--------------------------+-----------------------
Reporter: shaiton | Owner: webmaster
Type: enhancement | Status: new
Priority: major | Milestone: ASAP
Component: General | Keywords:
Blocked By: | Blocking:
--------------------------+-----------------------
We should use the redirect as described in puppet:/modules/fedora-
docs/files/redirects.conf instead of linking to specific doc release.
Example:
replace "/en-US/Fedora/16/html/Installation_Guide" occurrences by
"/install-guide".
actual redirect are:
{{{
RewriteRule /accessibility-guide /en-
US/Fedora/16/html/Accessibility_Guide [R=301]
RewriteRule /deployment-guide /en-
US/Fedora/15/html/Deployment_Guide [R=301]
RewriteRule /install-guide /en-
US/Fedora/19/html/Installation_Guide [R=301]
RewriteRule /installation-quick-start-guide /en-
US/Fedora/19/html/Installation_Quick_Start_Guide [R=301]
RewriteRule /readme-burning-isos /en-
US/Fedora/19/html/Burning_ISO_images_to_disc [R=301]
RewriteRule /readme-live-image /en-
US/Fedora/15/html/Fedora_Live_Images [R=301]
RewriteRule /security-guide /en-
US/Fedora/19/html/Security_Guide [R=301]
RewriteRule /selinux-faq /en-
US/Fedora/13/html/SELinux_FAQ [R=301]
RewriteRule /selinux-managing-confined-services-guide /en-
US/Fedora/13/html/Managing_Confined_Services [R=301]
RewriteRule /selinux-user-guide /en-US/Fedora/13/html
/Security-Enhanced_Linux [R=301]
RewriteRule /technical-notes /en-
US/Fedora/16/html/Technical_Notes [R=301]
RewriteRule /user-guide /en-
US/Fedora/14/html/User_Guide [R=301]
RewriteRule /virtualization-guide /en-
US/Fedora/13/html/Virtualization_Guide [R=301]
RewriteRule /wireless-guide /en-
US/Fedora/13/html/Wireless_Guide [R=301]
RewriteRule /release-notes/fc1/x86_64 /en-
US/Fedora_Core/1/html/Release_Notes_for_64-bit_x86_Systems [R=301]
RewriteRule /release-notes/fc1/x86 /en-
US/Fedora_Core/1/html/Release_Notes_for_32-bit_x86_Systems [R=301]
RewriteRule /release-notes/fc2/x86_64 /en-
US/Fedora_Core/2/html/Release_Notes_for_64-bit_x86_Systems [R=301]
RewriteRule /release-notes/fc2/x86 /en-
US/Fedora_Core/2/html/Release_Notes_for_32-bit_x86_Systems [R=301]
RewriteRule /release-notes/fc3/x86_64 /en-
US/Fedora_Core/3/html/Release_Notes_for_64-bit_x86_Systems [R=301]
RewriteRule /release-notes/fc3/x86 /en-
US/Fedora_Core/3/html/Release_Notes_for_32-bit_x86_Systems [R=301]
RewriteRule /release-notes/fc4 /en-
US/Fedora_Core/4/html/Release_Notes [R=301]
RewriteRule /release-notes/fc5 /en-
US/Fedora_Core/5/html/Release_Notes [R=301]
RewriteRule /release-notes/fc6 /en-
US/Fedora_Core/6/html/Release_Notes [R=301]
RewriteRule /release-notes/f7 /en-
US/Fedora/7/html/Release_Notes [R=301]
RewriteRule /release-notes/f8 /en-
US/Fedora/8/html/Release_Notes [R=301]
RewriteRule /release-notes/f9 /en-
US/Fedora/9/html/Release_Notes [R=301]
RewriteRule /release-notes/f10 /en-
US/Fedora/10/html/Release_Notes [R=301]
RewriteRule /release-notes/f11 /en-
US/Fedora/11/html/Release_Notes [R=301]
RewriteRule /release-notes/f12 /en-
US/Fedora/12/html/Release_Notes [R=301]
RewriteRule /release-notes/f13 /en-
US/Fedora/13/html/Release_Notes [R=301]
RewriteRule /release-notes/f14 /en-
US/Fedora/14/html/Release_Notes [R=301]
RewriteRule /release-notes/f15 /en-
US/Fedora/15/html/Release_Notes [R=301]
RewriteRule /release-notes/f16 /en-
US/Fedora/16/html/Release_Notes [R=301]
RewriteRule /release-notes/f17 /en-
US/Fedora/17/html/Release_Notes [R=301]
RewriteRule /release-notes/f18 /en-
US/Fedora/18/html/Release_Notes [R=301]
RewriteRule /release-notes/f19 /en-
US/Fedora/19/html/Release_Notes [R=301]
# Current release
RewriteRule /release-notes/f20 /en-
US/Fedora/20/html/Release_Notes [R=301]
RewriteRule /release-notes /en-
US/Fedora/20/html/Release_Notes [R=301]
}}}
--
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/241>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance
7 years, 6 months