The recent influx of new doc team contributors and Kenneth's wiki work caused something to click in my brain. I started thinking about the specific role of quality tech documentation in attracting and retaining contributors.

I would like to establish an image of the documentation team as one of the highest providers of value to the project. We can express this idea with a simple formula: in FOSS projects contributors equal money. A documentation team that provides excellent copywriting and tech docs is equal to an investor. Contributors keep flowing in as long as the doc team is strong in this area.

Now for something concrete, based on feedback received recently. I would like you to take a look at the main LibO website https://www.libreoffice.org/ In the menu bar, do you agree that "Events" should be exchanged with "Get involved" that is currently hiding as a submenu item under "Community"? Could the intention be conveyed better by changing "Get involved" to something else? "How can I help?" was proposed, but I think we need to be careful not to mislead people seeking help files (and consider translatability).

In the "Get involved" page itself http://www.libreoffice.org/community/get-involved/ should we have a short piece that sells the idea of contributing? Ie. make everything as explicit as possible instead of "here are our teams, you know the rest, right?". There could be a general bit to draw the visitor in and then the individual team entries could be finessed until they are at the absolute peak of comprehensibility.

I am able to edit the page contents and if something in the layout needs changing I can handle it with the admin.

--
To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/documentation/
All messages sent to this list will be publicly archived and cannot be deleted

Reply via email to