Difference between revisions of "Talk:Main Page"

Revision as of 13:14, 3 May 2012

current todo

Trying to get the following things done by the end of May:

• Series on information gathering (meaning nmap, dig, and traceroute and mtr could use an overhaul, amongst other things)
• Interpreted Language updates PHP, Ruby, HTML, CSS, JavaScript, LUA, TCL
• Shellcode miniseries kicked out for programming, 32 bit/64 bit linux asm, same for windows, User:Hatter/Windows Shellcode page, finalizing User:Hatter/Alphanumeric Shellcoding
• Finished Assembly Basics page, renamed to just Assembly (leave redirect?)
• Something about heap overflows and format string vulnerabilities
• Chimera Live OS
• Update of C page, perhaps an entry on Java (but not required)
• Finish up Gentoo Installation Page, write hardening chimera article
• Articles on using debuggers (GDB, OllyGDB, IDA Pro) and disassemblers (Objdump) and hex editors
• Articles on executable file formats (PE and ELF formats)
• Knock out cleanup and expand tags
• IRC rules & Posting guidelines
• Update/Redesign main page
• Open wiki registration (after all above is completed)
• New website
• Forums online

Hatter 14:20, 2 May 2012 (MSK)

markup stuff

Templates and example markups at Test.

Hatter 13:58, 2 May 2012 (MSK)

general policy

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 Aritcles, 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 (asside 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 capitalised 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. Sinlgle = section headers should really never be used in articles. The work more or less like ==double section== only they force everything below them to be listed as a sub section. Their purpose is soley 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)