I think this is a nice and clear Markdown intro. I think we do want something about doing GitHub favoured tables: I used them recently in a PH lesson. It does taper off a bit at the end but I'm not sure how to best wrap it up... perhaps with a paragraph about other uses for Markdown in DH?

Maybe end with a paragraph on limits. (Most journals wont know what to do with it) and then a paragraph reiterating its value, before finishing with a historian-ey example? Maybe a structured short primary source?

Are we ready to add this lesson? Just noticing we never merged the pull request. @williamjturkel @acrymble

Close, not quite! I'm having a colleague read through and zest up the content a bit. Still feel it could use some tweaking.

Just pinging as I see this is still outstanding: how are things going, @ssimpkin? I think this'll be a fantastic addition for historians (especially those who want to write for Programming Historian!).

Don't blame @ssimpkin on this one, I've fallen down on looking at the dang thing and she asked me like twenty years ago. Am going to do it today.

This has been added to the Lesson Pipeline wiki.

Just checking in again like the gadfly that I am. How go things?

They go! John had a look over here and the biggest change was a switch over to another browser-based md editor. I'm happy with it as a public intro, but feel that the wiki "instructions for authors" page is better suited for teaching people the ropes as lesson contributors.

Thanks @ssimpkin! While there's overlap with the wiki 'instructions for authors' page, I still think there's value to having it as a lesson - there'd be folks who want to write in Markdown who would never think of looking at our contribute page (and it's a great, simple overview).

Other editorial thoughts?

Agreed!

On Tue, Aug 25, 2015 at 11:26 AM, Ian Milligan notifications@github.com
wrote:

Thanks @ssimpkin https://github.com/ssimpkin! While there's overlap
with the wiki 'instructions for authors' page, I still think there's value
to having it as a lesson - there'd be folks who want to write in Markdown
who would never think of looking at our contribute page (and it's a great,
simple overview).

Other editorial thoughts?

—
Reply to this email directly or view it on GitHub
#61 (comment)
.

me too--i think the authors page is about our process and doesn't offer
much in the way of markdown, which we require. so it's super helpful.

a possible addition to the lesson would be a concluding paragraph or so
about the process of writing a markdown file (like a PH lesson) in a basic
text editor, knowing that all the formatting will show up eventually, and
that getting used to the idea of not actually seeing the formatting--but
rather the syntax for it--takes a little time but is super useful. this
makes the files highly portable (not just over time, but across different
platforms and editorial workflows!).

the one other addition i would like, but isn't necessarily essential, is to
have more consistent visualization of the rendering of markdown in the
tutorial itself so that users can skim through the lesson and easily see
what markdown produces when rendered or converted into something else like
HTML. it appears in some places, but not in a standardized way or evenly
across the examples. i think smoothing this out would make the lesson more
useful for those just skimming through to understand what markdown is, and
also even more useful for readers who sit down and go through the whole
thing and want to easily associate the syntax with a typographical style
they are used to. obviously the markdown renderer does this, but i think
there's real value in having it in the lesson itself as well. (the renderer
could be used for other things in the lesson, too, like instructing the
reader to take a raw .md file from the PH repository and paste it into the
renderer to see what happens...)

but it's going to be really great to have this on the lesson page!

On Tue, Aug 25, 2015 at 10:20 AM, Miriam Posner notifications@github.com
wrote:

Agreed!

On Tue, Aug 25, 2015 at 11:26 AM, Ian Milligan notifications@github.com
wrote:

Thanks @ssimpkin https://github.com/ssimpkin! While there's overlap
with the wiki 'instructions for authors' page, I still think there's
value
to having it as a lesson - there'd be folks who want to write in Markdown
who would never think of looking at our contribute page (and it's a
great,
simple overview).

Other editorial thoughts?

—
Reply to this email directly or view it on GitHub
<
#61 (comment)

.

—
Reply to this email directly or view it on GitHub
#61 (comment)
.

