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

Implement new website interface #1460

Closed
bnvk opened this Issue Nov 27, 2015 · 20 comments

Comments

Projects
None yet
6 participants
@bnvk

bnvk commented Nov 27, 2015

As per the goal of better branding for Qubes, I'm implementing the designs I proposed in #1207 it will basically be a custom Bootstrap theme on top on the exiting Jekyll site.

I'm just opening this issue to track the progress of it!

@bnvk

This comment has been minimized.

Show comment
Hide comment
@bnvk

bnvk Nov 27, 2015

@mfc @adrelanos responses to your points in #1207

I advice to check if using the Tor logo below the Whonix logo is safe. Perhaps asking for permission

I just asked Moritz from Tor Project and he gave me the thumbs up! I purposefully didn't write the blurb about Xen as they have very specific terms of wording they like used. I looked through the Debian & Fedora pages and our use is OK.

Instead of "use the OS you prefer" maybe it should highlight "use all your favorite apps" or similar?

That's a good point. I'm not sure what's best here. That was in response to numerous Debian people in the community not wanting to try Qubes because they think it doesn't support Debian.

I'm hesitant (at this stage) to market Qubes from the "install whatever 'apps'" angle, as currently installing anything not in Yum / Apt is one of the biggest user experience painpoints, IMO. To my UX brain "Install apps" means, a simple GUI browsable app store which we're a bit far from having!

I would make sure that you implement the things that already have content, so that you don't have to create new content.

Definitely I just put Videos as a place holder / brainstorm / documenting a path forward. There's a few things that won't be implemented by Tues as well, like "Newsletter" which need to be decided if the project even wants that.

re: Awards & Grants, OTF dislikes being described as providing grants...

Okie doke!

bnvk commented Nov 27, 2015

@mfc @adrelanos responses to your points in #1207

I advice to check if using the Tor logo below the Whonix logo is safe. Perhaps asking for permission

I just asked Moritz from Tor Project and he gave me the thumbs up! I purposefully didn't write the blurb about Xen as they have very specific terms of wording they like used. I looked through the Debian & Fedora pages and our use is OK.

Instead of "use the OS you prefer" maybe it should highlight "use all your favorite apps" or similar?

That's a good point. I'm not sure what's best here. That was in response to numerous Debian people in the community not wanting to try Qubes because they think it doesn't support Debian.

I'm hesitant (at this stage) to market Qubes from the "install whatever 'apps'" angle, as currently installing anything not in Yum / Apt is one of the biggest user experience painpoints, IMO. To my UX brain "Install apps" means, a simple GUI browsable app store which we're a bit far from having!

I would make sure that you implement the things that already have content, so that you don't have to create new content.

Definitely I just put Videos as a place holder / brainstorm / documenting a path forward. There's a few things that won't be implemented by Tues as well, like "Newsletter" which need to be decided if the project even wants that.

re: Awards & Grants, OTF dislikes being described as providing grants...

Okie doke!

@adrelanos

This comment has been minimized.

Show comment
Hide comment
@adrelanos

adrelanos Nov 27, 2015

Member

Brennan Novak:

I advice to check if using the Tor logo below the Whonix logo is safe. Perhaps asking for permission
I just asked Moritz from Tor Project and he gave me the thumbs up! I purposefully didn't write the blurb about Xen as they have very specific terms of wording they like used. I looked through the Debian & Fedora pages and our use is OK.

I advice going for a legally binding letter. We don't know what the new
executive director will say on this.

But perhaps it doesn't matter as much. They very most likely won't sue
before asking to remove it. And as long they not ask, we're cool.
Removing the logo at a later point will not be that much work. I was a
bit worried about this, because in past changing the names from TorBOX,
Tor-Gateway and Tor-Workstation to something that no longer includes the
string "tor", was a painful, time wasting and time consuming process.
Not a mistake I wish to repeat.

Member

adrelanos commented Nov 27, 2015

Brennan Novak:

I advice to check if using the Tor logo below the Whonix logo is safe. Perhaps asking for permission
I just asked Moritz from Tor Project and he gave me the thumbs up! I purposefully didn't write the blurb about Xen as they have very specific terms of wording they like used. I looked through the Debian & Fedora pages and our use is OK.

