一些UI层面的建议
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 4
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
### Search first
- [X] I searched and no similar issues were found
### What Happened?
1. 若block本身没有数据，是否可以隐藏block本身，就类似于目前的markdown版本：
左边老版本，右边老版本：
2. UI层面弱化 block和page的区别：
3. text类型的property的值中的block，若要拖动，会导致整个property被拖动
4. 希望可以官方支持普通页面的父页面：
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the four UI suggestions and their attached screenshots, then clarify which behavior should be addressed first and how it should work. Define acceptance criteria for empty blocks, block/page presentation, dragging text-property blocks, and parent pages before locating the relevant UI entry points. Done means the selected behavior is implemented and verified against those criteria.
Written by the indexing model from the issue text.
Assessment
- Domain
- design, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100