I want to agree with Eric regarding the Summer Reboot. I started
using Radiant last week, before volunteering at the sprint to write
documentation for new users. At that point, I was directed to the
Summer Reboot, to start updating those pages. I hope to do a lot more
work in them over the next few weeks, documenting into them as I go;
as I become more familiar with Radiant and its tools/extensions. Let's
get those pages higher on the list, at least.
I did do some updates to docs located in the handbook - marking them
as 'old' with newer version existing in the Reboot, and marking in the
Reboot where I stole text directly from the Handbook and elsewhere.
I also incorporated the navigation style I found in the Handbook into
the Reboot - i.e. the 'footer navigation'.
If no-one has a problem with this then I will focus on it more through
this week/week-end.
~jt
On Dec 15, 2008, at 2:41 PM, Erik Ostrom wrote:
Just wanted to chip in one piece of constructive (I hope)
criticism. I'm
still getting started using Radiant. I've found the documentation
sufficient - in fact, it's generally quite good for a relatively new
open-source project of its scope.
That said, I notice a lot of people on the mailing list answering
questions
with some page that's linked to from the Summer Reboot. Or saying
we should
document some feature and add it to the Summer Reboot.
The Summer Reboot has some great stuff in it. But it's the very
last thing
listed on the documentation page, and the description makes it sound
like
it's some shaky, immature thing you probably shouldn't waste your
time on.
I didn't even realize it existed until I had the experience of going
to the
wiki, following documentation links that I thought would answer some
question I had, reading for a while, giving up, going to Google to
search
the web for an answer, and being pointed back at another section of
the same
wiki.
Also, where I live, it's cold out. I think it's time to start
integrating
Summer Reboot content into the primary documentation. Maybe keep
the Summer
Reboot structure as-is (I know there are a lot of sections that
haven't been
written yet) but start linking to it from relevant sections of the
Radiant
Handbook. And give it co-equal billing with the Handbook, instead of
putting it down at the bottom. Make it clear that it's unfinished,
but it's
still a useful resource.
- Erik Ostrom
[email protected]
P.S. How was the mini-sprint?
On Sun, Dec 14, 2008 at 9:40 AM, Mohit Sindhwani <[email protected]>
wrote:
Anton J Aylward wrote:
<rant >
Radiant has great potential, but, apart from a few people, Sean and
Chris being the most outstanding, the Geeks rule. The code may be
great
but the usability sucks. The READMEs are sparse, the installation
instructions missing and the examples for use non-existent or
confusing
(the gallery extension must be up there among the most confusing
to use).
I wouldn't mind so much if the author wrote things like 'This
software
"works for me", but it may not work for you.' That's fair enough.
But lack of this means a great waste of time.
</rant>
Hi Anton
I'm sorry for the problems you are experiencing. I'm hoping that
most
people release code when it's at least at a stage where it works
for them.
Unfortunately, you have to cut the developers some slack when it
comes to
this - it may be that when they created their extension, they had
stuff
pre-installed and somehow in their thinking, that item didn't make
it into
the prerequisites.
As far as the Radiant community goes, it's one of the better and
more civil
communities I have seen. We have worked hard to put out
instructions for
different things. Take a look at some of these for example:
* http://wiki.radiantcms.org/Copy_and_Move
* http://wiki.radiantcms.org/Using_Radiant_as_a_Blog
* http://wiki.radiantcms.org/Reorder
* http://wiki.radiantcms.org/Settings_Extension
all starting from http://wiki.radiantcms.org/Summer_Reboot
That said, it may just be that those of us who are doing the
documentation
have not yet used/ encountered the extensions that you want to use.
The community here is helpful - it's usually willing to go a much
longer
way than just saying "find your own way - or use something else,
this is
open source - get in and code" and I'm sure your own experience
will also be
similar.
That said, are you talking about:
http://github.com/artofmission/radiant-articles/tree/master as the
articles plugin? I had trouble trying to find what you may be using.
Cheers,
Mohit.
12/15/2008 | 2:40 AM.
_______________________________________________
Radiant mailing list
Post: [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
_______________________________________________
Radiant mailing list
Post: [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
_______________________________________________
Radiant mailing list
Post: [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
