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.
Trying to use it as if it were Confluence and build a real wiki from
existing content, I think you'll end up with a tar-baby.
On Tue, Jan 27, 2015 at 9:18 PM, Jay Maechtlen <techwriter -at- laserpubs -dot- com> wrote:
> As I understand it, these will be SharePoint's "Wiki pages".
> I need to understand more about how SP works, and I need to discuss all this
> with the guy who is setting everything up.
> But it seems there's only "a guy" setting things up, so I'm afraid there's
> nothing too fancy here.
> On 1/27/2015 4:02 PM, Ryan Young wrote:
>> What sort of wiki are you using? Confluence has an "import word" feature
>> that automatically creates pages for each section of a document. There are
>> some quirks, but it works pretty well.
>> You can also import files in bulk from SP to Confluence by simply dragging
>> and dropping them onto the Confluence attachments page. But that will only
>> create attachments, not wiki pages.
>> Finally, Atlassian has a Confluence-Sharepoint connector
>> But it looks like it only works if you want to keep both SP and Confluence
>> going. Plus, it's pricey.
>> On Tue, Jan 27, 2015 at 3:18 PM, Jay Maechtlen <techwriter -at- laserpubs -dot- com
>> <mailto:techwriter -at- laserpubs -dot- com>> wrote:
>> My (new!) employer has large numbers of documents used as guides
>> and references by customer service centers and other users.
>> They have decided to move them from their current repository to a
>> SharePoint site with Wiki pages.
>> I have a number of concerns, and want to understand some of the
>> abilities and limitations of that platform, and suitable
>> approaches to make this thing work as well as possible.
>> I think we'll have a combination of "throw existing docs int
>> position as quickly as possible" and "rebuild docs as appropriate
>> to break them into suitable topic-sized chunks".
>> The good news is - it shouldn't be boring!
>> -- Jay Maechtlen
>> 626 444-5112 <tel:626%20444-5112> office
>> 626 840-8875 <tel:626%20840-8875> cell
>> www.laserpubs.com <http://www.laserpubs.com>
> Jay Maechtlen
> 626 444-5112 office
> 626 840-8875 cell
> This email has been checked for viruses by Avast antivirus software.
> Doc-To-Help: The Quickest Way to Author and Publish Online Help, Policy &
> Procedure Guides, eBooks, and more using Microsoft Word |
> You are currently subscribed to TECHWR-L as robert -at- lauriston -dot- com -dot-
> To unsubscribe send a blank email to
> techwr-l-leave -at- lists -dot- techwr-l -dot- com
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>http://www.techwhirl.com/email-discussion-groups/ for more resources and
> Looking for articles on Technical Communications? Head over to our online
> magazine at http://techwhirl.com
> Looking for the archived Techwr-l email discussions? Search our public
> email archives @ http://techwr-l.com/archives
Doc-To-Help: The Quickest Way to Author and Publish Online Help, Policy & Procedure Guides, eBooks, and more using Microsoft Word | http://bit.ly/doctohelp2015