Add more explanations about how to add information to the website

[hegner]

No description provided.

[jouvin]

As a general remark, try to respect casing for product/service names. For example, github should be written GitHub. A global replace is needed basically: I don't add it as a comment to each instance!

[jouvin]

not content-> no content (not that the subject itself is useless...).

[hegner]

agreed.

[jouvin]

The same remark about casing applies toindico. Should beIndico`.

[jouvin]

Before opening a pull request, one must push back to its fork...

[hegner]

thanks. makes more sense now.

[hegner]

I incorporated the proposals and fixed the GitHub / Indico naming.

[jouvin]

I'd say: Despite this is not the recommended option, if you are not confortable with Git and you only want to do simple changes, the GitHub web interface allows you to add and edit the files in your browser. In this case, you don't need to have a local clone of your personal forkon GitHub.`

[jouvin]

Also, in the Adding to the newsletter section, the directory mentioned is incorrect: workinggroups -> newsletter

[hegner]

Let me know once you are done w/ the review. I'll wait with my next push till then.

[jouvin]

In the first sentence in the page, I'd replace HSF GitHub repository people by HSF GitHub contributors (making only contributors a link).

[jouvin]

I'd also replace: We all like to work in code editors; this lets you write content in a friendly editor using the easy markdown syntax (which is used by GitHub itself). by The site content is written using the Markdown syntax.

(markdown is another word that must be capitalized!).

[jouvin]

I think I'm done for now! Thanks again for the work done!

[jouvin]

One more thing! front-matter is mentioned several times. It'd be good in how to add and edit to add a few word on the fact that all files starts with a few special lines delimited by --- lines than contain metadata about the page and are called front-matter.

[jouvin]

And one last thing: the page title in the front-matter is incorrect: newsletter shoud be removed.

[hegner]

Incorporated your additional comments; should we merge?

[jouvin]

It looks much better! I have still a few (minor remark):

• GitHub’s Pages service: service should not be part of the anchor (in general we tend to put to many words in the anchor, IMO).
• Pages uses Jekyll link: Pages and Jekyll should be 2 separate links
• HSF website repository: HSF should not be part of the anchor
• liquid in side menu customization should be a link
• The liquid template engine used by Jekyll: only liquid should be a link
• liquid should be Liquid
• markdown should be Markdown (at least one occurence left at the end)
• Markdown syntax: only Markdown should be in the anchor (2 occurences at least)

Should be perfect then!

[jouvin]

And as usual one more thing! I'd renamed the file howto to howto-contribute in order to avoid future possible conflicts (also requires editing reference to it).

[hegner]

Can you make the last point a bug report?

[jouvin]

Why did you close the PR?

[hegner]

Did I close? By accident then.

[jouvin]

One last detail that you missed in my previous comment: the first reference to Liquid is not a link and should be one IMO. Then I am happy to merge!

[hegner]

Done

[jouvin]

Rename request tracked as a separate issue (#5), as requested by @hegner .

[jouvin]

Thanks for all the refinements done! Merging...

[hegner]

Thanks.