Btw if you like, you could get access to edit common.css too.
In that case, let me know. Might have to add you interface administrator to be able to edit that page.
Security precautions against bricking the wiki:
Let me know if that makes sense.
Also an option. We likely could use wiki templates for that. Let me know if you like help with that.
Yes please. That would be very helpful.
Very well understood. 
That would be great. We could use a template or maybe change make changes per page. Not sure if we want to change the theme per page though (a little to extreme) , we just want little tweaks.
https://www.mediawiki.org/wiki/Extension:Theme
The Theme extension allows loading of themes (preset CSS to change the appearance of a skin). Users can determine their preferred theme by configuring this in their preferences. The
$wgDefaultThemevariable can be used to control what theme is being used site-wide, and theusetheme=Xparameter is accepted on a request to change the theme on a per-pageload basis.
Will see about the wiki templates in a day or so.
Done. Added interface administrator and widget editor while at it (equally sensitive).
I would go with what you like to work on.
If you like to have Extension:Theme - MediaWiki - that looks easy - can install. Just let me know.
Thanks
Was looking at Dev/About Infrastructure - Kicksecure . This would be a good opportunity to test out some new themes and/or skins for the wiki. Could we please try installing Extension:Theme - MediaWiki
Will work on it. While I am at it…
Extension:Theme allows to change the mediawiki skin.
So at the same time, we need to install another skin(s). Here is a link to a post where I post links to other mediawiki skins:
There might be other skins too to be found on search engines too. Needs to be Freedom Software.
Skins we have currently installed are listed here:
Having a different skin per page may provide sufficient visual difference for Whonix vs Kicksecure.
Extension:Theme however does not look like an extension that provides multiple MediaWiki:Common.css. Customization may or may not be limited and/or difficult.
Is that what you suggest?
Patrick via Whonix Forum:
Will work on it. While I am at it…
Extension:Theme allows to change the mediawiki skin.
So at the same time, we need to install another skin(s). Here is a link to a post where I post links to other mediawiki skins:
Thanks.
There might be other skins too to be found on search engines too. Needs to be Freedom Software.
I’ve been looking at all the different skins available. It seems hard to
tell if they would work (look good) on whonix.org just by seeing a few
pics. From what I’ve seen lighter colors would look best. Not many
people would go like the darker (black, brown) colors.
Color scheme will be important to choose. Anyone have any colors that
they would prefer? Or any websites that would be good examples?
Skins we have currently installed are listed here:
Login required - WhonixHaving a different skin per page may provide sufficient visual difference for Whonix vs Kicksecure.
I agree. Plus it might take to much time to customize the the page
manually.
Extension:Theme however does not look like an extension that provides multiple MediaWiki:Common.css. Customization may or may not be limited and/or difficult.
Is that what you suggest?
Lets go with Extension:Theme. (no customization) Better to go use work
thats already been completed for use. Looks like a lot of time when into
making many of those skins “just” right.
From this point on marks the start of Work performed for Google Season of Docs 2019.
I’m planning on working closely with the Kicksecure developers for documentaion develepment. I’d greatly value any feedback.
There are two additions to my project that I believe require separate threads to make it easier to follow issues.
Awesome. Ping me for feedback on any specific pages you are working on.
I’m trying to use smaller bit size paragraphs for the about page and introduction similar to Tails - How Tails works
For example:
Kicksecure is an security focused (non-anonymous) Linux distrition that aims to provide an advance and highly secure computing environment in its default configuration. Numersous enhancements have been pre-built into the the codbase which provides defenese in depth while maintaining usabililty.
Kicksecure is an complete desktop operating system which is designed to be run ontop of your operating system using a hypervisor. This configuration further hardens the OS while also allowing cross-platform compatibilty with popular operating systems.
Writing the Kicksecure About page: Why use kicksecure over say; hardened debian or any other OS. What features do we what to focus on. Obviously we want to mention debian, We don’t want to overload the reader with to much info. Similar in structure to Tails - How Tails works
Note: I find pages such as https://whonix.org/wiki/Main_Page very well writen and very informative but it seems like to much information. Almost like we are trying to “sell” Whonix a little to hard to beginners who will likely have no idea what much of that language means.
That page is probably not found often by beginners. Only for those who dig a big deeper. It is like an “advanced introduction”?
https://www.whonix.org provides a (hopefully) simpler, more high level introduction?
Yes.
If you have available, feasible, ok…: read it to a laymen.
Text is not bad but presentation a bit underdeveloped imho.
Usability wise, we can always look for comparison at popular either similar projects or even from other fields.
Good. This can later become a link.
This is a bit hard to understand for a laymen.
Ok
Got it.
Likely because the correct syntax must be learned to contribute. Not easy like Whonix wiki.
Looking at other project wiki’s. Came up with different language. This look better? Looks more like good start to an “About Kicksecure” page. Going to start adding content to the wiki. Where would be a good place to add? Kicksecure - A Security Hardened Linux Distribution
Kicksecure is a free and open-source (non-anonymous) Linux distribution focused on security that aims to provide an advance and highly secure computing environment in its default configuration. Developed from the ground up according to a formidable – and time proven – defense in-depth security module. Kicksecure’s layered defenses provides better protection from many types of viruses that can be encountered “In the Wild”.[ref]Viruses that have not been contained or eradicated through operating system security updates. These updates plug holes in software which the virus would use to compromise the operating system. see; https://www.pcmag.com/encyclopedia/term/44855/in-the-wild for more on this[/ref]
Keeping a broad user base in mind through out development resulted in an operating system that is both secure and highly flexible. This means Kicksecure can be used for everyday “general-purpose computing” or for more risky activities where an highly advanced security-centric platform is required.
Kicksecure is an complete desktop operating system with an hardened Debian base designed to be run in a virtual machine (VM) on top of the host OS . This configuration leverages the security benefits gained from running an operating systems in an virtual environment while also allowing cross-platform compatibility with popular operating systems.
Numerous applications come pre-installed with safe defaults which can be used immediately upon installation with minimal user input. Since Kicksecure is Freedom software users may install any application of their choosing[ref]Some example of freedom software are Whonix, Debian, and Qubes OS[/ref] with no restrictions placed on how Kicksecure can be used, customized or modified.
Edit: Broke up the above content into more bit size chunks. Will look better for a book like structure imo.
For Kicksecure, I’d recommend we go with an even more barebones version of the Tails example you linked. Practically a landing page that links to more advanced documentation if the user is curious enough to research it. Otherwise we state the main point of Kicsecure and how it differs from Whonix.
Thanks HulaHoop.
OK, Very basic landing page, but point out features that would be desirable / useful to users. Add links for anything we want to highlight. Users that are curious to learn more.
Pages that could be linked from landing:
About Kicksecure
Designs and Goals
Installation instructions
FAQ (This page got to long for Whonix wiki. Maybe good to have one for Kicksecure though)
[…]
Main documentation page (TOC)
Looking at the Whonix wiki. I don’t see a reason to have both an “Overview” and About" Kicksecure page. That might be a little redundant since Kicksecure is not as complex as Whonix.(i.e. no Tor)
About can clarify the relationship with Whonix while Overview describes what ithe main idea is that makes it an independent project?
Makes sense. Point out Kicksecure = security focuses. Whonix = anonymity . Would be good to state bluntly they are separate projects. Link to a move detailed Overview of Kicksecure.
Starting to fall into place now. 
I don’t disagree but one more point on clarification.
By presentation I meant formatting, theme, style.
For example https://www.whonix.org/ has a better presentation than any Whonix wiki page.
I.e. the contents of the Tails homepage is not bad but the visual impression is not that of lets say https://www.torproject.org/, https://elementary.io/ (for lack of better examples found quickly).
Btw not just wiki’s. Better to compare with homepages.
The reason we are using a wiki (with some skin) and not a homepage is lack of resources.
Very good! Some nits…
Yes.
Dunno what advance means here.
General Note: as a non-native English speaker my judgements on English language interpretation may be wrong sometimes.
Btw did you see Wikipedia? Could you please have a glimpse at a few articles there? Just for the general style. Perhaps introductions texts could be inspired by such language (since we have non-native English speaking users with only basic levels of English language).
Not sure in the wild vs off the shelf vs targeted malware (using viruses even though less correct technically it is better understood by non-computer, non-native speakers) is important enough to mention there.
Btw we have:
Malware, Computer Viruses, Firmware Trojans and Antivirus Scanners
Seems unfit there.
Not sure development philosophy has a place there?
OS: abbreviation, not well known
host OS: rewrite to Windows, MacOS, Linux since not well known term
Freedom Software
Yes.
This is not great but may be required as long as hosted on whonix.org.
Yes.
Good point.
It’s perhaps for different levels of complexity / attention / difficultly.
For example while looking at https://www.crowdstrike.com I just saw they briefly describe their products. While not Open Source (probably, I didn’t find) I didn’t get the slightest technical details how they could implement that. The homepage (Kicksecure - Secure by Default Operating System until moved to kicksecure.com, if we get there one day) would be “the buzz”.
About page would be more technical getting. And linking to further pages from there could get to the actual meat so to speak.
It’s important that the homepage explains the product as concise and clear as possible. It’s to reduce bounce rates for people who think they found something irrelevant but they actually found something suitable for what they were looking for. It should motivate to take action, i.e. download.
I guess that’s the general philosophy nowadays and also what users expect since all popular projects do that?
Yes. Perhaps a small wiki table?
OK
Kicksecure.com would be ideal instead of a “skin” to separate the projects. But I think we can make it work well.
Mostly a habit to use words to “jazz” up content a little bit i guess. Wrong use of “Advanced”. Or wrong placement.
Was looking at Wikipedia:Very good articles - Simple English Wikipedia, the free encyclopedia . There is only 34 Very Good articles in wikipedia. Interesting how those pages are structured. Each paragraph is very specific. Every sentence conveys a short, very informative fact about the subject. With each sentence building upon the previous sentences.
Didn’t find any “IT good pages”. The closest thing would be the “Evolution very good page” Evolution - Simple English Wikipedia, the free encyclopedia. Its a subject somewhat similar in complexity but laid out and structured in a simple way.
A curiosity. I wonder what people would think if we started writing Whonix wiki like that. Remove most adjectives, unneeded language.
Could Kicksecure be written like that. It seems from looking at other project with less resources a lot of effort is spent trying to set the project apart from others using big flashy Catch phrases. Kinda like people expect to see that sort of thing.
Not sure beginners can appreciate “in the wild”
Would be better.
yes.
Mostly opinion based. Doesn’t belong.
OK
Ok.
Looking at https://www.torproject.org/ you get all the info you need right off the bat. But have the option of scrolling down for more info.
Yes. Needed to avoid confusion.
Extension:Theme - MediaWiki and Skin:Chameleon - MediaWiki is now installed, see Login required - Whonix.
I was hoping it could be used on a by-page base by simply using
usetheme=chameleon
on any wiki page. But I could not make that work.
Extension:Theme - MediaWiki links to example link ShoutWiki — express yourself and be heard!
But using it that might be incompatible with what we want to do.
Also does not look great
Whonix ™ - Anonymous Operating System
dunno if this is a skin or extension issue. Looks like a skin issue. As per
Login required - Whonix
users can choose a skin in their mediawiki account settings. Using that preview the skin does not look great.
Could be an issue with https://www.whonix.org/wiki/MediaWiki:Common.css
Edit:
Kicksecure - Secure by Default Operating System
looks a bit better.