TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
SharePoint has a crude wiki unsuitable for serious documentation.
In my experience, the only place where Confluence may not surpass it
is in maintaining a library of MS Office-format documents.
On Wed, Aug 12, 2015 at 6:10 AM, Sean Brierley
<sean -dot- brierley -at- gerberscientific -dot- com> wrote:
> I am not suggesting Sharepoint is a better wiki environment, just that
> Sharepoint has one. Rather, I am saying that for internal communication,
> Sharepoint is a stronger resource, repository, and way of sharing documents
> in total.
>
> So, my question then goes to is this external or internal communication,
> and then related questions about the utility of wikis overall....
>
> The timing on this convo is odd, because, out of the blue, I got asked
> about wikis yesterday by a tech writer at a different company.
>
> Cheers,
>
> Sean
>
> On Wed, Aug 12, 2015 at 9:01 AM, John G <john -at- garisons -dot- com> wrote:
>
>> Sharepoint is, IMHO, a very poor alternative to something like Confluence.
>> It's more of a repository than an interactive medium. You upload files to
>> Sharepoint where people can - sometimes - find them. But Confluence is much
>> more user friendly both as an author and a user.
>>
>> My 2Â
>>
>> JG
>>
>> On Wed, Aug 12, 2015 at 8:54 AM, Sean Brierley <
>> sean -dot- brierley -at- gerberscientific -dot- com> wrote:
>>
>>> Are Wikis still a thing for documentation?
>>>
>>> For internal documentation, Sharepoint seems to have taken over (and it
>>> has
>>> some Wiki-ish features you can use). Plus, after the first two months, who
>>> do you get to author your wiki content?
>>>
>>> For external Wikis, have we resolved the questions of who owns the content
>>> and what if the content causes harm, who's to blame, the author or host?
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Learn more about Adobe Technical Communication Suite (2015 Release) | http://bit.ly/1FR7zNW
