On Thu, Jun 07, 2007 at 06:50:54PM -0700, Matthew Fulmer wrote:
> Regarding specific parts of the page, Those Google search boxes
> look really weird to me, and I would never think to come use
> them. Would there be a way to put those as drop-down choices on
> some search box at the top of www.squeak.org? that is how
> several other sites do it. Or just put a search box up there
> that searches the website, the Swiki, SqueakPeople, the mailing
> lists, and (maybe) the IRC logs.
A few more changes:
- I removed those search boxes from the documentation page.
- I also re-organized the top few sections, merging the video,
book, and tutorial list into a "Useful Resources" heading.
- Added the "Discovering Better Code Series" as a top-document,
as it was particularly useful today, as someone was looking
for a document on exactly that topic
- Moved the link to http://squeak.joyful.com/Sites to the
"Community" page
- Replaced links to irc and the mailing list with a single link
to the Community page
Still to be done:
- figure out what to do with the links at the bottom of the
page. Especially the link to squeaknews.com. I am examining
that site to see what is there; unfortunately, my system is
not able to mount their zipped ISO images right now, due to
some error with my /dev/loop device.
- Move the section "Exploring the code" onto a dedicated wiki
page. I am sure an appropriate page exists, but I need to go
to bed.
My goal for this page is to be able to point to it as "the"
place to direct anyone unfamiliar with squeak able to operate
the system. More specifically, I am about to start a Seaside
tutorial, and I want to be able to assume that the reader is
already familiar with Squeak. I would like to justify that
assumption with only one link:
http://www.squeak.org/Documentation
How well does the page meet that criteria? Is it a valid
criteria? If so, should the page be renamed "Getting Started" ?
> The doc team should probably move most of those links off the
> website and put them into a bigger, easier list on the Swiki,
> kind of like I did with the tutorial list.
Still todo.
--
Matthew Fulmer -- http://mtfulmer.wordpress.com/
Help improve Squeak Documentation: http://wiki.squeak.org/squeak/808
On Sun June 24 2007, Brad Fuller wrote:
> On Sun June 24 2007 12:38 am, Matthew Fulmer wrote:
>
> >
> > Still to be done:
> > - figure out what to do with the links at the bottom of the
> > page. Especially the link to squeaknews.com.
>
> the squeaknews link can be removed. We already have a feed and links
> on the right side of every page.
Heh. Matthew said 'squeaknews.com', not 'news.squeak.org'. ;)
Ken
Cross-posted to both the web team list and the doc-team list.
Sorry.
In the postscript to my last message to the web team, an old
uncertainty I have had for a while crept up. What is (or should
be) the separate duties of the web and doc teams?
By my understanding, the Web team is solely responsible for the
maintenance of the www.squeak.org site. I started the Doc team,
because I saw a lack of good tutorials, but mostly what I have
been doing is Swiki cleanup, which seems more like website
maintenance work. The other members of the doc team have been
writing tutorials and screencasts, but not me.
This is not really a problem until one wants to collaborate with
others on a particular cleanup task. Simon Michael has said he
would be interested in such a task. Perhaps Swiki cleanup could
be a joint effort between the doc team and web teams, and we
could host a "Page of the week/month" type focus. That seems
quite on target with the web-team list, where folks gather to
discuss page edits. Might that be a good idea? If so, where
should it be hosted? on the web team list? the doc team list? or
on the Swiki? I don't want to have to cross-post again.
If there is interest, I know just where to start... ;-)
--
Matthew Fulmer -- http://mtfulmer.wordpress.com/
Help improve Squeak Documentation: http://wiki.squeak.org/squeak/808
I never sent a monthly report for the month of April, so this is
a two-month report.
In the March report, I promised, with the help of Paul Bennet,
that we would have a plan to get Seaside Documentation to a
better state by the end of the Month. Paul Bennet, however,
disappeared just as fast as he had appeared, so this never
happened. Also, I was very busy in April finishing my school
projects, so *nothing* happened April.
Around the beginning of May, I began discussing on #squeak what
kind of tools would make it easier for people to contribute to
Squeak Documentation. The consensus seems that successful
documentation for squeak would need to be as distributed,
navigable, and searchable as code for squeak. Seems reasonable.
Around mid-may, I was discussing this again, and Simon Michael
and Ken Causey said they would lend some unofficial help.
Within the last week, I started a small project to help me learn
Seaside and perhaps boost the amount of testing and discussion
that happens around Squeak code: adding email notification to
SqueakSource commits. It should be fun.
Also this month, I re-arranged the tutorial list I have been
building to be more navigable: http://wiki.squeak.org/squeak/792
I haven't really heard from Andrew Lawson about his Collections
tutorial, or from Aaron Riechow about his screencasts for three
months.
Suggestions are always welcome. Keep on Squeaking.
--
Matthew Fulmer -- http://mtfulmer.wordpress.com/
Help improve Squeak Documentation: http://wiki.squeak.org/squeak/808