Difference between revisions of "Talk:Main Page"
MaxSchiller (Talk | contribs) (→markup stuff) |
MaxSchiller (Talk | contribs) (→markup stuff) |
||
| Line 83: | Line 83: | ||
:Also, when creating Articles, they shouldn't be pluralized. For instance the correct article is [[password]] rather than passwords. If you want the plural link, you can use <nowiki>[[password]]s</nowiki> (appears as [[password]]s) to pluralize, but there is no syntax (aside from piping) for unpluralizing. On the topic of linking (or piping) when you pipe in a wiki, the first letter's capitalization does not matter. [[Password]] and [[password]] yield the exact same result, and so generally when creating multi-word articles you should either leave them as all lowercase (first will be capitalized automatically) unless it's a proper noun. I know it can get a little anal, but that's what asspies with too much free time are here for, and it saves a lot of effort down the road when you have strong precedents set up in the beginning. {{User:Mike/Sig}} 14:18, 2 May 2012 (MSK) | :Also, when creating Articles, they shouldn't be pluralized. For instance the correct article is [[password]] rather than passwords. If you want the plural link, you can use <nowiki>[[password]]s</nowiki> (appears as [[password]]s) to pluralize, but there is no syntax (aside from piping) for unpluralizing. On the topic of linking (or piping) when you pipe in a wiki, the first letter's capitalization does not matter. [[Password]] and [[password]] yield the exact same result, and so generally when creating multi-word articles you should either leave them as all lowercase (first will be capitalized automatically) unless it's a proper noun. I know it can get a little anal, but that's what asspies with too much free time are here for, and it saves a lot of effort down the road when you have strong precedents set up in the beginning. {{User:Mike/Sig}} 14:18, 2 May 2012 (MSK) | ||
| − | ::Another thing I'm running into is section header handling. Single = section headers should really never be used in articles. | + | ::Another thing I'm running into is section header handling. Single = section headers should really never be used in articles. They work more or less like ==double section== only they force everything below them to be listed as a sub section. Their purpose is solely for handling archives. You would say, take a talk page on Wikipedia that has 50+ section headers and go back with single sections to sub section them off by dates or similar methods. {{User:Mike/Sig}} 02:34, 3 May 2012 (MSK) |
==Templates:== | ==Templates:== | ||
[[:Category:Templates]] has been populated with every template we have, and I deleted [[Template:Toggle]] and [[Template:PrettyTable]] because they were weird and unused. If you make a new template be sure to add noincludes and the category after the template so every page the template's on doesn't also get tagged as being a template. {{User:Mike/Sig}} 09:28, 7 May 2012 (MSK) | [[:Category:Templates]] has been populated with every template we have, and I deleted [[Template:Toggle]] and [[Template:PrettyTable]] because they were weird and unused. If you make a new template be sure to add noincludes and the category after the template so every page the template's on doesn't also get tagged as being a template. {{User:Mike/Sig}} 09:28, 7 May 2012 (MSK) | ||
Revision as of 22:26, 19 May 2012
wiki todo
Trying to get the following things done by the end of May:
- Knock out cleanup and expand tags - people should be working on this constantly.
|
Wiki To-Start
- Series on information gathering (traceroute+tcp traceroute and mtr, amongst other things)
- Interpreted Language updates: PHP, Ruby, HTML, CSS, JavaScript
- Interpreted Language updates: Add a "Security" section to each (existing) language; explaining dangerous functions, common mistakes, and sanitizing user input
- Something about heap overflows and format string vulnerabilities
- Articles on using debuggers (GDB, OllyDBG, IDA Pro) and disassemblers (Objdump) and hex editors
- Articles on executable file formats (PE and ELF formats)
- "How to get involved" page or forums post
- Open wiki registration (after all above is completed)
- Java (not required)
Wiki in progress
- IRC rules & Posting guidelines
- Forums online
- Update/Redesign main page
- xo is working on a metasploit page
- xo is working on an integer overflows page
- bitwise math cleanup job
- C page update - some can be imported from old forums, get at hatter for info
- Assembly updates : linux assembly, assembly basics rewrite as assembly
- Information Gathering: nmap, dig
- Gentoo Installation - some new, some importing to be done from http://www.blackhatacademy.org/academy_x/GENTOO_f9834Axlfu83VDSs9.txt
Wiki done (but no official release yet)
- Logistics: Security101:About, Security101:Privacy_policy, Security101:General_disclaimer
- Kolkata
- LUA
- null-free_shellcode
- alphanumeric shellcode
- unsafe string replacement
- 64 bit additions to buffer overflow page
Hatter 14:20, 2 May 2012 (MSK)
Chimera Todo
- Artwork
- Full LXDE theme
- Disclaimer
- Add custom LXDE app menu with links to added tools (update .desktop files in /usr/share/applications)
- Update installed packages (if needed)
- PDFify the wiki and add to /opt/docs - this will take some time, due to wiki todo. was thinking we'd release chimera around the same time as a lot of our updates. ~hatter
- Bind to disk tool - hatter
- Yaourt & Pacman repos - hatter & kratos
Done
- grsec/pax kernel
- hardened apps
- Domain name - chimeralinux.org - ErrorProne
- BHA Tools Updated in /opt - ErrProne
Buggy
- Crashes while outputting to /dev/null. Lighten up policies? - I think this is a /proc/mounts and /etc/fstab thing.
Not done/started
- Finish chimera tweaking guide - ErrorProne
- Hardening chimera article
- Fix /opt packages. add YAML:XS
markup stuff
Templates and example markups at Test.
Hatter 13:58, 2 May 2012 (MSK)
Contents
A few things I noticed should be addressed, so I'm opening up this talk page as a temporary community portal until project pages are set up, or a permanent destination is decided on. First:
Templates:
When making a template, it's important to pay attention to where you add the <includeonly> and <noinclude> tags, specifically in regards to spacing. It's counter intuitive, but when you add the tags on the next line, it incorporates the break in the template's transclusions. It's directly against good form with basic HTML, but is necessary for good layout, because you can't remove anything from a template without substituting it and defeating the point of using a template. A quick example of what I'm talking about:
<includeonly>
<div style="padding: .2em .3em; margin: .2em .2em; background-color: #FFF6BF; border: solid 2px #FFD324; font-size: 107%;">'''{{{label|Notice:}}}''' {{{1}}}</div>
</includeonly>
Would produce a template with a break at the top and bottom, and in this example would be more than likely desired, but if not paid attention to can lead to undesirable whitespace.
The other thing is talk pages: A good idea for those of you who don't know is to read up briefly here on the general use, but with a wiki that's rapidly expanding like this one is and will be, there's almost no documented discussion going on. The jist of the article is basically use the discussion pages, sign your comments (add four tildes ~~~~) and about general layout (indent for a response with :)
Overall this wiki is very new and so there are no help articles for actually using the wiki, so anybody who has any questions should just ask them. It's a wiki and nothing gets broken by talking at people on it and we have several people who are good enough at wiki to help anything. Mike (Talk) 13:46, 2 May 2012 (MSK)
- Also, when creating Articles, they shouldn't be pluralized. For instance the correct article is password rather than passwords. If you want the plural link, you can use [[password]]s (appears as passwords) to pluralize, but there is no syntax (aside from piping) for unpluralizing. On the topic of linking (or piping) when you pipe in a wiki, the first letter's capitalization does not matter. Password and password yield the exact same result, and so generally when creating multi-word articles you should either leave them as all lowercase (first will be capitalized automatically) unless it's a proper noun. I know it can get a little anal, but that's what asspies with too much free time are here for, and it saves a lot of effort down the road when you have strong precedents set up in the beginning. Mike (Talk) 14:18, 2 May 2012 (MSK)
- Another thing I'm running into is section header handling. Single = section headers should really never be used in articles. They work more or less like ==double section== only they force everything below them to be listed as a sub section. Their purpose is solely for handling archives. You would say, take a talk page on Wikipedia that has 50+ section headers and go back with single sections to sub section them off by dates or similar methods. Mike (Talk) 02:34, 3 May 2012 (MSK)
Templates:
Category:Templates has been populated with every template we have, and I deleted Template:Toggle and Template:PrettyTable because they were weird and unused. If you make a new template be sure to add noincludes and the category after the template so every page the template's on doesn't also get tagged as being a template. Mike (Talk) 09:28, 7 May 2012 (MSK)
