Skip to content

Decide the publishing workflow #2

Open

Description

@apoikola

We need publishing workflow and tooling which makes it:

  • easy to comment and modify the original source of the spec
  • easy to publish HTML and PDF versions from releases without manual work

We could use for example W3C bikeshed framework for publishing HTML and PDF from Markdown source.

Then we would need easy collaborative environment for updating the markdown source. Below one workflow experimentation where the original source is kept in Google drive.

1A. Copy the link: http://bit.ly/mydata2html to “Load from URL” in here: https://api.csswg.org/bikeshed

OR

1B. Run on your command-line the following curl command
´´´curl https://api.csswg.org/bikeshed/ -F url=http://bit.ly/mydata2html > index.html´´´

  1. Make some changes in the original source http://bit.ly/sourcemarkdown and try 1A/B again.

Activity

  1. apoikola commented on Sep 15, 2016

    @apoikola
    ContributorAuthor

    Addition to the earlier I suggest that we start using Github issues for managing suggested changes to the spec.

    Labeling could follow for example:
    https://github.com/sandhawke/spec-labels-min/labels?sort=name-asc

    Issues can be referenced directly from the Bikeshed markdown source and the issues discussion can be directed to the Gitter chat: https://gitter.im/mydata-stack

  2. self-assigned this
    on Sep 15, 2016
  3. added this to the 1.2 version milestone on Sep 15, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions