Re: The Fedora wiki system sucks

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, 2020-08-01 at 13:18 -0500, Richard Shaw wrote:
> On Sat, Aug 1, 2020 at 1:10 PM Adam Williamson <adamwill@xxxxxxxxxxxxxxxxx>
> wrote:
> 
> > On Sat, 2020-08-01 at 12:00 -0500, Richard Shaw wrote:
> > > So I wanted to document a ham radio related howto, so I decided that I
> > > would make it an extension of the Amateur Radio SIG wiki, and I've got an
> > > incomplete version created:
> > > 
> > > https://fedoraproject.org/wiki/AmateurRadio/Howto/Pat
> > > 
> > > How can a wiki not have some kind of <code> tag?
> > 
> > Use {{code|}}, <pre>, or just add any number of spaces before each line
> > of the code segment (even one space works).
> > 
> 
> Yup, <pre> got me going for now.
> 
> 
> 
> > > Most other systems in Fedora support markdown, and I would be a fan of
> > > that.
> > 
> > wikitext predates markdown by several years. mediawiki first appeared
> > in 2001 and wikitext developed along with it, Markdown was invented in
> > 2004. wikitext is quirky because of its age, development history, and
> > the fact that it's actually more than just markup, it has quite
> > extensive dynamic capabilities (particularly with extensions like
> > https://www.mediawiki.org/wiki/Extension:ParserFunctions , which we
> > have in our instance).
> > 
> 
> Yeah, the whole interface does look rather "dated", perhaps it's time to
> start looking at a successor?

I don't think there really are any that are particularly more 'modern'
or less quirky than mediawiki. Project wikis in general are going out
of style these days (the infra team would quite like to get rid of
ours, but I won't let them :>) A lot of the reason the wiki is still
around is people (like me...) doing advanced stuff with templates and
ParserFunctions which probably wouldn't be easily transferable to any
other software either.

> > If what you're writing falls under the general heading of
> > 'documentation', you might want to write it for docs.fedoraproject.org
> > rather than the wiki. docs.fp.o is built by a static generator and uses
> > the ASCIIDoc markup language. See
> > 
> > https://docs.fedoraproject.org/en-US/fedora-docs/contributing/adding-new-docs/
> 
> 
> Perhaps... Is docs open? Or is there some process for getting this
> approved? I'm heavily making updates right now. I'm somewhat
> selfishly documenting it so I remember how I set everything up as I'm sure
> I won't remember a year from now :) But figured it's worth documenting for
> others as well.

I don't really interact with it much myself, I use the wiki more. So
that page is really all I know. You could contact the docs team on IRC
for more details I guess, if no-one else answers this thread.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux