markhub
← Back to Learn

Basics · 07

Create a Note

Write meeting recaps, plans, docs right inside the hub.

Scroll to take the tour

8+ lines in chat → auto-promoted to a note

You just sent a long message. Markhub splits it into a note for you so the chat doesn't break into a wall of text.

'A new Note has been created'

Where the message would have gone, a note link card appears. Tap it to open the auto-generated note.

Auto note, body preserved verbatim

The 8 lines you just typed become the note body. Leave the title empty and ✨ generates it from the body.

Header ⋯ menu → Note

Open the more-menu in the hub header to enter the Notes area.

Notes list, meeting minutes, call minutes and free notes in one place

Type, created/updated time and author all line up at a glance.

Add note → start a blank note

Leave the title empty and ✨ generates it from the body for you.

Free writing, body + checklist

Notes live next to tickets. A long chat (over 8 lines) also gets auto-saved as a note.

Code blocks · tables · images, full markdown

Specs, tech notes, comparison tables, all in one note. Same structure as auto meeting/call notes, so search and linking stay consistent.

#Dev-Only
Quick alignment on applying the to-do ticket design across the chat area.
For UX consistency, I'd like to reuse the existing data-bucket ticket design
in the chat area as well.
Specifically: card width, status pill, due-date placement, same rules across both.
See the attached reference image for the exact layout.
Drop any objections in the thread.
Hoping we can decide today and start the work tomorrow morning. Thanks!
To-Dos
AllBoardListCalendar
Not Started
Add to-do…
#Dev-Only
Yoon Shin 99902:32 PM
A new Note has been created
To-do ticket design, apply across chat area
Message #Dev-Only, @ to mention · link todos & notes
To-Dos
AllBoardListCalendar
Not Started
Add to-do…
Title
Leave empty to auto-generate with ✨
AuthorYoon Shin 999
Approver+ Approve
2 more properties
Quick alignment on applying the to-do ticket design across the chat area.
For UX consistency, I'd like to reuse the existing data-bucket ticket design
in the chat area as well.
Specifically: card width, status pill, due-date placement, same rules across both.
See the attached reference image for the exact layout.
Drop any objections in the thread.
Hoping we can decide today and start the work tomorrow morning. Thanks!
To-Dos
AllBoardListCalendar
Not Started
Add to-do…
#Dev-Only
Yesterday
Yoon Shin 99911:17 PM
Everything written in the Notes area is searchable and linkable to tickets in one go.
Note
File
Board
Activity
Settings
Message #Dev-Only, @ to mention · link todos & notes
To-Dos
AllBoardListCalendar
Not Started
Add to-do…
NotesMyBoardList
Add note…
NoteTypeCreatedUpdatedAuthor
YC interview Q&A draft by Jein
Jein Song 777
Note
2026-05-07
2026-05-08
Jein
Yeong-gwang full-time decision, paused
Yoon Shin 999
Call
2026-05-06
2026-05-08
Yoon
WhatsApp integration feasibility & strategy
Yoon Shin 999
Note
2026-04-29
2026-05-07
Yoon
MARKHUB call minutes
Yoon Shin 999
Call
2026-05-06
2026-05-07
Yoon
Plan, 'clone from me' + resource access scope
Jein Song 777
Note
2026-05-06
2026-05-06
Jein
Clone delegation, image attach + intermediate context
Jein Song 777
Note
2026-05-03
2026-05-03
Jein
Clone workflow feature plan
Jein Song 777
Note
2026-05-01
2026-05-01
Jein
To-Dos
AllBoardListCalendar
Not Started
Add to-do…
Title
Leave empty to auto-generate with ✨
AuthorYoon Shin 999
Approver+ Approve
2 more properties
Write something…
To-Dos
AllBoardListCalendar
Not Started
Add to-do…
How to write a note
AuthorYoon Shin 999
Approver+ Approve
2 more properties
Notes exist for the kind of note-taking and memos that tickets aren't built for.
And when a regular chat goes over 8 lines
it gets recorded as a note automatically.
Like this
you can also
write to-dos
right inside.
To-Dos
AllBoardListCalendar
Not Started
Add to-do…
How to write a note
AuthorYoon Shin 999
Approver+ Approve
2 more properties
right inside.
1const handleLogout = () => setLogoutModalVisible(true);
2
3
4const handleConfirmLogout = async () => {
5 try {
6 setIsLoggingOut(true);
7 setLogoutModalVisible(false);
8 await stateTransitionLogic.handleLogout(true);
9 await signOut();
10 navigationGuard.navigateToLoginAfterLogout(router);
11 } catch (error) {
12 setIsLoggingOut(false);
13 console.error('[More Screen] 로그아웃 실패:', error);
14 }
15};
Option
Tone
Fit
To-Do
Direct, 1:1 with To-Do
◎ best
Task
IT startup
Item
Generic, neutral
Action
Meeting → decision
◎ (alt)
To-Dos
AllBoardListCalendar
Not Started
Add to-do…
← Back to Learn