I advice going for a legally binding letter. We don't know what the new
executive director will say on this.

But perhaps it doesn't matter as much. They very most likely won't sue
before asking to remove it. And as long they not ask, we're cool.
Removing the logo at a later point will not be that much work. I was a
bit worried about this, because in past changing the names from TorBOX,
Tor-Gateway and Tor-Workstation to something that no longer includes the
string "tor", was a painful, time wasting and time consuming process.
Not a mistake I wish to repeat.

@mfc

This comment has been minimized.

Show comment
Hide comment
@mfc

mfc Nov 27, 2015

Member

@adrelanos as you have previously mentioned and Brennan confirmed with Moritz, using the Tor logo in this way is fine:
https://www.torproject.org/docs/trademark-faq.html.en#onionlogo

The issue you faced was related to incorporating the Tor word into a new name for a different project, which they explicitly say they prefer not to have happen:
https://www.torproject.org/docs/trademark-faq.html.en#combining

As you mention, if they end up having a problem with it, we can cite their language on their website for support/justification. No one is going to get sued.

I'm hesitant (at this stage) to market Qubes from the "install whatever 'apps'" angle, as currently installing anything not in Yum / Apt is one of the biggest user experience painpoints, IMO.

Yeah this is two different things. What it would highlight is that any application that is in the repos of Fedora or Debian are available to Qubes users, and that any Windows 7 applications can be installed as well.

So the angle is, as an existing Debian user (or Windows 7 user, or Fedora user): "all those applications that you already use for your workflow exist in Qubes as well". This is the actual impact of the statement "Qubes supports Debian".

Only advanced users need to install programs not in the repos, that is not something ever we should focus on.

To my UX brain "Install apps" means, a simple GUI browsable app store which we're a bit far from having!

That exists, it's the package managers. But again the focus is saying that someone can import their existing workflow of applications they use into Qubes a-ok.

Member

mfc commented Nov 27, 2015

@adrelanos as you have previously mentioned and Brennan confirmed with Moritz, using the Tor logo in this way is fine:
https://www.torproject.org/docs/trademark-faq.html.en#onionlogo

The issue you faced was related to incorporating the Tor word into a new name for a different project, which they explicitly say they prefer not to have happen:
https://www.torproject.org/docs/trademark-faq.html.en#combining

As you mention, if they end up having a problem with it, we can cite their language on their website for support/justification. No one is going to get sued.

I'm hesitant (at this stage) to market Qubes from the "install whatever 'apps'" angle, as currently installing anything not in Yum / Apt is one of the biggest user experience painpoints, IMO.

Yeah this is two different things. What it would highlight is that any application that is in the repos of Fedora or Debian are available to Qubes users, and that any Windows 7 applications can be installed as well.

So the angle is, as an existing Debian user (or Windows 7 user, or Fedora user): "all those applications that you already use for your workflow exist in Qubes as well". This is the actual impact of the statement "Qubes supports Debian".

Only advanced users need to install programs not in the repos, that is not something ever we should focus on.

To my UX brain "Install apps" means, a simple GUI browsable app store which we're a bit far from having!

That exists, it's the package managers. But again the focus is saying that someone can import their existing workflow of applications they use into Qubes a-ok.

@bnvk

This comment has been minimized.

Show comment
Hide comment
@bnvk

bnvk Dec 3, 2015

