Addison

@POMXARK - you'll still need to publish the space, but you could do so using a private/share link!

Hey @edsiper The content needs to be published in some way first - afterwards, you can direct traffic to the local version as so: https://github.com/GitbookIO/gitbook?tab=readme-ov-file#set-up For instance: > Then open...

@edsiper It's linked to the published version - meaning the editing experience doesn't change (online in the editor, or through GitSync) TLDR; it's linked to the published part, not the...

Closing this as #2419 contains the most up to date information on fixing the developer experience of this repo

This is now shipped and possible from https://github.com/GitbookIO/gitbook/pull/3372 You can change the behavior of your links in the customization panel!

Thanks for the context @edsiper - We're keeping an eye on this area as we build out more features/GitBook for teams like yours. I'm curious for a little more context...

Thanks for the context @edsiper - we've got it logged on our side. I'd love for us to revisit this area as well so we can make it a lot...

@fabianhug Not as of now - but this is a great place to leave us any feedback on specific points you’d like to see. Things like previewing your changes specifically,...

I think this is expected from the way expandable sections are rendered in the front end - we’re also working on updating the in-app styles to match the published version...

Thanks for pointing this out - basically, it sounds like the conversion of adding ` ` (non breaking space) gets converted to a new markdown line with a space (new line...