New story type or option : vue standalone page

[troyere]

Clear and concise description of the problem

Hey 🤙 !

First, the objective of my idea : more flexibility & freedom in the redaction of the stories.

People using Histoire in my job are not all devs, far from it. Once deployed, the documentation must not only be technical, but it must also be displayed using the product designer rules, be understable by all, and, most important, stay simple.

In https://histoire.dev/guide/vue3/docs.html#documentation, we can see that Histoire provide a way to create standalone pages, that's great ! But sadly, essentialy in markdown, that's all.

Would that be possible to create standalone pages in Vue ? The result would be the same as markdown stories, but using Vue instead.

Thanks in advance for your help 😉

Suggested solution

Only a functional solution, I'm afraid :

First, the file format would be :

• Markdown standalone page : Introduction.story.md (no change here)
• Vue standalone page : Introduction.story.vue (here we usually starts to use the <Story> component)

And in Introduction.story.vue :

<Story> component new option :

• standalone , a boolean that totally disable :
  • the right side panel
  • the "responsive" option
  • the "background" option
  • the "text direction" option
  • the "open in new tab" option

Alternative

No response

Additional context

I created my ideas in the discussions tab, but since I didn't have any answers, I'm trying here in the issues. If needed :

• https://github.com/histoire-dev/histoire/discussions/558
• https://github.com/histoire-dev/histoire/discussions/605

Validations

• [X] Follow our Code of Conduct
• [X] Read the Contributing Guidelines.
• [X] Read the docs.
• [X] Check that there isn't already an issue that requests the same feature to avoid creating a duplicate.

[theDevelopper]

I would like this one very much. Alternatively, a way to disable various "features" for specific stories/variants. Like "hide Source", "hide Controls", "hide Docs", etc. I don't mind having multiple properties, so a "one-to-disable-all" is not necessary for me, as long as I can disable "all" somehow on the story/variant level.