-
Notifications
You must be signed in to change notification settings - Fork 21
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
Trial content for editting via Prose.io #33
base: master
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,14 +1,19 @@ | ||
--- | ||
title: Edit a post or page | ||
description: All you need is a GitHub account to write a blog post or suggest edits to any page. | ||
description: >- | ||
All you need is a GitHub account to write a blog post or suggest edits to any | ||
page. | ||
weight: 1 | ||
published: true | ||
--- | ||
|
||
## tl;dr | ||
|
||
1. Use the "Suggest Edits" link on an existing page or [click here][7] to add a new page. | ||
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. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 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. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yeah, I think that makes sense |
||
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. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Haven't gone through account creation process from prose, so this will need that testing first. |
||
1. Write/edit in [Markdown][3] using the web-based text editor. | ||
1. Click the "Save" icon to the right of your edits. | ||
|
||
## The long version | ||
|
||
|
@@ -87,5 +92,5 @@ We also have a custom `{{</* iframe */>}}` shortcode that accepts `src` and _CSS | |
[4]: /hack-this-site/edit-group-page/ | ||
[5]: https://gohugo.io/extras/shortcodes/#figure | ||
[6]: https://gohugo.io/extras/shortcodes/ | ||
[7]: https://github.com/hackshackers/hackshackers-hugo-content/new/master | ||
[7]: http://prose.io/#hackshackers/hackshackers-hugo-content | ||
[8]: https://help.github.com/articles/using-pull-requests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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 ofpublished: [true|false]