-
Notifications
You must be signed in to change notification settings - Fork 339
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
Markdown formatted Character Export #6979
Comments
Having experienced the fact that markdown has many 'flavors' depending on which site has implemented it, I'll need something a little less vague. I frequently use RPOL which uses a very different markdown (with quick tables) than other sites or even basic editors like Obsidian (I get completely different views based on the site/app). Try this in Obsidian and it'll be different than what you'd see on RPOL Now that my concern for which markdown variant support is out there, what is the desired layout? Emulating the existing character layout is not possible if you begin using markdown tables, also what game system is this geared towards? What extra fields will be supported? Is this designed for 3.x, Pathfinder 1e, Pathfinder 2e, D&D 4e, D&D 5e, or a very generic sheet? Here's just one layout sample I have: PATHFINDER Character Sheet| Name: | xxxxx | Race: | xxx | Height: | x'x" |
|
Honestly I'm okay with just the basic syntax from here https://www.markdownguide.org/basic-syntax/ or maybe the github flavor. As for formatting, I'm looking for a statblock layout to quickly import into a hugo or jekyll managed webpage. So a something like this for PF1 and 3.5 (and possible PF2, as our group is considering moving):
|
Describe the solution you'd like
It would be nice if one of the text options of character export was either a simple or extended markdown format.
Describe alternatives you've considered
I looked at building a character export, but failed after some simple testing.
I considered taking one of the existing text exports and changing it after the fact. This is doable, but slow.
The text was updated successfully, but these errors were encountered: