I was really excited when I read your post. I've long looked for a good MarkDown -> PDF or RTF workflow, so I gave KeenWrite a quick try. At first glance I really thought I'd be exactly the user for this tool, but quickly realized that the discoverability of KeenWrite isn't nearly good enough.
Upon launch, I'm presented with three panes. I've got a MarkDown authoring interface and an output preview. Great. I drop in some markdown and it renders.
Then I have a "variables.yaml" pane open with three little controls, "Create", "Rename", and "Delete". Ok... I'm editing a YAML file. But it's a clunky nested node editor. People can edit a MarkDown file but you don't think it's faster to simply let people edit YAML in text?
So, I get it, I'm editing a YAML file that stores metadata about... SOMETHING about my document output. Except I don't have a single example of a variable. Not a single one. I have no idea what variables are available and exploring every single menu option tells me nothing. Help only provides a small about page with no link to the documentation.
So, I go to keenwrite.com and click documentation. It takes me to a single GitLab readme that talks about different command line launch options, and then finally how to begin to use metadata, but the options all revolve around creating an .Rmd file and using R or creating a "definitions.yaml" instead of a "variables.yaml" in a seperate editor.
This is the moment I realize there's no chance this tool is going to be useful for me.
Were the video tutorials[0], in particular the variables tutorial[1] not helpful?
> Except I don't have a single example of a variable.
Did you watch the metadata tutorial[2]?
> People can edit a MarkDown file but you don't think it's faster to simply let people edit YAML in text?
Close the variable editor panel if you like and edit the variables in a different text editor. (Or create a symbolic link between the .yaml and .yaml.txt file and edit the .yaml.txt file in a KeenWrite tab.) The downside is that KeenWrite won't know how to inject variables into the document when pressing the Control-Space hotkey.
The variables, architecturally speaking, need not be written in YAML. They could be TOML, XML, JSON, etc. The software reads a nested hierarchy of variables and values into a tree data structure, which abstracts away the data's file format. Presently only YAML format is integrated. The hierarchy is then presented through a clunky JavaFX Tree UI element.
> discoverability of KeenWrite isn't nearly good enough
I received that same feedback years ago and made video tutorials, which are linked to at the bottom of the home page[3]. Do they need to be more prominent?
The home page also links to a documentation page[4] that describes variables, metadata, R integration, and more.
The home page[1] links to documentation[2] that describes variables, metadata, R integration, and more. If that's not sufficient, I'm open to improving the documentation.
Probably not. PillPack is MDP: multi-dose packaging, which is little packets containing multiple medications. All they're advertising here is regular bottled medications, which is a much easier-to-solve mail-order prescription problem.
At the same time, Reddit exists, and this is a community of people created by a VC company explicitly to have wonky tech discussions with other professionals called "Hacker News". It's fine every once in a while but I don't want this to be filled with generic human interest stories.
What does "society values" mean, though? These women in their 70ies supposedly don't care about being attractive. So the only thing that matters is could they get decent jobs if they were unattractive. They supposedly don't care about societies evaluation of their attractiveness anyway.
And we were talking about "pressure to be attractive". What form does that take. What happens to you if you are unattractive?
It's actually really common for women who have experienced sexual assault to take steps (gaining weight, wearing loose baggy clothing) to avoid the male gaze.
