You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Davor Bonaci (JIRA)" <ji...@apache.org> on 2017/03/20 17:26:41 UTC

[jira] [Assigned] (BEAM-751) infrastructure for extracting code snippets into documentation

     [ https://issues.apache.org/jira/browse/BEAM-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Davor Bonaci reassigned BEAM-751:
---------------------------------

    Assignee: Robert Bradshaw  (was: James Malone)

> infrastructure for extracting code snippets into documentation
> --------------------------------------------------------------
>
>                 Key: BEAM-751
>                 URL: https://issues.apache.org/jira/browse/BEAM-751
>             Project: Beam
>          Issue Type: Improvement
>          Components: website
>            Reporter: Frances Perry
>            Assignee: Robert Bradshaw
>              Labels: starter
>             Fix For: Not applicable
>
>
> As we fill in more and more documentation, the number of code snippets is going to drastically increase, and we should ensure the quality of those snippets by automatically extracting them from code that is regularly compiled and tested.  
> Goals:
> * automatically extract code snippets from incubator-beam for use in the beam website documentation
> * use stable references so folks editing the code can clearly tell what documentation changes this will result in (good: specially formatted comment, bad: line number)
> * freshness (is live possible? or at least during the general 'jekyll build' phase?)
> The best we've found so far is using jekyll-gist with gist-it, but that would rely on fragile line numbers.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)