All, For anyone looking to make modifications to the website, the readme in the nifi-site directory should contain all the details for setting up the build environment and a brief overview of where stuff is. It also describes the process for the automated deployment. If someone is lacking, please let me know and we'll get it squared away.
Dan, I'm not sure the best approach here but I agree that we need to get those documents on here too. The issue is that the navigation built into the help page is dynamic and contains links for the guides and REST API documentation. The guides and the REST API documentation have some pre-processing they go through prior to being bundled in the website that doesn't happen when they are included in the application. So we'd either need to come up with another approach for navigating between component documentation or rip out the existing help from a running instance and manually remove the links for the guides and REST API. Neither of this options thrill me but we definitely need to come up with something. If they could be generated at build time that would definitely solve this issue but that's easier said then done as your earlier emails have stated. Matt On Fri, May 15, 2015 at 1:30 PM, Dan Bress <[email protected]> wrote: > Matt, > The website looks great! I'd like us to incorporate the > processor/controller service/reporting task documentation into the > website. I think having this information on the website will showcase all > the awesome input/output formats that are available in NiFi, and help new > users see how NiFi can fit into their system. > > Short term, could we work towards copying the html out of a running > instance of NiFi and putting it on the website? I realize we need to come > up with a sort of "aggregator" page to list all the processors/controller > services/reporting tasks and link to their documentation. I can help with > this if you'd like. > > Long term, I'd like us to have an automated way of generating this > documentation at some point during the release process. I've thought about > it a little and don't have any great ideas. I first wanted to use a Maven > plugin, but this has dependency issues (it would depend on the > nifi-documentation jar file that is being built as part of the build). We > could have a script, or add a target to the nifi.sh script that just starts > nifi enough to generate the documentation and then stops. I'm totally open > to any ideas people have on this piece. > > Let me know what you think, > > Dan Bress > Software Engineer > ONYX Consulting Services > > ________________________________________ > From: Joe Witt <[email protected]> > Sent: Wednesday, May 13, 2015 9:41 AM > To: [email protected] > Subject: Re: Website Transition > > Matt, > > Nice! Thanks for sticking with this for so long. > > Look forward to seeing the live version. > > Thanks > Joe > > On Tue, May 12, 2015 at 11:11 PM, Matt Gilman <[email protected]> > wrote: > > All, > > > > I am in the process of transitioning our website to the layout/design we > > discussed a few months ago. I believe at this time the CMS tool has been > > disabled. I am going to upload the new site content this evening. Once > > everything is in place infra will update the pubsub config to point to > the > > new content. > > > > Future updates should be able to be done in an automated fashion. I've > > worked through the mechanics of this and will send out detailed > > instructions once everything is situated. Thanks. > > > > Matt > > > > https://issues.apache.org/jira/browse/INFRA-9291 >
