reorg as proposed in #75 #76
Conversation
…t and some minor language updates
|
Hey @brownsarahm - I like this a lot! Thanks for getting it started? Do you want me to merge the PR, or was this just a checkin? |
| @@ -0,0 +1,102 @@ | |||
| --- | |||
| title: "Formatting problems" | |||
There was a problem hiding this comment.
I just realized missed changing this title
| helpful resources for thinking about ways to purposefully document metatdata | ||
| as part of your research. | ||
|
|
||
| (Text on metadata adapted from the online course Research Data [MANTRA](http://datalib.edina.ac.uk/mantra) by EDINA and Data Library, University of Edinburgh. MANTRA is licensed under a [Creative Commons Attribution 4.0 International License](https://creativecommons.org/licenses/by/4.0/).) |
There was a problem hiding this comment.
Most other carpentries lessons don't have referencing in this form? is there a specific style we should use to be more consistent (ie on a separate page or is it because more of the content is generic?
There was a problem hiding this comment.
that is a great question. I don't believe there is... @ErinBecker - can you confirm that references like this are not standardized across DataCarpentry lessons?
There was a problem hiding this comment.
There's no guidance in the style guide, I think it would be a good thing to add to the style guide of lesson example
|
I think this could be merged, but it would be better if more of the content from @VickySteeves was added. |
|
OK - we can keep the PR open for now if @VickySteeves still can contribute! |
|
Wanted to give this a bump @brownsarahm and @VickySteeves - any thoughts on next steps? |
|
Thank you for your contribution. This lesson has migrated to use The Carpentries Workbench, but unfortunately, due to various factors, the Maintainers of this lesson were unable to address this pull request before the transition. Because of this, we had to close your pull request. Please note that this does not mean that your contribution was not valued. There are many reasons why a pull request is not merged. It's important to remember that the Maintainers are first and foremost people---people who maintain this lesson on a voluntary basis. Sometimes pull requests become stale because other responsibilities take precedence. Thank you for taking the time to open the pull request in the first place. If you wish to contribute again, you will need to delete and re-fork your repository. How to contributeIf you wish to contribute, you will need to use the following steps to delete, 📹 How to update (delete) your fork https://carpentries.github.io/workbench/faq.html#update-fork-from-styles
QuestionsIf you have any questions or would like assistance, please contact @core-team-curriculum (email: curriculum@carpentries.org) or you can respond to this message. |
I started the proposed reorganization to move the common error with the formatting principles and separate out metadata as a separate episode. It needs more added for the metadata episode, but this way we can collaborate on it.