[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
talk:start [2012/09/16 20:49 (UTC)] – alienbob | talk:start [2012/12/07 02:08 (UTC)] – cheap pandora charms pandora053 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | + | Wu rises and although big Tang Deng Ren is also very curious, however proper | |
- | **Main Page Talk** | + | "Talk of how?"Wu since smiled |
- | + | Li Qiang of"go, we surrender ……" | |
- | 082012@1618hrsEDT - I was wondering if there was a way to use the standard Slackware logo and wallpaper from the Slackware website for this wiki. It would give it that comfortable old shoe type feeling, I think. ~V. T. Eric Layton | + | I also have [http://pandora.charmclub-uk.com/ cheap pandora charms] a condition |
- | + | <a href="http://inevoware.com/kivendi/members/pandora048/"> | |
- | ------ | + | |
- | >I think that depends on whether it is decided to place the wiki under a slackware.com subdomain or slackdocs.org is going to be favoured. If it is not a slackware.com site I would not want to use a full set of Slackware visuals. \\ --- //[[wiki: | + | |
- | + | ||
- | ------ | + | |
- | >> | + | |
- | + | ||
- | ------ | + | |
- | The front page says that you must create an account to be able to edit the wiki... OK, but where is the link to create such an account? I love Slackware and I'd love to participate! (and I have my own Slackware wiki as well: http://www.gilandre.net/ | + | |
- | + | ||
- | ------ | + | |
- | >Simple. Click " | + | |
- | + | ||
- | ------ | + | |
- | + | ||
- | 082312@2100hrsEDT - I've created a hyperlink on the main page in the paragraph under the Help topic where it says "you must create an account" | + | |
- | + | ||
- | ------ | + | |
- | Is it really useful to hyperlink every mention of " | + | |
- | " | + | |
- | http://docs.slackware.com/ | + | |
- | \\ --- // | + | |
- | + | ||
- | + | ||
- | ---- | + | |
- | + | ||
- | + | ||
- | Yes, NEWS looks out of step with the rest of the page. I've changed it. --- // | + | |
- | ------ | + | |
- | + | ||
- | == NOTICE TO ALL == | + | |
- | + | ||
- | **PLEASE** do not edit the Main Page without consulting someone on the admin/ | + | |
- | ------ | + | |
- | + | ||
- | I think a link in the " | + | |
- | --- // | + | |
- | + | ||
- | ------ | + | |
- | + | ||
- | >You are absolutely correct zithro. I will alert Eric or Niki to change the link to: http:// | + | |
- | Thanks for alerting us to this. | + | |
- | + | ||
- | --- // | + | |
- | + | ||
- | ------ | + | |
- | + | ||
- | Do the site admins intend to follow the documentation structure recommended on [[http:// | + | |
- | + | ||
- | ------ | + | |
- | >Matthew, the TOC is just a list of suggestions, | + | |
- | --- // | + | |
- | + | ||
- | ---- | + | |
- | >>@ Matthew & Marcin - We are still in flux over the TOC issue, I believe. I am of the belief that the main page needs a traditional table of contents (or a link to one in the toolbox). Currently, I'm using the [[http://docs.slackware.com/? | + | |
- | + | ||
- | ---- | + | |
- | + | ||
- | Shouldn' | + | |
- | + | ||
- | --- // | + | |
- | + | ||
- | ---- | + | |
- | + | ||
- | + | ||
- | + | ||
- | Also, while I'm thinking about it... The "Navigation" | + | |
- | + | ||
- | * Navigation | + | |
- | + | ||
- | * Main Page (loop link) | + | |
- | * Project Charter | + | |
- | * Staff | + | |
- | * Site News | + | |
- | * Table of Contents | + | |
- | * Random Article | + | |
- | * Help | + | |
- | + | ||
- | * Search Box | + | |
- | + | ||
- | * Toolbox | + | |
- | + | ||
- | * What Links Here | + | |
- | * Recent Changes | + | |
- | * Media Manager | + | |
- | * Site Index (Map) | + | |
- | * Printable Version | + | |
- | * Permanent Link | + | |
- | * Cite This Article | + | |
- | + | ||
- | * Slackdocs | + | |
- | + | ||
- | * Docuwiki Manual | + | |
- | * Docuwiki Syntax | + | |
- | * Slackdocs Style Guide | + | |
- | + | ||
- | * Slackware Links | + | |
- | + | ||
- | * Slackware.com | + | |
- | * Slackware-Current Change Log | + | |
- | * Package Browser | + | |
- | * Slackware Mirrors | + | |
- | * LinuxQuestions.org/ | + | |
- | + | ||
- | * Language | + | |
- | + | ||
- | * QR Code | + | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | Thoughts? | + | |
- | + | ||
- | ---- | + | |
- | Time's up for me tonight but I think you are making valid points about the sidebar Eric. I will work on that tomorrow.\\ | + | |
- | + | ||
- | ---- | + | |
- | + | ||
- | >Good night, Eric. Pleasant " | + | |
- | + | ||
- | ------ | + | |
- | I changed the sidebar content to align mostly with what you suggested. I think there is a better logical separation of topics now. \\ What I found out in the process is that the two pages [[slackdocs: | + | |
- | + | ||
- | >Looks really good, Eric. My only suggestion (complaint ;-) ) would be that we need to use consistent capitalization rules for the sidebar headings and the links within the sidebars (see my suggestion above). I prefer this because I'm a hard-ass when it comes to the written word. I think texting and chatrooms have done major damage to proper writing and punctuation over the last decade. I mean how hard is it to let your left pinky hit that Shift key? :-) It makes for a more professional presentation; | + | |
- | + | ||
- | >Oh, and if someone hasn't already merged the styleguide and editing_rules, | + | |
- | + | ||
- | ------ | + | |
- | Looking at the start page and thinking about some people' | + | |
- | + | ||
- | > | + | |
- | + | ||
- | ------ | + | |
- | + | ||
- | All good! Things are really shaping up. The Main Page is the hook. It needs to be enticing, informative, | + | |
- | + | ||
- | + | ||
- | ------ | + | |
- | + | ||
- | Has there been a syntax decided on to note which version of Slackware (or application) a page is applicable to? Subtle changes that aren't caught/ | + | |
- | < | + | |
- | < | + | |
- | + | ||
- | Also, my 2 cents: " | + | |
- | ------ | + | |
- | Please follow our guidelines about [[slackdocs: | + | |
- | I noticed a [[: | + | |
- | + | ||
- | >Re: slackpkg on main page -- myeh... it's not necessary, but it is something a beginner would need to use after installing their system. \\ --- //[[wiki:user: | + | |
- | + | ||
- | >Re: slackpkg on main page: Noting slackpkg on the main page is not necessary since it should be documented in the install article and will be covered in all package management tutorials. \\ --- // | + | |
- | + | ||
- | Been thinking this over. What we might want to have instead is a chapter " | + | |
- | + | ||
- | ------ | + | |
- | + | ||
- | + | ||
- | I think it would be a good idea to add a link to the beginners_guide following this link: | + | |
- | * [[slackware: | + | |
- | Like so: | + | |
- | * [[slackware: | + | |
- | --- // | + | |
- | + | ||
- | >Thanks for this suggestion, Mario. Oh, I've moved your post to the bottom of the page (older at top - newer at bottom). Cheers! | + | |
- | + | ||
- | ------ | + | |
- | + | ||
- | I've been wondering, if there is a good article (example: [[http://www.slackwiki.com/Building_A_Package|this guy]]) on some other site, do we simply create our own article and link to it as a source, or do we ask permission to move the article wholesale to the wiki? --- //[[wiki: | + | |
- | + | ||
- | ------ | + | |
- | I am not in favour of copying whole articles into our wiki, except if the person doing the copying is also the author of the original article. You can use another article as the source or inspiration for your own article here, and if you are re-using parts of it, it is good practice to mention it in the **Sources** section. \\ --- //[[wiki: | + |