public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: malc <mlashley@gmail.com>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Gentoo Handbooks moving to the wiki
Date: Sun, 14 Dec 2014 19:46:27 +0000	[thread overview]
Message-ID: <CAPkQJpS9J6F_-fHKqeQmhW5wZqBhtMPD0d4yJpdLrCb1k5c1mw@mail.gmail.com> (raw)
In-Reply-To: <20141214181918.37999d7aba90041be217ccc0@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 3442 bytes --]

What about simple transclusion? [1] Example of first few handbook-chapters
at [2]
It's not pretty (the top TOC works, but the inline-toc on the
right-hand-side doesn't work) That could be prevented with some <noinclude>
directives on the source pages but I didn't want to trample over Sven.
Would that work? (And yes - a few other includes are broken because this is
rooted in my user-space and not under the handbook, but I think these
should work if a page of this type was included in the Handbook namespace.)

Cheers,
malc.

[1] http://www.mediawiki.org/wiki/Transclusion
[2] https://wiki.gentoo.org/wiki/User:Mlashley

On Sun, Dec 14, 2014 at 3:19 PM, Andrew Savchenko <bircoph@gentoo.org>
wrote:

> On Sun, 14 Dec 2014 10:02:36 -0500 Jeff Horelick wrote:
> > > > In such cases I would recommend a Live USB (or CD/DVD) that has a
> > > > graphical environment, so that the user can keep a modern web browser
> > > > next to a terminal window, to ease installation. In that case the
> wiki
> > > > is perfectly usable.
> > >
> > > No, this is not a solution, because on particular hardware live
> > > media (live usb/cd/dvd/whatever) may fail with video or gui support.
> > >
> > > I had such problem this year, when I had to install Gentoo from
> > > LiveCD without ability to use any other host for support (reading
> > > howtos, googling and so on). I used SystemRescueCD because of ample
> > > set of debug, admin and analysis tools I needed to configure
> > > system properly, but GUI was just a failure due to lack of nvidia
> > > drivers out of the box. Of course, I can easily fix such issues
> > > when fresh system is installed, but while it was being installed I
> > > had to use what is available from the live media. And elinks was a
> > > great help back there.
> > >
> > > So it will be really nice to keep handbook copies outside of wiki
> > > interface. Probably a reasonable compromise will be to keep
> > > handbooks at the wiki, but to use some script to generate simpler
> > > htmls for out of the wiki usage scope.
> > >
> > > Best regards,
> > > Andrew Savchenko
> > >
> >
> >
> > I feel like we do not need to optimize for this case really. I feel that
> > the odds of installing Gentoo where you have no GUI (via either the
> LiveDVD
> > or SystemRescueCD), no smartphone to use to look at the wiki, no tablet
> to
> > use to look at the wiki (I'm not sure about elsewhere, but here in the
> US,
> > you can get a brand-new Android tablet for $40 USD at a physical store
> > (less online) and in the UK you can find them under 50GBP), no spare
> > computers to use to look at the wiki are extremely unlikely.
>
> This case was really simple: use of any electronic devices aside
> from PC in question was prohibited due to company's security
> policies. In fact this is quite common case when we're talking
> about business setups and not private workstations.
>
> Also I'd like to note that smartphone is not solution for people
> without perfect eyesight (e.g. me): reading too much text from small
> screen is either painful (with small fonts) or inconvenient (with
> large ones).
>
> Please note I'm not saying "do not put handbooks in wiki" — this
> is really a good idea to have all docs in one place; I'm talking
> about some backup solution for such cases, like simple generated
> htmls.
>
> Best regards,
> Andrew Savchenko
>

[-- Attachment #2: Type: text/html, Size: 4319 bytes --]

  reply	other threads:[~2014-12-14 19:46 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-12 15:30 [gentoo-project] Gentoo Handbooks moving to the wiki Sven Vermeulen
2014-12-12 15:44 ` Manuel Rüger
2014-12-12 17:00   ` Sven Vermeulen
2014-12-13 13:05 ` Alexander Berntsen
2014-12-13 14:55   ` Ulrich Mueller
2014-12-13 15:40     ` Sven Vermeulen
2014-12-13 15:41       ` Alexander Berntsen
2014-12-13 15:53       ` Rich Freeman
2014-12-13 16:02         ` Alexander Berntsen
2014-12-13 16:27           ` Ciaran McCreesh
2014-12-13 16:34             ` Alexander Berntsen
2014-12-13 17:03               ` Rich Freeman
2014-12-13 18:35             ` Andreas K. Huettel
2014-12-14 13:11               ` Markos Chandras
2014-12-13 19:47       ` Sven Vermeulen
2014-12-14 13:57   ` Ben de Groot
2014-12-14 13:59     ` Alexander Berntsen
2014-12-14 14:04       ` Ben de Groot
2014-12-14 14:22         ` Andrew Savchenko
2014-12-14 14:45           ` Matthias Maier
2014-12-14 15:18             ` Rich Freeman
2014-12-14 15:02           ` Jeff Horelick
2014-12-14 15:19             ` Andrew Savchenko
2014-12-14 19:46               ` malc [this message]
2014-12-14 20:31                 ` Andrew Savchenko
2014-12-15  8:11                   ` Sven Vermeulen
2014-12-15 11:25             ` Ben de Groot
2014-12-20 21:40 ` Tom Wijsman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAPkQJpS9J6F_-fHKqeQmhW5wZqBhtMPD0d4yJpdLrCb1k5c1mw@mail.gmail.com \
    --to=mlashley@gmail.com \
    --cc=gentoo-project@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox