Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

03-pages > 01-building-your-application > 01-routing > 09-authenticating.mdx #314

Merged
merged 3 commits into from
Jul 10, 2023

Conversation

JiehoonPark
Copy link
Contributor

@JiehoonPark JiehoonPark commented Jun 27, 2023

기여자용

문서 개선

Progress

@ChanghyeonYoon ChanghyeonYoon added the documentation 문서 작업 label Jun 28, 2023
@JiehoonPark JiehoonPark mentioned this pull request Jun 29, 2023
@haileyport haileyport linked an issue Jun 30, 2023 that may be closed by this pull request
@haileyport haileyport requested review from haileyport and removed request for ChanghyeonYoon July 4, 2023 01:53
Copy link
Contributor

@haileyport haileyport left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

수고하셨습니다! 리뷰 반영 부탁드립니다 :)


The first step to identifying which authentication pattern you need is understanding the [data-fetching strategy](/docs/pages/building-your-application/data-fetching) you want. We can then determine which authentication providers support this strategy. There are two main patterns:
어떤 인증 패턴이 필요한지 파악하기 위해 먼저 [데이터 가져오기 전략](/docs/pages/building-your-application/data-fetching) 을 이해해야 합니다. 그런 다음 이 전략을 지원하는 인증 공급자를 결정할 수 있습니다. 주요 패턴은 다음과 같습니다.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

data-fetching이 기능을 의미하는 경우 번역하지 않기로 Next.js Korea User Group(오픈톡방)에서 이야기 된 바 있습니다.
따라서 데이터 가져오기 전략data-fetching 전략으로 수정되면 좋습니다 :)


One advantage of this pattern is it allows pages to be served from a global CDN and preloaded using [`next/link`](/docs/pages/api-reference/components/link). In practice, this results in a faster TTI ([Time to Interactive](https://web.dev/interactive/)).
이 패턴의 장점 중 하나는 전역 CDN에서 페이지를 제공하고 [`next/link`](/docs/pages/api-reference/components/link) 를 사용하여 사전로드할 수 있다는 것입니다. 실제로 이렇게 하면 더 빠른 TTI ([Time to Interactive](https://web.dev/interactive/)).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

실제로 이렇게 하면 더 빠른 TTI ([Time to Interactive](https://web.dev/interactive/)). 로 문장이 끝나는 것이 어색해서, 문장을 끝내주셨으면 합니다 :)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

실제로 이렇게 하면 더 빠른 TTI를 만들 수 있다/구현할 수 있다/만들어낸다 등 편하신 워딩으로 문장 종결 부탁드립니다!

@JiehoonPark
Copy link
Contributor Author

@ChanghyeonYoon 리뷰반영 완료 하였습니다

Copy link
Contributor

@haileyport haileyport left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM🥰
수고하셨습니다! 더 번역하고 싶은 부분이 있으시다면 이슈에 댓글 남겨주세요~

@haileyport haileyport merged commit 08b5b0f into Nextjs-kr:main Jul 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

09-authenticating.mdx
3 participants