-
Notifications
You must be signed in to change notification settings - Fork 463
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
Convert wiki to markdown #1234
Convert wiki to markdown #1234
Conversation
Renaming References: |
I'm not too worried about where this sits in sorting order since we'll be On Tue, May 26, 2015 at 12:45 PM, Peter Jas notifications@github.com
|
Nevertheless I suggested in the spirit of "better convention should go viral": keeping docs on top, then goes the rest of the repository assets. 🎌 |
Linux uses text files, that's not something we should encourage to go viral
|
We'll stick with docs. It's more node-y |
6461788
to
6eec94b
Compare
4842d2d
to
0bfdcc6
Compare
brought this back to life. Added tasks to show progress. We are close to getting this done! |
😍 |
0ba948a
to
50e7608
Compare
Okay, this should cover all the pages I have. @xzyfer we probably want to get this in before the docs change for 3.3 :) |
- doc index - makefile and autotools docs - convert local links to markdown - contributing and dev environment, triage, compat - function, context, importer, value, errors, unicode, others
50e7608
to
8676263
Compare
squashed to single commit |
|
||
### Implementing libsass | ||
|
||
If you're interested in implementing libsass in your own project see the [API Documentation](api-doc.md) which now includes implementing |
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.
Maybe keep the consistent naming convention of "LibsSass" > "libsass"
|
||
## ABI forward compatibility | ||
|
||
We use a functional API to make dynamic linking more robust and future compatible. The API is not yet 100% stable, so we do not yet guarantee ABI forward compatibility. We will do so, once we increase the shared library version above 1.0. |
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.
Can you link to the API here so people can read up on it for further details if they find a problem?
The docs look good to me, just did a few copy edits/notes to watch out for 😄 thanks for doing this! |
Thanks for looking through these. I probably won't get to making these On Thu, Oct 8, 2015, 8:28 AM Una Kravets notifications@github.com wrote:
|
I'd be happy to! |
|
||
| Issue Tracker | Issue Triage | Community Guidelines | | ||
|-------------------|----------------------------------|-----------------------------| | ||
| We're always needing help, so checkout our issue tracker, help some people out, and read our article on [Contributing](contributing.md)! It's got all the details on what to do! | To help understand the process of triaging bugs, have a look at our [Issue-Triage](triage.md) document. | Oh, and don't forget we always follow [[Sass Community Guidelines|http://sass-lang.com/community-guidelines]]. Be nice and everyone else will be nice too! | |
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 you want "check out" here.
http://grammarist.com/spelling/checkout-check-out/
copy edits, case changes, punctuation in docs
Work in progress converting all the local wiki articles to markdown files and linking them appropriately.
After this is complete, the wiki will link to https://github.com/sass/libsass/tree/master/docs
Fixes #1226
Check it out: https://github.com/drewwells/libsass/blob/feature/md/docs/README.md
Internals