-
Notifications
You must be signed in to change notification settings - Fork 7
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
Canon next 0.1.5 #1379
Canon next 0.1.5 #1379
Conversation
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.
@scespinoza this is looking great, and it makes sense to me. I see what you mean about commenting out the customSections for now. Are you intending for me to merge/release this so we can get the ProfileSearch improvements, or do you want to keep working in here until you get CustomSections working? (if so, I'd also like you to add something to the README describing the folder/config settings needed!)
@davelandry do not merge yet!! I want to get CustomSections working, and yes, the Readme.md update is on my mind, but as I haven't been able to figure out the correct setup, I haven't included it yet I hope to get it working early next week. And btw, this is already released as I needed it on monshaat 😅 I just wanted to get your comments on the CustomSections implementation |
Hey guys, Good morning! |
hi @bidwolf! I just published a version of an internal guide we wrote to start migrating projects to Nextjs (and completely abandoning canon-core). Check it out, and if you have any questions please make a new Github issue in this repository and we can discuss/help! https://github.com/Datawheel/canon/wiki/Migrating-from-canon-to-Next.js |
Update: 0.1.6 pushes back on custom sections. Working on the monorepo, but not on the monshaat project, its a breaking change so I had to roll back.