Trial content for editting via Prose.io #33
Conversation
|
Paired with hackshackers/hackshackers-hugo#86 Not complete, just wanted to test the flow. The tl;dr did get longer, so let me know what you think of that. Longer version needs more work, but I'm done for the day, so I'll have to come back |
| All you need is a GitHub account to write a blog post or suggest edits to any | ||
| page. | ||
| weight: 1 | ||
| published: true |
There was a problem hiding this comment.
this gets added automatically by prose :/
There's a ticket open for it, but is it acceptable for now?
There was a problem hiding this comment.
I think so, published is not a known post-level variable in Hugo so it would just get treated (and ignored) as custom metadata.
FWIW Hugo uses draft: [false|true] instead of published: [true|false]
| 1. Write/edit in [Markdown][3] using GitHub's web-based text editor. | ||
| 1. Keep clicking the *big green buttons* until your [pull request][8] is created. | ||
| 1. Use the "Suggest Edits" link on an existing page | ||
| - Alternatively, create a new page by [navigating to the appropriate website directory][7] and clicking the "New file" button. |
There was a problem hiding this comment.
Is this "create new" process acceptable? We could direct to a specific page like before, but it makes assumptions about where the user wants for page...
There was a problem hiding this comment.
Yeah, I think that makes sense
| 1. Keep clicking the *big green buttons* until your [pull request][8] is created. | ||
| 1. Use the "Suggest Edits" link on an existing page | ||
| - Alternatively, create a new page by [navigating to the appropriate website directory][7] and clicking the "New file" button. | ||
| 1. Click the green "Power button" in the bottom right to authorize on GitHub (or create an account). |
There was a problem hiding this comment.
Haven't gone through account creation process from prose, so this will need that testing first.
2 participants
This pull request has been automatically generated by prose.io.