Hi, Rudi asked me to do a demo of how Fedora could make a rebuilt docs website look, so I've made a demo site & tweaked it a bit. Before I spend too much effort on it I thought I'd open it up for input.
I wanted to get a bit more done before the weekend, but time slipped away. I wanted to get it out for some feedback over the weekend so I can do some more on Monday, so I'd thought I'd just put it out there and hope people can understand it is only half baked.
Some of the stuff I did for this I liked so I've started migrating the template changes back in to publican, leaving this site with just some colour changes on what a default web_style 2 site will look like. I'll update my fedora people site next week so show what a default site will look like.
I've made a script to pull out most of the docs packages from git, and run through a bunch of branches per book, and try to build them with the latest publican. I'll make the script available next week for people who want to build their own copy. It should be useful to QA the process as it spits out a log file out for each repo and branch so you can get a good list of what's broken and what's not. I'll also put those up on my fedora people site next week ... If I have any quota left :D
Demo site is https://jfearn.fedorapeople.org/fdocs/en-US/index.html
I think this is a pretty good layout https://jfearn.fedorapeople.org/fdocs/en-US/index.html#Fedora
Colours are hard :-/
Note if you click a group, below the versions, then it filters out all the other groups.
Note that in the "System administration" group for Fedora 20 there is an external link "The Ways And Means Of Pants" which is a fake URL, if you have a couple of examples of real external links you'd like in that group, or any other group, I'd be happy to swap out the fake one.
I haven't changed the brand XSL for the html payload, I'd like to remove the old left and right logos at the top of the pages. They aren't really needed given the menu content.
bah I just noticed a bug on that page, the first two items in the navigation menu are swapped ... :(
I'm sure there are lots more :}
I've built html, html-single, epub & pdf.
The site is only in en-US, it's 417M and I'm not sure the hosting people would be happy if I hosted more languages :)
Anyway, it's Friday evening and the wine is calling, please reply if you have any ideas or feedback, beware that I'm currently hacking on the publican devel branch, so I might steal any really cool ideas for publican.next ;)
P.S. All the RSS feeds on there should work, but you probably do not want to sign up for that site!
You are kindly invited to the meeting:
Docs Office Hours ( Americas ) on 2015-05-07 from 12:00:00 to 13:00:00 US/Mountain
The meeting will be about:
Office hours for Fedora Docs contributors. Stop in to #fedora-docs for help with writing documentation or just to schmooze with the Docs community. Bring your own cake.
I like to contribute to Docs team
I have been editing wiki pages for local events, latam budget, latam
procedures, freemedia project.
I have using fedora since fedora core 4, I am not programmer or
sysadmin, but I have get experience in installation, creating local
repos, settin up web servers for wikimedia and wordpress. I have been
documenting part of my experience on my blog http://taygon.com
I have been part time teacher at university level on and off since 1998.
I can dig into a subject, look for the key points and make an
explanation for others.
I have been for a time freemedia coordinator, FAmSCo member and Fedora
Board member. I have helping out latam activities as Community credit
card holder, to provide resources to collaborators in this region.
I have decent writing skills in English, but excellent style in Spanish
as a native speaker.
I would like to get hand on learning how to make official documentation
helping along the way. My ultimate goal is to make the documentation for
Icaro Project, an educational robotics software/hardware made entirely
with fedora in LATAM
I hope to get a chance to help docs team.
pub 1024D/96851663 2009-06-20 [expires: 2016-10-25]
uid Neville A. Cross (yn1v - fedora - Nicaragua) <neville(a)taygon.com>
uid Neville A. Cross (Fedora Ambassador - Nicaragua)
uid Neville A. Cross (YN1V - Fedora - Nicaragua) <nacross(a)gmail.com>
uid Neville A. Cross (Fedora Ambassador - Nicaragua) <yn1v(a)taygon.com>
sub 2048g/1E3CFE30 2009-06-20
There was recently a discussion on the Fedora Rel-Eng list as the
result of a Project Planning workflow. As this was discussed
further in irc it was decided that this is likely a conversation that
should be had across more Fedora groups to see if there's a solution
that we would all like to utilize. If we can all agree on a workflow
and utility we'll hopefully remove the potential for duplicating
efforts or requesting multiple solutions to the same problem be hosted
by the Infrastructure team. In an attempt to not cross-post I am
duplicating this post on the rel-eng, qa, infrastructure, docs,
buildsys, and env-and-stacks mailing lists. I would like to request
that if there are any discussions around this, please rely to the
rel-eng list so we can consolidate the discussion.
All interested parties please fill out the following WhenIsGood so
that we can find a meeting time to discuss this.
 - https://lists.fedoraproject.org/pipermail/rel-eng/2015-April/019806.html
I'm thinking about how stale we want to let a book get before we stop
publishing it. Right now, the de-facto policy is to stop maintaining a
guide for a release when the release goes EOL, but on migrating to a new
publishing system, we'll have to decide if we want to republish
It seems like publishing the currently maintained versions, plus the
release under development, plus the most recently EOL'd release, should
be enough. Early adopters are covered, stragglers are covered for
their upgrade, stubborn EOL users get the appropriate amount of support,
and nobody gets really stale, potentially incorrect or harmful
instructions. I'm throwing this on the agenda to discuss at the next
meeting, if you can't make it, please reply here.
Also, is there some number of participants we consider a quorum for
voting during meetings? We don't do a lot of voting, but it seems like
a good thing to establish.