frederick w gibbs | assistant professor of history | univ. of new mexico
fredgibbs.net | @fredgibbs
http://www.twitter.com/fredgibbs

This lesson seems to me like it's ready to merge. Unless I'm mistaken, I think it's already been reviewed, and revisions have been made. It all looks good to me!

Ah, I missed the little commit hidden there. I think it looks ready to go! What do you think, @ssimpkin?

Sending it off to another colleague for a quick look, then it's just a
matter of adding the reviewers' names. Will wrap it up by the end of the
week. Excited to get it out there!

On 9 November 2015 at 08:43, Ian Milligan notifications@github.com wrote:

Ah, I missed the little commit hidden there. I think it looks ready to go!
What do you think, @ssimpkin https://github.com/ssimpkin?

—
Reply to this email directly or view it on GitHub
#61 (comment)
.

@ianmilligan1 I don't think anyone is posting this. Can you manage it?

Where do we find our images (i.e. do we have a central repository of our images, or do we just randomly find them on the Web and make sure we've got the rights)? I'm at a conference all week but can probably find some time.

Instructions here: https://github.com/programminghistorian/jekyll/wiki/Lesson-Images

But I can't figure out how to actually upload the image to the site. If you figure that out, let me know.

Sure, I can do that - wanna just shoot me it via e-mail? if you give me a good shortcut to downsize an image to 200 x 200 - any online platform that you use? My Photoshop is borked.

(am at a conference so there's a chance I might disappear until tomorrow at any point)

Nevermind, just found the world's sketchiest photo resizer site and used it. If you shoot me the image, I'll upload them together.

It also occurs to me - what section should this go into? Data Manipulation is the closest current fit, but it's not a great one. Any offhand thoughts, @acrymble?

Data Management, no? But the title is awkward. It's about formats for best
practices.

On Wed, Dec 2, 2015 at 7:39 PM, Ian Milligan notifications@github.com
wrote:

It also occurs to me - what section should this go into? Data Manipulation
is the closest current fit, but it's not a great one. Any offhand thoughts,
@acrymble https://github.com/acrymble?

—
Reply to this email directly or view it on GitHub
#61 (comment)
.

Maybe we need a new category.

On Wed, Dec 2, 2015 at 7:41 PM, Adam Crymble adam.crymble@gmail.com wrote:

Data Management, no? But the title is awkward. It's about formats for best
practices.

On Wed, Dec 2, 2015 at 7:39 PM, Ian Milligan notifications@github.com
wrote:

It also occurs to me - what section should this go into? Data
Manipulation is the closest current fit, but it's not a great one. Any
offhand thoughts, @acrymble https://github.com/acrymble?

—
Reply to this email directly or view it on GitHub
#61 (comment)
.

I figure Data Management is OK for now, but we should think about a new category?

In any case, it's LIVE!!! Hurray. Both on http://programminghistorian.org/lessons/ and http://programminghistorian.org/lessons/getting-started-with-markdown.

Can we start the publicity engine? 😀

Oh hey, awesome! Looks like it's under "Data Manipulation" instead of "Data
Management", though.

I'll send along a little bio blurb shortly.

Thanks again for all of your patience and suggestions. It was fun!

On 2 December 2015 at 18:21, Ian Milligan notifications@github.com wrote:

I figure Data Management is OK for now, but we should think about a new
category?

In any case, it's LIVE!!! Hurray. Both on
http://programminghistorian.org/lessons/ and
http://programminghistorian.org/lessons/getting-started-with-markdown.

Can we start the publicity engine? [image: 😀]

—
Reply to this email directly or view it on GitHub
#61 (comment)
.

Sorry @ssimpkin, fixed in the last commit. And yes, please send along a bio - probably easiest is to just e-mail it to me.

As per #119, pinging @miriamposner to let her know that this post is up. @acrymble's "Extracting Keywords" is up too. A banner day!

Gah, somehow I didn't see this! I will tweet up a storm tomorrow. Congrats, @ssimpkin and @acrymble!