start
First choose what you want to do this time, and then bring in the information you really need at the moment.
Product capabilities are not just a bunch of extra functions
It is to really catch the project
For Lime, starting, bringing data, continuing to modify, and saving results are different stages of the same thing. The focus of product capabilities is to sequence these steps, not to make the page lively.
Put something that will continue to advance
from beginning to end
Start with tasks first, not modes and entrances
After opening it, decide what to do this time and then bring the information in. In this way, users are faced with tasks, not a bunch of interface structures that need to be understood first.
Choose tasks firstBring more informationless cut mode
Reference materials are brought in directly, and the draft continues to be revised along with the project.
Articles, screenshots, highlights and old drafts can all be dropped into the current project. Drafting, continuing writing, rewriting, and organizing the results continue along the same path without having to restart each step.
Bring in referenceContinue writing old manuscriptsMultiple rounds of rewriting
The results are saved back to the project, and you can directly connect them next time you open them.
The master draft, version, notes, and next steps will all remain in the project. What really saves time is not getting one version of the answers at once, but not having to explain the background from scratch next time you come back.
Keep the main articleVersion reviewContinue next
four core movements
Basically the product skeleton
There can be many pages, but these are the only types of really high-frequency actions. Only when these categories are arranged in order will users feel that the product is a whole.
Bring information
Web pages, screenshots, highlights, and old drafts are returned directly to the project without having to be moved manually.
continue writing
Drafting, continuation, rewriting and editing all continue in one path.
Leave results
The main draft, notes and next steps will be retained, and the project will not be broken into one answer.
What scene is more suitable for
These situations will be easier
It’s certainly quick to get one version of the results in one Q&A, but the real trouble in long-term projects is the subsequent series of actions. Lime’s value lies in the latter string.
Content items need to be revised repeatedly
It is suitable for those who need to continue to add information, change the structure, and change the tone after writing the first version.
A main article needs to be split into multiple channel versions
It is suitable for scenarios where Xiaohongshu, public account, summary and comment area hooks need to be processed together.
You want both the results and the process to be retained
Suitable for long-term projects, rather than just pursuing one version of results at a time.
Want to continue reading
You can follow these pages
If you want to continue looking at creative skills, ability networks or developer connections, the following entrances have been opened.