![]() ![]() At least one level of nesting, preferably two, or three - all simultaneously viewable at filename or thumbnail level, in a hierarchical **sidebar**. Presents the reader with a **nested** page structure - like a website - which is easily navigated. Can be **synchronously** edited - like md docs in NextCloud Uses **the web** as its (scrolling?) display space, not hard-copy (paged?) versions Requirements for a **public** library/handbook/FAQ (or a private **operational** handbook): op abandoned its own wiki during its first year - why? Why did members think we could manage without one? Has the **website** met all the user-facing needs - no? Does the **forum-plus-NextCloud-plus- Matrix/Element** meet all the ops-members' needs - no? But the standard wiki interface (Mediawiki) may be both too complex, too uninteresting and too inflexible to serve our purpose. (Then, with something like a **push-newsletter** or a **pull-blog** tacked on?). And some kind of static, structured, one-stop front-end, rather than straggling, erratic forum threads and a limited website (limited for good reasons).Ĭonventionally this purpose might be handled in a **wiki**. > This all needs wholesale, holistic redesign. **contributions** that members can make and ways members can engage one another, how to **become a member** and types of membership, the **policies** and development commitments of op, **events** & milestones planned and achieved, channels for member-enquiries or **trouble reporting**, etc etc. > Why? Bcos it's simply not possible for anybody, right now, to get a comprehensive view of op. Corresponds to the 'Library' category in (). > Intention: To find a coherent and easily navigated way of posting a public 'library' for op (or a set of libraries, including private, ops-only libraries). ![]() Start of an investigation : May 2021 : mike hales Updated 2021 07 15 We will not go as far as saying it is the easiest and fastest alternative out there, since it does require a bit of working knowledge of Markdown and Git, but once these are mastered, you can take all that is written above about GitBook Editor for granted.# Tools for managing a public 'library', handbook or FAQ, in markdown To conclude, GitBook Editor offers an efficient and straightforward environment for writing, editing and publishing your ebooks, directly from the comfort of your computer's desktop. ![]() Competent publishing utility, but may not be everyone's cup of tea In addition, its built-in history manager enables you to review the changes made before you submit the book for publishing. The utility also provides you with some advanced proofreading features, like spell-checking and suggestions meant to improve the clarity of your texts.įor example, it can detect errors or overly-complicated phrases and words and propose better alternatives, with support for more than 30 languages. You can edit text from both the top toolbar or with the help of the contextual menu, whatever suits your working style best. Swiftly write and edit books using Markdown and Asciidoc Once logged in, you are met by a simplistic main window that makes it easy for you to create new or manage books both locally or from the platform.Īs soon as you open or create a new book, you are greeted by a more comprehensive window that provides quick access to all the app's features, as well as the contents of your books via chapter and file-tree panels. If this is the first time you have to deal with GitBook, then you are required to create an account before you proceed. In a few words, GitBook Editor is a simple and useful software solution that makes it as easy as possible for you to write and publish your books without many distractions. If you are looking for a web-based publishing platform that enables you to write both Markdown and Asciidoc, all while offering some useful features like proofreading and version control, then GitBook might be worth your while.īut if you want a more direct writing environment, like the one provided by your desktop, then GitBook Editor can offer you exactly that. ![]()
0 Comments
Leave a Reply. |