Skip to content
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

Merged
merged 3 commits into from
Oct 24, 2015
Merged

Convert wiki to markdown #1234

merged 3 commits into from
Oct 24, 2015

Conversation

drewwells
Copy link
Contributor

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

  • Front page
  • API doc page
  • Build
    • win/darwin/linux
    • autotools, makefile
    • minGW
    • Visual Studio
    • Gentoo
  • Dev setup
  • Implementations
  • compat plan
  • unicode and charset support

Internals

  • Plugins
  • Context
  • Function
  • Importer
  • Custom function
  • Value
  • Trace
  • Source maps

@coveralls
Copy link

Coverage Status

Coverage remained the same at 80.28% when pulling 75b54e6 on drewwells:feature/md into 221d7fb on sass:master.

@ghost
Copy link

ghost commented May 26, 2015

Renaming docs to Documentation will stick the directory always on top (unless, of course, you have some directory like BAM which doesn't happen very often).

References:

@drewwells
Copy link
Contributor Author

I'm not too worried about where this sits in sorting order since we'll be
linking to it from the README and wiki rather than hunting for it in the
source tree.

On Tue, May 26, 2015 at 12:45 PM, Peter Jas notifications@github.com
wrote:

Renaming docs to Documentation will stick the directory always on top
(unless, of course, you have some directory like BAM which doesn't happen
very often).

References:


Reply to this email directly or view it on GitHub
#1234 (comment).

@ghost
Copy link

ghost commented May 26, 2015

Nevertheless I suggested in the spirit of "better convention should go viral": keeping docs on top, then goes the rest of the repository assets. 🎌

@drewwells
Copy link
Contributor Author

Linux uses text files, that's not something we should encourage to go viral
On Tue, May 26, 2015 at 2:31 PM Peter Jas notifications@github.com wrote:

Nevertheless I suggested in the spirit of "better convention should go
viral": keeping docs on top, then goes the rest of the repository assets. [image:
🎌]


Reply to this email directly or view it on GitHub
#1234 (comment).

@xzyfer
Copy link
Contributor

xzyfer commented May 26, 2015

We'll stick with docs. It's more node-y

@drewwells drewwells force-pushed the feature/md branch 3 times, most recently from 6461788 to 6eec94b Compare September 7, 2015 22:03
@drewwells drewwells changed the title [DO NOT MERGE] Convert wiki to markdown Convert wiki to markdown Sep 7, 2015
@drewwells drewwells force-pushed the feature/md branch 7 times, most recently from 4842d2d to 0bfdcc6 Compare September 7, 2015 23:00
@drewwells
Copy link
Contributor Author

brought this back to life. Added tasks to show progress. We are close to getting this done!

@xzyfer
Copy link
Contributor

xzyfer commented Sep 7, 2015

😍

@drewwells
Copy link
Contributor Author

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
@drewwells
Copy link
Contributor Author

squashed to single commit

@xzyfer xzyfer self-assigned this Sep 28, 2015

### Implementing libsass

If you're interested in implementing libsass in your own project see the [API Documentation](api-doc.md) which now includes implementing
Copy link
Contributor

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.
Copy link
Contributor

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?

@una
Copy link
Contributor

una commented Oct 8, 2015

The docs look good to me, just did a few copy edits/notes to watch out for 😄 thanks for doing this!

@drewwells
Copy link
Contributor Author

Thanks for looking through these. I probably won't get to making these
changes for a while. You can send a PR to this branch and I'll merge it in
with this.

On Thu, Oct 8, 2015, 8:28 AM Una Kravets notifications@github.com wrote:

The docs look good to me, just did a few copy edits/notes to watch out for [image:
😄] thanks for doing this!


Reply to this email directly or view it on GitHub
#1234 (comment).

@una
Copy link
Contributor

una commented Oct 8, 2015

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! |

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/

UNA A. KRAVETS and others added 2 commits October 8, 2015 09:56
@xzyfer xzyfer added this to the 3.3 milestone Oct 24, 2015
xzyfer added a commit that referenced this pull request Oct 24, 2015
@xzyfer xzyfer merged commit bb090ed into sass:master Oct 24, 2015
@drewwells drewwells deleted the feature/md branch October 24, 2015 04:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Cleaning up implementations wiki page
5 participants