Skip to content
This repository was archived by the owner on Mar 25, 2018. It is now read-only.
This repository was archived by the owner on Mar 25, 2018. It is now read-only.

List of Documentation Issues to Be Worked on from nodejs/iojs.org (formerly iojs/website) #10

Description

@bnb

I have tagged issues from the old iojs/website repo, now located at nodejs/iojs.org, with docs and invalid to indicate that they should be handled by the Docs WG, and removed them from the new.nodejs.org agenda.

These issues are still important, and need to be addressed. They just aren't in the perfect place to do so - thus, this issue has been created.

List: node/iojs.org - issues tagged with "docs"

These issues are something that I think can be taken care of by the Docs WG. Feel free to pull these into an issue or PR in this repo - if you do, though, make sure you link the issue in nodejs/iojs.org you're working from.

Activity

  1. stringparser commented on Jun 22, 2015

    @stringparser

    @nodejs/iojs-es, concerning API docs and open questions about API localization docs.
    EDIT: Related to #11

  2. ungoldman commented on Feb 11, 2016

    @ungoldman

    Looks like every issue in the list linked to above (node/iojs.org - issues tagged with "docs") is now closed. Is it safe to assume this issue can be closed too?

  3. Trott commented on Mar 13, 2018

    @Trott
    Member

    Closing as this repository is dormant and likely to be archived soon. If this is still an issue, feel free to open it as an issue on the main node repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions