Skip to content

Embed the markdown template into the main questionnaire. #191

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

jyasskin
Copy link
Member

@jyasskin jyasskin commented Apr 14, 2025

@miketaylr reported that this change would have prevented him from missing the existence of the markdown file. I don't have a strong opinion about the ordering relative to the Acknowledgements section or whether to call it a "Markdown Template" or something else.


Preview | Diff

Comment on lines +1334 to +1337
<pre class=include-code>
path: questionnaire.markdown
highlight: markdown
</pre>
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I could include just a subset of the lines, if the file's introductory text doesn't seem useful to embed... What do folks think?

Suggested change
<pre class=include-code>
path: questionnaire.markdown
highlight: markdown
</pre>
<pre class=include-code>
path: questionnaire.markdown
highlight: markdown
show: 9-9999
</pre>

Copy link
Member

@tantek tantek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea. For whether to include introductory text or not, I would suggest not including anything that you wouldn’t want by default left in the finished use of this template. Users of the template won't know (or think) to remove the introductory text, if that is in fact the intent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants