You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Joseph Witt (JIRA)" <ji...@apache.org> on 2015/02/08 19:26:37 UTC

[jira] [Resolved] (NIFI-162) Create overall documentation/engage theme on website

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

Joseph Witt resolved NIFI-162.
------------------------------
    Resolution: Fixed

lots of good progress here.  New work in this space should be specific and on its own ticket.

> Create overall documentation/engage theme on website
> ----------------------------------------------------
>
>                 Key: NIFI-162
>                 URL: https://issues.apache.org/jira/browse/NIFI-162
>             Project: Apache NiFi
>          Issue Type: Task
>          Components: Documentation & Website, Tools and Build
>         Environment: apache nifi website
>            Reporter: Joseph Witt
>            Assignee: Joseph Witt
>              Labels: documentation
>             Fix For: 0.0.2
>
>         Attachments: NIFI-162.patch, NIFI-162.patch, NIFI-162.patch
>
>
> Perspectives / Flow of Documentation:
> - Overview
> -- What problem does NiFi solve?
> -- What is the general design philosophy of NiFi?
> -- What are some of the key features?
> - User Guide
> -- Dataflow Manager
> --- How to build flows
> --- Create / Share / Use templates
> --- How to monitor behavior/performance
> --- Data Provenance
> --- In-line documentation / change history
> -- Observer
> --- Read-only access
> - System Administration Guide
> --- How to install
> --- Best practice configuration
> --- Security / Hardening
> --- Controlling access/levels of access
> - Developer Guide
> -- What are the extension points
> -- What is a NAR and what does the Classloader hierarchy/model look like?
> -- How to build extensions
> -- Thinking about the right abstraction and considering cohesion/coupling for a processor or extension in general
> -- Emphasis on the user experience - the in-line documentation, the naming of properties, is a custom UI needed, etc..
> -- Key things to consider/design considerations/strengths/limitations
> -- How to contribute to Apache NiFI
> These are meant to flow logically from top to bottom where we want to gain interest in reading further by explaining the 'why' / the 'context'.  Then it flows into usage and capabilities of the application.  Then we flow into how to extend the application's capabilities to suit your needs and to contribute back to the community.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)