-
Notifications
You must be signed in to change notification settings - Fork 7
Import pages through navigation (part 1) #103
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
Conversation
8eaf911 to
e9ccfc1
Compare
673f77f to
482b23d
Compare
|
@akirk @ashfame I'm making progress here on what comes after what is shown in the screen recording (importing each of the pages the user selected). I should have a finished version tomorrow. My goal is to build a first iteration of the flow here, we can then adapt it however is needed for the demo in other PRs. |
5a50f12 to
6681827
Compare
fd7096d to
3c3610c
Compare
3c3610c to
5089e7b
Compare
| setUrl( selectedPages[ pageIndex ] ); | ||
| }, [ session.id, pageIndex, navigate, selectedPages ] ); | ||
|
|
||
| return <>{ url }</>; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The next PR will implement this component.
ashfame
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good 👍
This PR implements one flow for import pages by selecting the navigation. Later, we can adapt it how we see fit, or we can implement other flows for importing pages that do it differently. This is just a starting point, any feedback you might have can be implemented.
A note on blueprints
This PR implements importing pages without relying on Blueprints. Blueprints are meant for things that would be crawled, where the user defines the structure of one thing (e.g. blog post), and we than use that to automatically import all other ones.
However, things that don't need to be crawled do not need to rely on a blueprint. Instead, the user can manually import all instances.
This PR implements page import in this manual way, where there is no automatic crawling, so no blueprints are involved. In the future we may decide that we do want to crawl pages, and if so, a new flow can be implemented that relies on blueprints.
This is only part 1
This PR was getting too large, so I figured I would ship it as is, and there will be a second one that completes the flow. This PR stops after the user selected the pages (see screen recording), the next PR will have the user iteratively import all selected pages, one by one.
Summary of changes
LinkFieldand a navigation parser. Takes a<ul>...<ul/>and returns an array ofLinkField<ul>./ui/import/pagesScreen recording
Screen.Recording.2024-11-12.at.15.58.41.mov