[HOME] [DOWNLOAD] [DOCS] [BLOG] [SUPPORT] [TIPS] [ISSUES] [Priority Support]

New Qubes Website! New Whonix Website?


#131

Good day,

The font actually was a suggestion by him. If you recall, initially, I used a much thicker one. In regards to the wiki/faq, like mentioned, his recommendation have (to the best of my abilities) been implemented, though it still needs to be decided which style/appearance suits best.

Done. Forgot to include the font containers locally…

Have a nice day,

Ego


#132

What’s your best guess? I guess the first one http://egobits1.github.io/wiki2/. (If I remember right, we agreed earlier that a sidebar is acceptable for non-mobile pages.)


#133

Good day,

Yes, Personally I feel like such a step-by-step approach is the best way to do things. As mentioned before, I feel like minimizing the amount of text a user sees at once makes what is there easier to handle.

Have a nice day,

Ego


#134

Yes. Reducing cognitive load. Sounds “plausible” (as discussed that workd some time ago) to me. Please go for it.

What about Thumbs.db? Can you remove please it if it is not required?


#135

#136

Good day,

Sorry, didn’t even notice that. Is a file Windows occasionally seems to create for some reason to handle preview icons. Has been removed. Also removed /wiki3 as it is a leftover from a testing phase.

Have a nice day,

Ego


#137
  • ./css/yQiAaD56cjx1AooMTSghGfY6323mHUZFJMgTvxaG2iE.woff2
  • ./css/0dTEPzkLWceF7z0koJaX1A.woff2

Cannot review those files. Any chance they exploit either our server or a client browser? Any way to compare them with official sources or with stuff that comes already preinstalled with Debian?

Also do those have a compatible license?


#138

Good day,

The font recommended by @elioqoshi (Raleways) is sadly provided by Google in this very specific format. It is a font container formats (https://en.wikipedia.org/wiki/Web_Open_Font_Format) which can’t really be opened/checked though this shouldn’t be necessary since these cannot contain anything other than the specific design for a font according to their own standard. You could, if you wanted to, convert it to a TrueType-Format though all this would do would enable you to use it as a font in Word. Even then, you can’t look into these files as any texteditor will output gibberish. Only thing we could do here would be to completley pass on custom fonts like Raleways all together.

License wise, according to their own site we may “use them in any non-commercial or commercial project.” The specific license is apparently the so called “SIL Open Font License” which, asside from certain extensions only applying to those who modify a font, seems to be point for point identical to GPL.

Have a nice day,

Ego


#139

which can’t really be opened/checked though this shouldn’t be necessary since these cannot contain anything other than the specific design for a font according to their own standard.

IMHO if we can’t inspect it then its not a good choice.


#140

Good day,

Like mentioned, files like these can be left out then, though if we do that and also don’t use any calls from outside sources, we won’t be able to use any outside fonts either.

For comparison sake:

With the recommended font:

My initial design which doesn’t need ouside sources or “shady” files:

Have a nice day,

Ego


#141

Doesn’t look so bad for me. We can still change it later if desired. Yes, please go for it.


#142

Good day,

Any references and unreadable files have been removed.

Have a nice day,

Ego


#143

I am not sure about the contents of http://egobits1.github.io/wiki/. Or the link to http://egobits1.github.io/wiki/. Perhaps the wiki button on the top should just redirect to https://www.whonix.org/wiki/Main_Page in meanwhile?


#144

Good day,

First of all, yes, the Qubes-URL (or any outside URL for that matter) does work. “href” simply exists to reference to any source, either local or on another server.

Secondly, changed the “Wiki-Tab” on the top to link to our Mediawiki-Documentation. We may include something later. That was what I meant when I wrote whether there already exists some content for the “Quick-Start-Guide”. Since this is just for the transition, I also linke the VBox-Download-Sections to the Wiki.

Have a nice day,

Ego


#145

Great!

Fortasse will install the new website soonish. Probably next weekend.


#146

Good day,

Exceptional news. Regarding translation and editing, I sadly had to setup everything independent of Github Pages. While it works to an extend on localhost, I still have problems getting it to run on my public server. Adding to that, the “language selector” (or rather drop-down menu) still doesn’t work properly on anything other then the lowest security setting when using the TBB which obviously isn’t an ideal state. So that needs to be addressed.

Either way, an important question would be whether we should use @torjunkie’s very thorough Quick-Start-Guide as a base or write something from the ground up: Whonix Quick-Start Guide v0.1 If the former should be the case, it could be integrated right away, still running in parallel to our “old” wiki.

Have a nice day,

Ego


#147

( My feedback to that quick start guide: Whonix Quick-Start Guide v0.1 )

I think it’s too verbose, very much so.


#148

@Ego: We’ve cherry-picked a couple pages out of your repo (they’re live now! :D), but it seems like there are some placeholder / incomplete pages in the repo. Could you look at having the master branch be “complete,” and use a separate branch for doing testing? That would make it easier for us to see that there are important changes we may need to pull down.

It’s a great landing page, thanks for all your hard work.


#149

Good day,

Sure, created a seperate branch and removed any references to my tests from the original one.

Have a nice day,

Ego


#150

Apologies I never cut down the v 0.1 version of the ‘Quick’ Start Guide for you. Been too busy.

I’ll look over what’s up on the new website page and revisit your feedback when I have a chance. There is value in editing the wiki too in various places.


splitting Whonix documentation into a short and long edition for better usability