Connected Docs - next level of docs module
Drag Ivko
I'd like to see more love for documents. Things like:
- ability to embed any CU entity into docs
- ability to build books/playbooks / etc from a table of contents that would pull information from documents based in multiple workspaces, folders, and lists
- outlining
- ability to convert OPML, plain text and mindmap files into outlines
- topics (with topic definition area) + colored topics
- categories (with category definition area) + colored categories
- tags (with tag definition area) + colored tags
- keywords & register of keywords
- dynamically cross-linked documents
- ability to create a visual network of documents via graph database based on tags or topics or categories
- floating windows for previewing any number of topics and or docs - i.e. while I am writing a document I'd like to see the outline of the playbook I am writing in a floating window so that I have the visual orientation of where the current document fits in a larger picture
- have linked entities (docs, tasks, goals) opened in a side window
- named blocks of text
- ability to lock all documents that reference a certain topic, category or tag(s)
- compare 2 revisions of a document side by side
- analysis based on topics, categories, tags
- tree views based on topics, categories, tags
Log In
S
Shreyansh Jain
This seems to be a great idea
For me:
- somewhat like docs in multiple docs + synced blocks (quote: dynamically cross-linked documents) will work
- (quote: ability to create a visual network of documents via graph database based on tags or topics or categories) Just like obsidian, I'll like it to be a part of clickup as a clickapp
- Floating windows are a must
J
Jonathan Cohen
ClickUp needs to replicate what Mem have done for notes
W
Wahid T. Yahya
Focus Mode
It would be of great help if you could consider adding a "Focus Mode" to Docs 3.0. This mode would allow all peripheral elements to fade away, leaving only the text a user is working on. The goal is to create an uninterrupted, immersive writing environment that helps the user to concentrate and enhance their productivity.
By having this feature, we can eliminate potential distractions and help users focus solely on their content, which is particularly beneficial for those needing to write extensive documents or those who get easily distracted.
Doc linking
Currently, I utilize the "mention of pages" to link ideas. However, the presence of the doc icon before each link interrupts the flow. A cleaner alternative would be the display of mentioned pages as simple text links, eliminating the document icon.
Tim Jasper
I'd like to be able to drag blocks (eg checklist items, tables etc) from one page to another in a doc https://clickup.canny.io/feature-requests/p/move-or-drag-blocksitems-between-doc-pages
Artur .T
Please redesign Doc Center using a Notion like architecture with nested pages and bidirectional links. Also being able to create docs databases just like lists with fields and throwing data in them using automatons would be awesome. Creating a new page in docs should not be the same as creating a notebook which is what CU does currently.
Dean Phillips
Artur .T: Definitely a direction I'd like to see too :)
D
Daniel Wojcik
Dean Phillips: we really need this, can't stress how unusable docs is without this feature
Lukas Moser
Artur .T: yess!!!11!!1
Amy Wagner
100% on the table of contents especially
Dean Phillips
These are all such good ideas Drag Ivko - as always super thought out by you.
B
Brian Shen
Hey, there!
We are planning improvements to docs and would love your feedback on this feature. We take your feedback to heart! Take the 60 second survey here:
Thanks!
Kevin Chard
hey Nick What about an event for docs in webhooks, so I can use an endpoint to automate publishing of content to another resource?
Nick
Kevin Chard: Great idea! I'll bring it back to the rest of the team to discuss - what events in particular would you want from docs webhooks?
Kevin Chard
Nick: hhmm, good question. I would see,
Events
---------------------
- docCreated
- docLastUpdated
- docUpdated
- docDeleted
- docTaskStatus ? draft, publish,
Other
---------------------
- format : html, markdown
- taskMeta or docMeta ?
( the idea that you could include keywords/seo or other data. Ideal would be manage these via the SEO Management template via keywords custom field.)
- docID
- docAuthor
- docImages
This would let HubSpot or other proprietary platforms or even plugins for WordPress. Much better process,
Nick
Kevin Chard: Got it! Added all of these to our task for a Docs API 🙂
Dean Phillips
Nick: Oh that's awesome. So docs will be getting an API too? :D
Kevin Chard
Nick: any update on the status of this ?
Drag Ivko
Nick:
Can we have some love for this?
Nick
Drag Ivko: All good ideas! We already have plans to implement some of these later this year. Docs is something we are going to be putting more resources into improving in the near future! I'm going to bring the other ideas here that we don't have planned to the rest of the team to talk about 🙂
R
R C
Nick: Nick, one thing I've found that I think might be improved is the doc hierarchy. Drag Ivko curious is this is something you had in mind too, kind of along the lines of your point "dynamically cross-linked documents" from above:
Right now, if you create a doc, you can build in sub-docs in a "Table of Contents" format that a lot of your users may have seen in Confluence, pretty much a market standards as you know for many years.
However, you guys have the great advantage of allowing Docs to belong to anywhere in the Space/Folder/List hierarchy. So for me, the natural place to house docs around my Software Platform (I know this is what Drag is also thinking of - Software development) is in particular Folders and Lists that I am using for parts of that Platform. Thinks like server infrastructure, micro services we build, individual integration with third party stuff like sentry.io, etc.
A lot of this is related on a hierarchical level so I build the actual system work that way in a Space/Folder/List/Task/Subtask set up. But if I want to have a Doc that has a hierarchy, the natural way to do that in Docs as they are currently set up is to make a "master" doc, then add section to it. But, doing that, you can't relate those sub docs to the sub-"units" in ClickUp.
For example, I want to build a Doc talking about components of a Emailing system I'm building. I'd set up the basic Doc at the Space or Folder level. Then, within the doc I build sections for each component, feature, etc. But that all stays at the Space level with this master doc lives. However, in the task structure in ClickUp, I have folders and lists for all these entities. So it would be great to be able to relate the actual doc that talks about something in one of my lists to that list.
One solution I thought of was to simply build my documentation at each entity level in ClickUp. So say in this Emailer I have a bulk sending tool that can be scheduled, and an ad hoc sender that sends on-off mail. I want a doc about each. But these are handled in lists. If I could see a "roll up" view of docs that are in sub entities in ClickUp, the way I can "roll up" to a folder view and see lists, or a Space view and see folders and lists, this would really help get Docs more aligned with actual work in ClickUp.
Hope that makes sense and is an idea you guys would also agree with!
Nick
R C: Makes perfect sense and we are working on adding a Doc Hierarchy feature as we speak!
Load More
→