Hi Erik, currently I've a little problem. My Fire doesn't at the moment and I've no time to fix it. So it would be nice if someone other could make a picture.
Flo
Hello,
my advice for faster way of fixing mistakes: Choose a language to start with (this is preferably English) and then write the article. Create an outline, write chapters, add screenshots... Get as much feedback as you can get. Do the guide by the shown steps and check for errors. THEN translate.
It's just easier if you don't need to fix minor issues in multiple versions.
----
On the text itself. You guys need to fix the screenshot sizes. The page loads a while and the screenshots are that huge that you cannot tell where text is and where just crap is. Crop the stuff that does not matter (e.g. services screenshot) and use thumbnails.
I would like to see the user pointed on how to create a samba share (bit more detailed though). You mentioned WinSCP which is specific to Windows and not very comfortable to use. Not sure if that is an option for anybody.
I think we do not need the disclaimer. In our law, even ping, telnet and nmap are illegal tools and it's up to the user what he is going to do with transmission. Bittorrent by itself is not illegal.
Furthermore, why do we have a huge "installation section" on every article? It is always the same. Why not create a very detailed guide and always refer to it and tell the names of the packages to install?
Altogether the article is quite nice and to the point. One could collect some links to the official transmission documentation for further reading.
-Michael
On Tue, 2012-01-17 at 13:39 +0100, Florian Ortmann wrote:
Hi Erik, currently I've a little problem. My Fire doesn't at the moment and I've no time to fix it. So it would be nice if someone other could make a picture.
Flo _______________________________________________ Documentation mailing list Documentation@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/documentation
Hi Michael,
if you think we don't need the disclaimer delete it. ;)
In my opinion it is easier to use/read if in every wiki the installation part is included. I don't like inkomplete wikis so I've to read several wikis if I want to install one thing.
I will reduce the screenshots in size and colordeph so the loadtime will get better.
Daniel
Am 17.01.2012 17:29, schrieb Michael Tremer:
Hello,
my advice for faster way of fixing mistakes: Choose a language to start with (this is preferably English) and then write the article. Create an outline, write chapters, add screenshots... Get as much feedback as you can get. Do the guide by the shown steps and check for errors. THEN translate.
It's just easier if you don't need to fix minor issues in multiple versions.
On the text itself. You guys need to fix the screenshot sizes. The page loads a while and the screenshots are that huge that you cannot tell where text is and where just crap is. Crop the stuff that does not matter (e.g. services screenshot) and use thumbnails.
I would like to see the user pointed on how to create a samba share (bit more detailed though). You mentioned WinSCP which is specific to Windows and not very comfortable to use. Not sure if that is an option for anybody.
I think we do not need the disclaimer. In our law, even ping, telnet and nmap are illegal tools and it's up to the user what he is going to do with transmission. Bittorrent by itself is not illegal.
Furthermore, why do we have a huge "installation section" on every article? It is always the same. Why not create a very detailed guide and always refer to it and tell the names of the packages to install?
Altogether the article is quite nice and to the point. One could collect some links to the official transmission documentation for further reading.
-Michael
On Tue, 2012-01-17 at 13:39 +0100, Florian Ortmann wrote:
Hi Erik, currently I've a little problem. My Fire doesn't at the moment and I've no time to fix it. So it would be nice if someone other could make a picture.
Flo _______________________________________________ Documentation mailing list Documentation@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/documentation
Documentation mailing list Documentation@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/documentation
On Tue, 2012-01-17 at 17:53 +0100, WhyTea wrote:
Hi Michael,
if you think we don't need the disclaimer delete it. ;)
Just wanted to know if there are some other reasons that I might have missed.
In my opinion it is easier to use/read if in every wiki the installation part is included. I don't like inkomplete wikis so I've to read several wikis if I want to install one thing.
Well, if a user has done this one time, he would know how to install a package. So most users skip that part and go on with the rest. I think wiki articles should be to the point. We must require some kind of knowledge of the reader and if he misses anything, there is still a search function or the forums.
I will reduce the screenshots in size and colordeph so the loadtime will get better.
Reduce the size with the implemented function in the wiki. Do not reupload images and NEVER upload images in a bad quality. The wiki resizes the images by itself and uses compression as well.
No comment on the rest?
-Michael
Daniel
Am 17.01.2012 17:29, schrieb Michael Tremer:
Hello,
my advice for faster way of fixing mistakes: Choose a language to start with (this is preferably English) and then write the article. Create an outline, write chapters, add screenshots... Get as much feedback as you can get. Do the guide by the shown steps and check for errors. THEN translate.
It's just easier if you don't need to fix minor issues in multiple versions.
On the text itself. You guys need to fix the screenshot sizes. The page loads a while and the screenshots are that huge that you cannot tell where text is and where just crap is. Crop the stuff that does not matter (e.g. services screenshot) and use thumbnails.
I would like to see the user pointed on how to create a samba share (bit more detailed though). You mentioned WinSCP which is specific to Windows and not very comfortable to use. Not sure if that is an option for anybody.
I think we do not need the disclaimer. In our law, even ping, telnet and nmap are illegal tools and it's up to the user what he is going to do with transmission. Bittorrent by itself is not illegal.
Furthermore, why do we have a huge "installation section" on every article? It is always the same. Why not create a very detailed guide and always refer to it and tell the names of the packages to install?
Altogether the article is quite nice and to the point. One could collect some links to the official transmission documentation for further reading.
-Michael
On Tue, 2012-01-17 at 13:39 +0100, Florian Ortmann wrote:
Hi Erik, currently I've a little problem. My Fire doesn't at the moment and I've no time to fix it. So it would be nice if someone other could make a picture.
Flo _______________________________________________ Documentation mailing list Documentation@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/documentation
Documentation mailing list Documentation@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/documentation
Documentation mailing list Documentation@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/documentation
new pictures in the english wiki
Am 17.01.2012 19:30, schrieb Michael Tremer:
On Tue, 2012-01-17 at 17:53 +0100, WhyTea wrote:
Hi Michael,
if you think we don't need the disclaimer delete it. ;)
Just wanted to know if there are some other reasons that I might have missed.
In my opinion it is easier to use/read if in every wiki the installation part is included. I don't like inkomplete wikis so I've to read several wikis if I want to install one thing.
Well, if a user has done this one time, he would know how to install a package. So most users skip that part and go on with the rest. I think wiki articles should be to the point. We must require some kind of knowledge of the reader and if he misses anything, there is still a search function or the forums.
I will reduce the screenshots in size and colordeph so the loadtime will get better.
Reduce the size with the implemented function in the wiki. Do not reupload images and NEVER upload images in a bad quality. The wiki resizes the images by itself and uses compression as well.
No comment on the rest?
-Michael
Daniel
Am 17.01.2012 17:29, schrieb Michael Tremer:
Hello,
my advice for faster way of fixing mistakes: Choose a language to start with (this is preferably English) and then write the article. Create an outline, write chapters, add screenshots... Get as much feedback as you can get. Do the guide by the shown steps and check for errors. THEN translate.
It's just easier if you don't need to fix minor issues in multiple versions.
On the text itself. You guys need to fix the screenshot sizes. The page loads a while and the screenshots are that huge that you cannot tell where text is and where just crap is. Crop the stuff that does not matter (e.g. services screenshot) and use thumbnails.
I would like to see the user pointed on how to create a samba share (bit more detailed though). You mentioned WinSCP which is specific to Windows and not very comfortable to use. Not sure if that is an option for anybody.
I think we do not need the disclaimer. In our law, even ping, telnet and nmap are illegal tools and it's up to the user what he is going to do with transmission. Bittorrent by itself is not illegal.
Furthermore, why do we have a huge "installation section" on every article? It is always the same. Why not create a very detailed guide and always refer to it and tell the names of the packages to install?
Altogether the article is quite nice and to the point. One could collect some links to the official transmission documentation for further reading.
-Michael
On Tue, 2012-01-17 at 13:39 +0100, Florian Ortmann wrote:
Hi Erik, currently I've a little problem. My Fire doesn't at the moment and I've no time to fix it. So it would be nice if someone other could make a picture.
Flo _______________________________________________ Documentation mailing list Documentation@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/documentation
Documentation mailing list Documentation@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/documentation
Documentation mailing list Documentation@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/documentation
Documentation mailing list Documentation@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/documentation
documentation@lists.ipfire.org