[Question] What is the core vision behind NarrativeLab and what specific problems does it solve?

[OHOHAI]

Hi @ringeringeraja33,

I came across NarrativeLab and found your approach to integrating several powerful tools such as Storyline, Univer, WebNovel Assistant, and Narrative Canvas into a single workspace very interesting.

Since many of these tools exist as standalone plugins in the Obsidian ecosystem, I would love to understand more about your vision for this project. Specifically, I have a few questions:

1. What is the main goal of NarrativeLab? Is the intention to create a unified, self-contained writing suite, or is there a specific, integrated workflow you have in mind that cannot be achieved by installing these plugins individually?

2. What core pain points or problems does NarrativeLab solve for writers and narrative planners compared to using separate, independent plugins?

3. How do you approach long-term maintenance? Since upstream plugins (like Storyline) update independently, how do you plan to handle updates, feature merges, or potential divergence in NarrativeLab's codebase?

Thank you for your hard work and dedication to this project. I look forward to hearing your thoughts!

[ringeringeraja33]

Hi! Thanks for taking an interest in the project and for your questions.

I started building NarrativeLab because I wanted to spend less time switching between tools and add features tailored to game narrative design. I need a flexible setup that keeps everything in one place while still letting me open individual files in their native applications. Supporting that workflow has required me to modify the original plugins.

I normally use these tools for drafting, long-form writing, and database management. Bringing them together helps me stay focused, coordinate separate workflows for stories, questlines, and configuration data, and keep the related data in sync.

I've been using and refining NarrativeLab every day for the past few weeks. I've found that it needs to stay simple and lightweight so I can minimize the time and effort required to make changes. For that reason, I probably won't update NarrativeLab whenever the original plugins change.

Thanks again for asking!

[OHOHAI]

Hi! Thanks for taking an interest in the project and for your questions.

I started building NarrativeLab because I wanted to spend less time switching between tools and add features tailored to game narrative design. I need a flexible setup that keeps everything in one place while still letting me open individual files in their native applications. Supporting that workflow has required me to modify the original plugins.

I normally use these tools for drafting, long-form writing, and database management. Bringing them together helps me stay focused, coordinate separate workflows for stories, questlines, and configuration data, and keep the related data in sync.

I've been using and refining NarrativeLab every day for the past few weeks. I've found that it needs to stay simple and lightweight so I can minimize the time and effort required to make changes. For that reason, I probably won't update NarrativeLab whenever the original plugins change.

Thanks again for asking!

Thanks for your answer! So, if I understand correctly, your goal is to create a plugin that can share data between multiple standalone plugins, while keeping the data consistent and intact so that each individual plugin can still work properly on its own, right?

I also think there’s a lot of potential in adapting Narrative Canvas to use the same shared database. Since you’ve already integrated StoryLine — which has a really impressive Codex system — I think it would be very interesting if NarrativeLab could eventually provide a way to convert a StoryLine project into an ncanvas project. That way, users wouldn’t have to rebuild their Library from scratch whenever they want to use ncanvas.

That’s just an idea from me, though. You should definitely keep developing NarrativeLab in whatever direction you think is best for the project. I’m really looking forward to seeing where it goes! By the way, I still haven’t seen NarrativeLab on the Community Plugins list. Have you not published it there yet?

I also completely agree with keeping the core features as the priority and making everything lightweight and simple while still retaining enough functionality. I’m really looking forward to seeing NarrativeLab eventually become a kind of hub or bridge that makes it easy for users to move between Ncanvas and StoryLine projects. And if it could eventually support AI features for StoryLine projects as well, that would be really exciting.

Also, if you don’t mind me asking, could you give me a little insight into any major updates or features you’re planning to work on next?

[ringeringeraja33]

Hi! Thank you for your helpful suggestion about converting StoryLine projects to NarrativeLab. When I publish it in the community, I plan to add an option in Converter that supports StoryLine projects. The plugin is still a work in progress, so this will probably take a couple of weeks. NarrativeLab will likely be updated at a measured pace, as the details are still being worked out. Still, I hope it can help other users and improve their workflows.
For future updates, I’m exploring features that could support tabletop role-playing game writing. I’m still reading rulebooks and learning more about what TTRPG writers need before settling on a plan.
Thank you again for sharing your ideas!