Here is a collection of to-do items (that I'm aware of) and working on today. They are ordered in how I think priority is:

  • Create a more proper "blog" at the /news/ section of the site
  • Fix RSS/atom feeds for the blog, currently master.atom and feed.xml are broken
  • Make news on homepage use proper news section
  • Make the "normal blue links" display a :hover state
  • Improve Get Started / Documentation info-arch
  • Improve and make h2, h3, h4s on sub pages uniform and nice looking
  • Make code snippets / terminal commands styled nicely
  • Properly center the LOGO - Qubes OS section on the homepage
  • Make the "Search with DuckDuckGo" box more polished
  • Fill out the Help & Support and Follow & Contact sections on homepage better
  • Make blue links & buttons use the Open Sans font
  • Update navbar logo with new colored icon

@rootkovska @marmarek @mfc @adrelanos @axon-qubes please add things you come across looking at the dev URL I sent you in email. Some of these already take into account Joanna's feedback!

bnvk commented Dec 3, 2015

Here is a collection of to-do items (that I'm aware of) and working on today. They are ordered in how I think priority is:

  • Create a more proper "blog" at the /news/ section of the site
  • Fix RSS/atom feeds for the blog, currently master.atom and feed.xml are broken
  • Make news on homepage use proper news section
  • Make the "normal blue links" display a :hover state
  • Improve Get Started / Documentation info-arch
  • Improve and make h2, h3, h4s on sub pages uniform and nice looking
  • Make code snippets / terminal commands styled nicely
  • Properly center the LOGO - Qubes OS section on the homepage
  • Make the "Search with DuckDuckGo" box more polished
  • Fill out the Help & Support and Follow & Contact sections on homepage better
  • Make blue links & buttons use the Open Sans font
  • Update navbar logo with new colored icon

@rootkovska @marmarek @mfc @adrelanos @axon-qubes please add things you come across looking at the dev URL I sent you in email. Some of these already take into account Joanna's feedback!

@adrelanos

This comment has been minimized.

Show comment
Hide comment
@adrelanos

adrelanos Dec 3, 2015

Member

Minor, on /donate there is a , to much in the headline.

QubesOS/qubes-doc#62 (comment)

Member

adrelanos commented Dec 3, 2015

Minor, on /donate there is a , to much in the headline.

QubesOS/qubes-doc#62 (comment)

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Dec 3, 2015

Member

Looks very nice so far; great work!

  • I agree about the search box. I think you should feel at liberty to reimagine the search function more broadly. (IOW: It doesn't have to just be polishing the existing box. Maybe there's a completely different but better way to do it.)
  • I wonder if "Get Started" is the right way to link to the documentation. When I saw "Get Started," I thought it was going to be something different. Not sure if most users will make the connection either. (My vote would be for "documentation" or "docs" or something along those lines.)
  • It would be nice if the sections at the bottom were arranged responsively. It looks like they remain a single, long column regardless of horizontal browser width. They should take advantage of that extra real estate.
  • Maybe this is big enough to be a separate project, but we should also consider revamping the whole "download" scheme. In many projects, clicking the big "download" button on the front page would result in immediately downloading the actual latest version of the software rather than redirecting the user to a page on which all past versions are featured equally prominently.
  • On the front page, in the "Posts & Announcements" section, Markdown asterisks are being displayed as literal asterisks rather than resulting in italics like they're supposed to.
  • The first section on /doc/ is being displayed as Markdown source.
  • Code block font color is way too light.
  • The script we use for auto-generating per-page ToCs adds an empty box to the bottom of each page. Any idea how to get rid of it? (The ToC boxes themselves could use some aesthetic improvement, too. Their ugliness is in no way your fault, of course, but it would be great if you could make them look better!)
Member

andrewdavidwong commented Dec 3, 2015

Looks very nice so far; great work!

  • I agree about the search box. I think you should feel at liberty to reimagine the search function more broadly. (IOW: It doesn't have to just be polishing the existing box. Maybe there's a completely different but better way to do it.)
  • I wonder if "Get Started" is the right way to link to the documentation. When I saw "Get Started," I thought it was going to be something different. Not sure if most users will make the connection either. (My vote would be for "documentation" or "docs" or something along those lines.)
  • It would be nice if the sections at the bottom were arranged responsively. It looks like they remain a single, long column regardless of horizontal browser width. They should take advantage of that extra real estate.
  • Maybe this is big enough to be a separate project, but we should also consider revamping the whole "download" scheme. In many projects, clicking the big "download" button on the front page would result in immediately downloading the actual latest version of the software rather than redirecting the user to a page on which all past versions are featured equally prominently.
  • On the front page, in the "Posts & Announcements" section, Markdown asterisks are being displayed as literal asterisks rather than resulting in italics like they're supposed to.
  • The first section on /doc/ is being displayed as Markdown source.
  • Code block font color is way too light.
  • The script we use for auto-generating per-page ToCs adds an empty box to the bottom of each page. Any idea how to get rid of it? (The ToC boxes themselves could use some aesthetic improvement, too. Their ugliness is in no way your fault, of course, but it would be great if you could make them look better!)
@rootkovska

This comment has been minimized.

Show comment
Hide comment
@rootkovska

rootkovska Dec 3, 2015

Member

I think my articles on Intel SGX should not be listed under "our research". Potentially also the "Intel x86 harmful" paper? Also would be nice to get some other papers there, i.e. authored by others?

Member

rootkovska commented Dec 3, 2015

I think my articles on Intel SGX should not be listed under "our research". Potentially also the "Intel x86 harmful" paper? Also would be nice to get some other papers there, i.e. authored by others?

@mfc

This comment has been minimized.

Show comment
Hide comment
@mfc

mfc Dec 4, 2015

Member

I think my articles on Intel SGX should not be listed under "our research". Potentially also the "Intel x86 harmful" paper? Also would be nice to get some other papers there, i.e. authored by others?

Should or should not be listed? If not listed, maybe not have the section? What are examples of other papers that should be listed instead? I think you would need to provide this content since it's outside Brennan's scope.

Member

mfc commented Dec 4, 2015

I think my articles on Intel SGX should not be listed under "our research". Potentially also the "Intel x86 harmful" paper? Also would be nice to get some other papers there, i.e. authored by others?

Should or should not be listed? If not listed, maybe not have the section? What are examples of other papers that should be listed instead? I think you would need to provide this content since it's outside Brennan's scope.

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Dec 4, 2015

Member

Perhaps the idea is that papers like the Intel SGX one are not accurately described as "Qubes research" but rather "Rutkowska's rsearch" or "ITL's research." Or perhaps the idea is that the section should not just be limited to research produced by the Qubes/ITL team, but rather that it should include papers which are relevant to Qubes (e.g., about desktop security topics) even if authored by others.

Member

andrewdavidwong commented Dec 4, 2015

Perhaps the idea is that papers like the Intel SGX one are not accurately described as "Qubes research" but rather "Rutkowska's rsearch" or "ITL's research." Or perhaps the idea is that the section should not just be limited to research produced by the Qubes/ITL team, but rather that it should include papers which are relevant to Qubes (e.g., about desktop security topics) even if authored by others.

@mfc

This comment has been minimized.

Show comment
Hide comment
@mfc

mfc Dec 4, 2015

Member

here is the existing "qubes research" page: https://www.qubes-os.org/doc/qubes-research/

Member

mfc commented Dec 4, 2015

here is the existing "qubes research" page: https://www.qubes-os.org/doc/qubes-research/

bnvk added a commit to bnvk/qubes-doc that referenced this issue Dec 4, 2015

bnvk added a commit to bnvk/qubesos.github.io that referenced this issue Dec 4, 2015

bnvk added a commit to bnvk/qubesos.github.io that referenced this issue Dec 4, 2015

bnvk added a commit to bnvk/qubes-posts that referenced this issue Dec 4, 2015

bnvk added a commit to bnvk/qubesos.github.io that referenced this issue Dec 7, 2015

bnvk added a commit to bnvk/qubesos.github.io that referenced this issue Dec 7, 2015

bnvk added a commit to bnvk/qubesos.github.io that referenced this issue Dec 7, 2015

bnvk added a commit to bnvk/qubesos.github.io that referenced this issue Dec 7, 2015

bnvk added a commit to bnvk/qubesos.github.io that referenced this issue Dec 7, 2015

bnvk added a commit to bnvk/qubesos.github.io that referenced this issue Dec 7, 2015

bnvk added a commit to bnvk/qubesos.github.io that referenced this issue Dec 7, 2015

bnvk added a commit to bnvk/qubesos.github.io that referenced this issue Dec 7, 2015

bnvk added a commit to bnvk/qubesos.github.io that referenced this issue Dec 7, 2015

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Dec 7, 2015

Member

Donation links are wrong - currently we don't have paypal. And '#' is in wrong place.

Member

marmarek commented Dec 7, 2015

Donation links are wrong - currently we don't have paypal. And '#' is in wrong place.

@mfc

This comment has been minimized.

Show comment
Hide comment
@mfc

mfc Dec 7, 2015

Member

just submitted a couple pull requests to improve language. Agree with Marek for now we should remove Direct Donation and Paypal in the footer, can add again once we have those options available to users.

Member

mfc commented Dec 7, 2015

just submitted a couple pull requests to improve language. Agree with Marek for now we should remove Direct Donation and Paypal in the footer, can add again once we have those options available to users.

bnvk added a commit to bnvk/qubes-attachment that referenced this issue Dec 7, 2015

bnvk added a commit to bnvk/qubesos.github.io that referenced this issue Dec 7, 2015

@bnvk

This comment has been minimized.

Show comment
Hide comment
@bnvk

bnvk Dec 7, 2015

@marmarek @mfc definitely, I just pushed updates to nav & the Donate page itself. My PageKite will be down for an hour or so now!

bnvk commented Dec 7, 2015

@marmarek @mfc definitely, I just pushed updates to nav & the Donate page itself. My PageKite will be down for an hour or so now!

bnvk added a commit to bnvk/qubes-posts that referenced this issue Dec 8, 2015

bnvk added a commit to bnvk/qubesos.github.io that referenced this issue Dec 8, 2015

marmarek added a commit to QubesOS/qubesos.github.io that referenced this issue Dec 8, 2015

autoupdate: attachment
attachment:
    tag mm_e2bb9da5
    tagger Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com> 1449575429 +0100

    Tag for commit e2bb9da55dece671e8a8819c7e17dbc97787bdd3
    gpg: Signature made Tue 08 Dec 2015 12:50:30 PM CET using RSA key ID 9684938A
    gpg: Good signature from "Marek Marczykowski-Górecki (Qubes Documentation Signing Key) <marmarek@invisiblethingslab.com>"

    e2bb9da added BTC QR code and changed color of outline logo QubesOS/qubes-issues#1460
    4b9d49c Merge branch 'master' of https://github.com/QubesOS/qubes-attachment
    74d7256 added qubes-purism-image
    18bcc0f added various icons and logos for new site design
    f22bf3c added Site graphics

@marmarek marmarek added the C: website label Dec 8, 2015

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Dec 8, 2015

Member

@axon-qubes @Nukama, we're going to switch the website in about an hour! :)

Member

marmarek commented Dec 8, 2015

@axon-qubes @Nukama, we're going to switch the website in about an hour! :)

marmarek added a commit to QubesOS/qubesos.github.io that referenced this issue Dec 8, 2015

autoupdate: _posts
_posts:
    tag mm_dc7e289f
    tagger Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com> 1449586397 +0100

    Tag for commit dc7e289f8ee7f99499f286b053a39a5d3e6935d5
    gpg: Signature made Tue 08 Dec 2015 03:53:20 PM CET using RSA key ID 9684938A
    gpg: Good signature from "Marek Marczykowski-Górecki (Qubes Documentation Signing Key) <marmarek@invisiblethingslab.com>"

    dc7e289 R3.1 rc1 release annoucement
    7d7efae Updated post categories with commas QubesOS/qubes-issues#1460
    8bc55fe created posts for all articles QubesOS/qubes-issues#1460
    c336b5e first pass at converting blog posts to actual Jekyll posts QubesOS/qubes-issues#1460

marmarek added a commit to QubesOS/qubesos.github.io that referenced this issue Dec 8, 2015

autoupdate: _doc
_doc:
    tag mm_b079a3b7
    tagger Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com> 1449588545 +0100

    Tag for commit b079a3b70547039980289dc780e49cde4fc405a8
    gpg: Signature made Tue 08 Dec 2015 04:29:07 PM CET using RSA key ID 9684938A
    gpg: Good signature from "Marek Marczykowski-Górecki (Qubes Documentation Signing Key) <marmarek@invisiblethingslab.com>"

    b079a3b Merge remote-tracking branch 'origin/pr/62'
    1ae209a moved Getting Started & Research to site repo QubesOS/qubes-issues#1460
    40c1312 fixed Privacy Guides heading QubesOS/qubes-issues#1202
    84c1a0c fixed merge conflict QubesOS/qubes-issues#1202
    c956a2c saved changes to Doc index as QubesOS/qubes-issues#1202
    c7aa41b started porting over Whonix documentation QubesOS/qubes-issues#1201 QubesOS/qubes-issues#1202
    554e5fd harmonized names for 'Resizing' things and improved Root Disk Size (QubesOS/qubes-issues#1441)
    015758b fixed link to Template Whonix and Doc ToC
    763abfb added Privacy section, moved TorVM & VPN there
    25a2fc0 Merge branch 'upstream'
    fb107c1 fixed markdown on resize-root-disk-image
@adrelanos

This comment has been minimized.

Show comment
Hide comment
@adrelanos

adrelanos Dec 8, 2015

Member

On https://www.qubes-os.org/doc/privacy/install-whonix/ the link to https://www.qubes-os.org/en/doc/troubleshooting/debian-and-whonix/ is broken.

Is there a general problem with /en/?

Perhaps QubesOS/qubes-doc#65 fixing a similar issue is superfluous.

Member

adrelanos commented Dec 8, 2015

On https://www.qubes-os.org/doc/privacy/install-whonix/ the link to https://www.qubes-os.org/en/doc/troubleshooting/debian-and-whonix/ is broken.

Is there a general problem with /en/?

Perhaps QubesOS/qubes-doc#65 fixing a similar issue is superfluous.

@bnvk

This comment has been minimized.

Show comment
Hide comment
@bnvk

bnvk Dec 9, 2015

@adrelanos sorry about that! When I first started working on porting the Whonix stuff, all the pages had the /en/ then at some point it changed to without before I sent a pull request and that one slipped through!

bnvk commented Dec 9, 2015

@adrelanos sorry about that! When I first started working on porting the Whonix stuff, all the pages had the /en/ then at some point it changed to without before I sent a pull request and that one slipped through!

@adrelanos

This comment has been minimized.

Show comment
Hide comment
@adrelanos

adrelanos Dec 9, 2015

Member

Apparently there are quite a few more broken /en/ links.

grep --exclude-dir=.git -r '(/en/'
managing-os/templates/whonix.md:To learn more and for installation instructions, read our privacy guide: [Whonix for privacy & anonymization](/en/doc/privacy/whonix/)
troubleshooting/updating-debian-and-whonix.md:Despite Qubes shipping with [Debian Templates](/en/doc/templates/debian/), most of Qubes core components run on Fedora and thus our documentation has better coverage for Fedora. However, Qubes has been working closely with the [Whonix](https://whonix.org) project which is based on Debian.
configuration/network-printer.md:In order to mitigate this risk, one might consider creating a custom template (i.e. clone the original template) and then install the 3rd party, unverified drivers there. Such template might then be made the default template for [Disposable VM creation](/en/doc/disposable-vms/), which should allow one to print any document by right-clicking on it, choosing "Open in Disposable VM" and print from there. This would allow to print documents from more trusted AppVMs (based on a trusted default template, that is not poisoned by 3rd party printer drivers).
privacy/install-whonix.md:You can learn more about [customizing Whonix here](/en/doc/privacy/customizing-whonix/)
privacy/updating-whonix.md:  However, if what you see is different or you see the word `WARNING:` you should look at our troubleshooting documentation for [Debian and Whonix](/en/doc/troubleshooting/debian-and-whonix/).
privacy/whonix.md:To improve your privacy & anonymity on the internet, you can install the [Whonix Template](/en/doc/templates/whonix/) on your Qubes machine.
privacy/whonix.md:*  [Install Whonix in Qubes](/en/doc/privacy/install-whonix/)
privacy/whonix.md:*  [Updating Whonix in Qubes](/en/doc/privacy/updating-whonix/)
privacy/whonix.md:*  [Customizing Whonix](/en/doc/privacy/customizing-whonix/)
privacy/whonix.md:*  [Uninstall Whonix from Qubes](/en/doc/privacy/uninstall-whonix/)
privacy/whonix.md:You can also use [Qubes support](/en/help/), but not all Qubes users run Whonix.
Member

adrelanos commented Dec 9, 2015

Apparently there are quite a few more broken /en/ links.

grep --exclude-dir=.git -r '(/en/'
managing-os/templates/whonix.md:To learn more and for installation instructions, read our privacy guide: [Whonix for privacy & anonymization](/en/doc/privacy/whonix/)
troubleshooting/updating-debian-and-whonix.md:Despite Qubes shipping with [Debian Templates](/en/doc/templates/debian/), most of Qubes core components run on Fedora and thus our documentation has better coverage for Fedora. However, Qubes has been working closely with the [Whonix](https://whonix.org) project which is based on Debian.
configuration/network-printer.md:In order to mitigate this risk, one might consider creating a custom template (i.e. clone the original template) and then install the 3rd party, unverified drivers there. Such template might then be made the default template for [Disposable VM creation](/en/doc/disposable-vms/), which should allow one to print any document by right-clicking on it, choosing "Open in Disposable VM" and print from there. This would allow to print documents from more trusted AppVMs (based on a trusted default template, that is not poisoned by 3rd party printer drivers).
privacy/install-whonix.md:You can learn more about [customizing Whonix here](/en/doc/privacy/customizing-whonix/)
privacy/updating-whonix.md:  However, if what you see is different or you see the word `WARNING:` you should look at our troubleshooting documentation for [Debian and Whonix](/en/doc/troubleshooting/debian-and-whonix/).
privacy/whonix.md:To improve your privacy & anonymity on the internet, you can install the [Whonix Template](/en/doc/templates/whonix/) on your Qubes machine.
privacy/whonix.md:*  [Install Whonix in Qubes](/en/doc/privacy/install-whonix/)
privacy/whonix.md:*  [Updating Whonix in Qubes](/en/doc/privacy/updating-whonix/)
privacy/whonix.md:*  [Customizing Whonix](/en/doc/privacy/customizing-whonix/)
privacy/whonix.md:*  [Uninstall Whonix from Qubes](/en/doc/privacy/uninstall-whonix/)
privacy/whonix.md:You can also use [Qubes support](/en/help/), but not all Qubes users run Whonix.
@adrelanos

This comment has been minimized.

Show comment
Hide comment
@adrelanos

adrelanos Dec 9, 2015

Member

Perhaps the following multi fix up would sort this out.

one='(/en/'
two='(/'

for file_name in $(grep -r -l --exclude-dir=.git '(/en/') ; do
   sed -i "s#$one#$two#g" "$file_name"
done
Member

adrelanos commented Dec 9, 2015

Perhaps the following multi fix up would sort this out.

one='(/en/'
two='(/'

for file_name in $(grep -r -l --exclude-dir=.git '(/en/') ; do
   sed -i "s#$one#$two#g" "$file_name"
done

adrelanos added a commit to adrelanos/qubes-doc that referenced this issue Dec 9, 2015

@adrelanos adrelanos referenced this issue in QubesOS/qubes-doc Dec 9, 2015

Merged

fixed broken /en/ links #71

@adrelanos

This comment has been minimized.

Show comment
Hide comment

bnvk added a commit to bnvk/qubesos.github.io that referenced this issue Dec 10, 2015

andrewdavidwong added a commit to QubesOS/qubesos.github.io that referenced this issue Dec 10, 2015

Merge pull request #12 from bnvk/master
Made default categories & author on blog work QubesOS/qubes-issues#1460

bnvk added a commit to bnvk/qubesos.github.io that referenced this issue Dec 10, 2015

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Dec 13, 2015

Member

The new page ToC design (in fact, the whole sidebar) is absolutely beautiful, @bnvk. Fantastic job there.

One small thing: I noticed that it responsively moves to the bottom of the content containers on narrow screens. I wonder if it might be better to have it at the top somehow (collapsible?), since most page visitors on narrow screens probably won't see it this way until they've already read through the whole page.

Member

andrewdavidwong commented Dec 13, 2015

The new page ToC design (in fact, the whole sidebar) is absolutely beautiful, @bnvk. Fantastic job there.

One small thing: I noticed that it responsively moves to the bottom of the content containers on narrow screens. I wonder if it might be better to have it at the top somehow (collapsible?), since most page visitors on narrow screens probably won't see it this way until they've already read through the whole page.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment