Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Add a contributing guide #18
Comments
|
Here’s some text the Contributing guide could include: The [`property/`](https://github.com/jgthms/css-reference/tree/master/property) directory contains the HTML descriptions of each property. For example, the explanation and examples for the [`align-content`](http://cssreference.io/property/align-content/) property is in [`property/align-content/index.html`](https://github.com/jgthms/css-reference/blob/master/property/align-content/index.html).
However, I am confused by seeing that the text in those HTML was apparently generated from Markdown, yet I don’t see any Markdown source files in the repo. It would be nice if the contributing guide either pointed to the Markdown files or explicitly said “while Markdown was used for the initial build, changes from now on should be made in the raw HTML”. |
|
@roryokane I think it was written in HTML, not markdown. But it missed some build scripts. For example, how to generate files in |
|
@yuezk Here is why I think the text was originally written with Markdown:
|
|
@roryokane，you are right. |
As newbie, I'd like to help but I'm little bit lost I don't know where I can add/edit properties.