Skip to content

API docs #6

Description

@JimBobSquarePants

Update

Docs are available at:
https://sixlabors.github.io/docs/


Original Issue

From @JimBobSquarePants on January 13, 2016 0:43

I would like to create documentation like the following:

http://dotnet.github.io/

MS are using the library below but I can't seem to follow the instructions.

http://dotnet.github.io/docfx/

Copied from original issue: JimBobSquarePants/ImageProcessor#297

Activity

  1. JimBobSquarePants commented on Oct 30, 2016

    @JimBobSquarePants
    MemberAuthor

    From @robertjf on January 13, 2016 0:53

    @JimBobSquarePants I have a little spare time at the moment and can take a look at it - have had a look through the walkthroughs etc.

    Have you started a project for this in Visual Studio yet? If so do you want to check it in and I'll start with that, or do you want me to start from scratch? And is your preference to use Visual Studio IDE or configure it under dnx instead?

  2. JimBobSquarePants commented on Oct 30, 2016

    @JimBobSquarePants
    MemberAuthor

    Awesome! Thanks mate 👍

    I haven't started a project yet, I planned to set a docs folder and stick a web project in there to do it all so I could preview.

  3. JimBobSquarePants commented on Oct 30, 2016

    @JimBobSquarePants
    MemberAuthor

    From @priyanshu92 on May 5, 2016 15:42

    @JimBobSquarePants I looked at it and created a sample documentation following their tutorials and I was able to create it but it doesn't seem to work on .NET Core projects 😕 with project extension as **.xproj. I think currently it only supports .csproj files. 😞

    Let me know if I can help.

  4. JimBobSquarePants commented on Oct 30, 2016

    @JimBobSquarePants
    MemberAuthor

    @priyanshu92 Thanks for giving it a go, I had issues myself when I tried. Maybe I should look elsewhere for something to use.

    Ideally I want something people can make pull requests against. I just wish Jekyll wasn't such a chore on Windows machines.

  5. M-Zuber commented on Oct 30, 2016

    @M-Zuber
    Contributor

    Volunteering to try and kickstart this.

  6. JimBobSquarePants commented on Oct 30, 2016

    @JimBobSquarePants
    MemberAuthor

    You're on! 😄 That would be awesome!

    If possible I would like to get them to build into a /docs/ folder so that I can host from github pages easily.

  7. daveaglick commented on Oct 30, 2016

    @daveaglick

    @M-Zuber Not sure you've been following along, but the Wyam docs recipe is almost done! I'm getting Cake up and running first, but the Recipe in general should be just about ready. I merged it into the develop branch last week and a release should be coming in 2-3 weeks.

  8. daveaglick commented on Oct 30, 2016

    @daveaglick

    img_2458

  9. M-Zuber commented on Nov 2, 2016

    @M-Zuber
    Contributor

    I didn't forget, RL has been very the last bit.
    But it is in in my schedule for today :fingers-crossed:

  10. M-Zuber commented on Nov 2, 2016

    @M-Zuber
    Contributor

    It seems that docfx does not yet support xproj/project.json 😢

  11. 10 remaining items

  12. dlemstra commented on Nov 4, 2016

    @dlemstra
    Member

    Would it be possible to add examples that include images to the documentation? That will have a big impact on the size of the project. And we should only update the documentation when a new release has been published so keeping it in sync is probably not an issue.

  13. M-Zuber commented on Nov 4, 2016

    @M-Zuber
    Contributor

    Yes, but having it in a seperate repo means a build step of cloning docs repo, running docfx, and pushing back up.
    Simpler to just have it generated by build.
    Images could be stored in another repo and served via github pages though

  14. JimBobSquarePants commented on Nov 4, 2016

    @JimBobSquarePants
    MemberAuthor

    I could add an app to azure that serves any images perhaps

  15. M-Zuber commented on Nov 4, 2016

    @M-Zuber
    Contributor

    Also a valid idea.
    I'm away from the computer until Sunday, but available on the phone for another few hours.
    Would love to reach a consensus so I can make the PR first thing Sunday

  16. JimBobSquarePants commented on Nov 7, 2016

    @JimBobSquarePants
    MemberAuthor

    Apologies for the slow reply, birthday weekend....

    I think we should go with adding this to the main repo. There's will be no images initially since it will be purely API docs. Anything additional custom images I can serve from Azure, another github pages repo, or somewhere else, as and when required.

    Ideally I would serve the documentation from a /docs/ folder in the main repo. I will need to either preserve a CNAME file containing the domain http://imagesharp.net within that folder or recreate it on build.

    https://support.dnsimple.com/articles/github-pages/#one-final-step

  17. M-Zuber commented on Nov 7, 2016

    @M-Zuber
    Contributor

    Happy birthday again! and no worries.
    apologies on my end if I sounding pressuring.

    Anyways here you have the basis #22

  18. added this to the milestone on Nov 21, 2016
  19. moshegutman commented on Dec 18, 2016

    @moshegutman

    What are your thoughts about using GitHub Pages for Tutorials/Sample code examples. This way people can easily edit them.

  20. M-Zuber commented on Dec 18, 2016

    @M-Zuber
    Contributor

    The default docfx template includes a link on every page exactly for allowing people to quickly jump from the docs to making a pull request edit

  21. JimBobSquarePants commented on Dec 19, 2016

    @JimBobSquarePants
    MemberAuthor

    Yeah, we just need to get the docs up and running. Hoping to have that for beta1

  22. added a commit that references this issue on Nov 27, 2019
  23. added a commit that references this issue on Jan 18, 2020
  24. added 2 commits that reference this issue on Feb 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions