Re: Importing to GitBook

[Chris Morton <salt -dot- morton -at- gmail -dot- com>]

Thanks, Nina.

I'm mulling over the process and admit to not wanting to learn GitBook just
for one project. I'm sure it's pretty simple, but my procrastination (and
obstinance) is getting in the way. I just don't have the "gung-ho, charge
ahead" attitude of yesterday and would rather be working on my memoir.

Chris Morton


On Thu, May 12, 2022 at 12:37 PM Nina Barzgaran <nina -dot- barzgaran -at- barzgaran -dot- at>
wrote:

> Hello Chris,
>
> at a first lance at their Quick Start and Import guides, GitBook seems
> comparatively simple.
>
> I wonder judging by other similar tool setups, if using one tool then
> importing to a second one is not a little roundabout way of doing it.
> You would expect to have to do quite some editing and fine-tuning after
> each import.
> Or are you thinking of a one-time thing - import already existing guide
> once, then work in Gitbook from there...?
>
> In principle I would import once and then go on from there, if necessary.
> Yet, looking at GitBook's import page of their guide, a number of common
> formats are allowed for import, among them Word too, for example (in case
> that was an existing format you work with, seems still not uncommon even
> among established companies) :
> https://docs.gitbook.com/features/import
>
> But I am not an expert on GitBook, just thinking out loud, as it were. ð
> A lot of guess work involved on my part, so more information on what you
> want to do might help others to help you.
>
> Good luck and may others chime in on this.
> Nina
>
>
> Am 12.05.2022 17:31, schrieb Chris Morton:
>
> My client wants me to create its user guide in GitBook. Swell. But though I
> know Markdown, I haven't found a good GitBook primer.
>
> Do you know of one?
>
> Wanting to fast-track this and not get involved in a messy learning curve,
> my inclination is to use InDesign (which I know well), export that as HTML,
> then import the HTML into GitBook.
>
> Waddayathink?
>
> Chris Morton
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Visit TechWhirl for the latest on content technology, content strategy and
> content development | https://techwhirl.com
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> You are currently subscribed to TECHWR-L as nina -dot- barzgaran -at- barzgaran -dot- at -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
> info.
>
> 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
>
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | https://techwhirl.com

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -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 info.

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