Synopsis: Synopsis: This is a talk page for the Mageia Linux wiki page Installing Google Chrome in Mageia Linux. Hashtags #IfItAintBrokeDontFixIt #WhereIsTheIntroduction #WikiIsNotABook Created: 16:04, 9 January 2021 Author: Doktor5000 |
--doktor5000 (talk) 16:04, 9 January 2021 (UTC) A few parts are not really necessary, and adding the key is overly complicated and can be reduced to one command:
Neither at needs to be installed nor atd needs to be running, installation and chrome itself works fine without those.
And this whole section
d=~/Downloads/Google_Linux_key mkdir -p ${d} 2> /dev/null cd ${d} wget https://dl.google.com/linux/linux_signing_key.pub #download Google's key /bin/sudo rpm --import linux_signing_key.pub #import the key
can be replaced with
/bin/sudo rpm --import https://dl.google.com/linux/linux_signing_key.pub
--
Contents
- 1 Introduction
- 1.1 Doubling of introduction
- 1.2 codegazer response to "doubling of introduction"
- 1.3 end of codegazer response to "doubling of introduction"
- 1.4 ...
- 1.5 codegazer second response to "doubling of introduction"
- 1.6 end of codegazer second response to "doubling of introduction"
- 1.7 codegazer second response addendum-1 to "doubling of introduction"
- 1.8 end of codegazer second response addendum-1 to "doubling of introduction"
- 1.9 You didn't get the point...
- 1.10 #ThisIsNotTwitter
- 1.11 codegazer response to "#ThisIsNotTwitter"
Introduction
A discussion about the Mageia wiki page Installing Google Chrome in Mageia. Including the following points:
- Different methods for downloading the Google signing key for Google Linux rpms
- Merits or lack thereof of the "introduction template" addition to codegazer's contribution Installing Google Chrome in Mageia.
In this example here , we show how the introduction template can be made a bit more useful by adding a pseudo-heading of Synopsis in bold text with a light blue background and complementing the actual Introduction section in the body of the wiki text.
Some benefits:
- the original heading and entry in the table of contents are retained,
- the introduction is where it belongs: integrated with the wiki text body immediately following the table of contents
Doubling of introduction
-- sturmvogel
The introduction was removed because if you use a proper introduction template [[1]] all informations belong there. Now you have the same content in your unnecessary introduction which is already present in the introduction template on top of the page (the blue shiny box on top of your page).
codegazer response to "doubling of introduction"
Update: 2022_04_17 at 21:55 GMT
-- codegazer
Leber Sturmvogel,
Thank you for taking the time and trouble to connect via talk to discuss this.
I politely disagree with your comment regarding the Introduction.
Using the introduction "template" actually moves the text of introduction away from the body of the wiki page.
The templated version has no heading and it does not appear in the table of contents. In addition, the strange light blue text background actually makes the text of the introduction harder to see and it does not "flow" with the rest of the text of the wiki page when reading through.
This is not necessary and hides the Introduction away. Why do that? Is there any benefit?
I recommend that either the introduction template be modified to meet the requirement to:
a) include in table of contents, b) have an heading "Introduction", c) Have the same text foreground and background colours so it is not lost by non-association, d) be positioned close to and with the rest of the text body.
Otherwise, it's simply too invisible and not on the flow of readable text. Simply not good enough IMHO.
If you want to use something like the introduction template then maybe it should be for something else that the reader does not need to see clearly but might want to find after careful study.
Some examples:
a) list of hashtags, b) list of related pages, c) some useful statistics about the page: c.1) date first added, c.2) date last updated, c.3) date for scheduled review by #mageia-doc team, c.3) how many times the page has been read, c.4) list of connections to the page by country of origin d) status of the page: draft, current, obsolete, archived, e) which versions of Mageia Linux the page is relevant to
etc etc.
I feel confident that you can think of creative and helpful data for such a header.
Mit freundlichen Grüßen codegazer (aka: Paul)
end of codegazer response to "doubling of introduction"
...
-- sturmvogel
This is a well known and established form for a short summary of a book/magazine/article. It is the same like a back cover text of a book. The back cover text of a book isn't shown in table of contents either.
The template was not created by me. It is used at over 150 pages in the Mageia wiki and is also mentioned in the "Create a wiki Howto".
a) include in table of contents, * the back cover text of a book isn't shown in table of contents either. It's purpose is to have a short summary/introduction without the need to read the book. b) have an heading "Introduction", * back cover text doesn't have a heading "back cover text" either c) Have the same text foreground and background colours so it is not lost by non-association, * It wouldn't be a template then. It would be simple text. The intention is to have a visible short summary of the article for the user to decide if the article contains any usefull informations for him without reading through thousends of "examples" and needless steps. d) be positioned close to and with the rest of the text body. * The intention is to have a visible short summary of the article for the user to decide if the article contains any usefull informations for him without reading through thousends of "examples" and needless steps. The majority of people read an article from top to bottom. So the position at the top seems logical.
codegazer second response to "doubling of introduction"
Update: 2022_04_18 at 00:48 GMT
-- codegazer
This is not a book/magazine/article. It is a wiki page.
Hiding the introduction in a separated section of text using colours that are not used in the body of the text and then not labelling it as an "Introduction" and not including the "Introduction" in the table of contents is confusing at best. Not helpful.
It does not matter how many pages this has been forced into it makes no sense and is not helpful to the reader IMHO.
The argument "Use X because N others use it" is like saying: "Eat sh?t because 50million flies cannot be wrong!". This does not work does it?
Unless you can help me understand what positive benefit there is for using the "introduction template" to this wiki page, to the Mageia wiki, or to Mageia I see no benefit in using this template.
It can be mentioned in many places but that does not change the fact that it is not a helpful option. If you want to use it for your wiki page, please go ahead.
I am not convinced and I do not plan to use it.
I think you should be asking the person who added the "introduction" template to remove their "introduction template" because there was already a perfectly good introduction complete with heading, entry in the table of contents and integrated with the body of the text of the wiki. Who did add it? I must look through the edit history and find out.
end of codegazer second response to "doubling of introduction"
codegazer second response addendum-1 to "doubling of introduction"
Update: 2022_04_18 at 01:21
-- codegazer
The edit history shows that the "introduction template" was added by Cmoifp at 08:21 on | 9 September 2021
end of codegazer second response addendum-1 to "doubling of introduction"
You didn't get the point...
-- sturmvogel
Then remove the template from "your" pages. In my first post i wanted to tell you that you have the SAME content TWICE in "your" "Installing Google Chrome in Mageia" page. But you didn't get it...
Honestly i won't care about "your" pages in the future. But i can tell you that the are far from readable, simple, understandable, consistent and easy to follow. But whatever...
#ThisIsNotTwitter
-- sturmvogel
In Mageia Wiki there are no hashtags. It's called Categories (it's also documented).
codegazer response to "#ThisIsNotTwitter"
-- codegazer (Update: 2022_04_18 at 12:37 GMT)
Genau: wiki != Twitter
Reading the story of Hashtag: they were introduced on Twitter.
However, hashtags are not exclusive to Twitter and are used in other systems.
Basically, a hashtag is searchable text string. As long as a platform has text search capability, hash tags will work.
Not to detract from the category tags which serve well to bring the user to index pages for those defined categories.
Return to top