@TJ Thanks for opening up some interesting aspects to think about concerning initial user experience and support for newcomers to AOO.
One reaction: I see a big difference between configuring builds to have one more language-dependency and configuring a URL to sniff languages though. The life-cycle and skills/karma required could be quite different. What is a good way to invite broad participation in this area? Also, I don't think the document should be put in a writable location if it is part of the install. For writable documents, that seems to be something that is more appropriate for a sample or even part of an included mini-tutorial. It might then be better to identify them as templates so they will not over-write the initial file by default if modified and saved. Finally, as a means for feedback, encouraging exploration and contribution, wouldn't a link to a web/wiki page be better for that? This is an interesting area. I wonder how to avoid scope creep and deal with the registration menu entry in a way that works for now and that can be expanded into a broader "welcome/starter" link. I know some first-run presentations tend to be sticky, with a way to stop it (and an indication on how to obtain it from the Help pull-down whenever it is to be revisited). Is this a candidate for that sort of thing? -----Original Message----- From: TJ Frazier [mailto:[email protected]] Sent: Saturday, January 28, 2012 14:34 To: [email protected] Subject: Re: [CODE]: "Registration..." menu entry in the Help menu Hi, all! Comments in-line. On 1/28/2012 14:23, Dennis E. Hamilton wrote: > If the welcome document is stored locally in the installation > locally, having it as an ODT might work. > > It does mean that translations will be required. > > Opening of a web page has the advantage of being able to adapt to > browser language settings on a server and also being able to update > the document over time. The URL could also be release- specific > (which would allow further customization). > > I think it is also important to consider the threat surface of both > approaches, especially if the document will be opened or the URL > fetched under the privileges of the install process. > > - Dennis > > PS: I suppose this is also an area that might be subject to > distribution-specific customization, including in-enterprise > distributions. > @Dennis: all good points to keep in mind, but please also keep in mind that the same work has to be done for a welcome in a doc or on a web page (customize, translate, &c.). We have lots of folks who can do that in Writer ... > -----Original Message----- From: Kay Schenk > [mailto:[email protected]] Sent: Saturday, January 28, 2012 09:37 > To: [email protected] Subject: Re: [CODE]: > "Registration..." menu entry in the Help menu > > On Thu, Jan 26, 2012 at 8:02 AM, Rob Weir<[email protected]> > wrote: [ ... ] >> The closest to registration that we might have is to encourage the >> user to sign up for the ooo-announce list. But this is just one >> of several things we want to tell the user. Maybe after install >> we automatically launch a web page, or even load an ODF document, >> with content like: >> >> >> -- Welcome message from the project -- Highlights of the release, >> link to detailed release notes -- Where to for documentation -- >> Where to go for support -- Extensions and templates informations -- >> Invitation / Instructions on joining ooo-announce mailing list -- >> Links to official social media, our blog. Google+, Twitter, >> Facebook, etc. >> >> If we do this in ODF format, as a document, then we can also use it >> as a quick demonstration of the capabilities of the editor, showing >> a really good looking, well formatted document, etc. A good first >> experience for the user. >> > > +1 > > I like this proposal a LOT! We tell them something interesting and > we don't have to maintain any additional DBs. Much less hassle in the > long run! :) So simple, and yet so good! > > +1 also. A three-bang good idea!!! Some more thoughts: * Store the doc as writable, so the user can make changes. Empowerment. * Turn on the Record Changes feature (mention this in the doc), and solicit advice from the users as to what is helpful, what is not, and what would be helpful. /tj/ > [ ... ] > > >
