[jira] [Commented] (NETBEANS-201) Replace plugin portal service
[ https://issues.apache.org/jira/browse/NETBEANS-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16846329#comment-16846329 ] Wade Chandler commented on NETBEANS-201: Awesome [~jkovalsky] Great stuff! > Replace plugin portal service > -- > > Key: NETBEANS-201 > URL: https://issues.apache.org/jira/browse/NETBEANS-201 > Project: NetBeans > Issue Type: Task > Components: website >Reporter: Wade Chandler >Assignee: Jiří Kovalský >Priority: Major > > The current NetBeans plugin portal site has a backing service used to help > upload, edit, list, etc plugin information for authors. We need something > similar to better support plugin authors and the plugin center. You can see > this at the following URL while it is still enabled > http://plugins.netbeans.org/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-151) Add link checking to project build or as a subproject
[ https://issues.apache.org/jira/browse/NETBEANS-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16769989#comment-16769989 ] Wade Chandler commented on NETBEANS-151: No particular technology or plan has been chosen or documented. However, the root issue is as we link to external documents or even things like the Slack sign up page, we need some way to verify all of those links added by people to tell us when something dead links or is broken versus manual checks or human detection. > Add link checking to project build or as a subproject > - > > Key: NETBEANS-151 > URL: https://issues.apache.org/jira/browse/NETBEANS-151 > Project: NetBeans > Issue Type: Task > Components: website >Reporter: Wade Chandler >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-125) Enumerate the template types needed for the new site based on various sections of the web site; this data will be used by the Groovy script which needs to be aid in c
[ https://issues.apache.org/jira/browse/NETBEANS-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16413068#comment-16413068 ] Wade Chandler commented on NETBEANS-125: [~vieiro] You might find the list here useful. I had similar lists in the Groovy script issue I just closed. The idea was to have templates for what seem main and noted subsections to allow different asides and Tech specific links etc. > Enumerate the template types needed for the new site based on various > sections of the web site; this data will be used by the Groovy script which > needs to be aid in conversion > --- > > Key: NETBEANS-125 > URL: https://issues.apache.org/jira/browse/NETBEANS-125 > Project: NetBeans > Issue Type: Task > Components: website >Reporter: Wade Chandler >Assignee: Wade Chandler >Priority: Major > > We need to create templates, and give them an identifier, to be used by > content and sidecar files, and eventually by JBake. These templates need to > be based or derived from the current sections of the new site which we wish > to keep. We need to map these to sections of the old site by relative paths. > These relative paths can then be used by the Groovy script which will process > the content in the hierarchy to correctly match up the page/template type for > the various content pages and sidecar files. This will cause the new site to > include the required content and structure for the specific content as the > static site is generated. > As an example, the new site has the platform top level domain files under the > "platform" directory. This pattern could then be mapped to > /platform/tutorials > https://platform.netbeans.org/tutorials/nbm-quick-start.html or perhaps > something else. > There is also the kb which has structures like this > https://netbeans.org/kb/docs/javaee and https://netbeans.org/kb/docs/java. > These can be linked to /kb/docs/java and kb/docs/javaee. These different > "sections", can have subtly different headers or footers as well as different > side bars which link to relevant other content. > The specifics of the templates themselves do not have to be worked out just > yet, but the names of them, which are valid values to be used by JBake, and > in the YAML sidecar files, do. The various templates can then be worked up as > needed after the list and requirements are determined. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Closed] (NETBEANS-124) Create Groovy script to generated required YAML side car files (meta-data) for content, and strip content from old site files
[ https://issues.apache.org/jira/browse/NETBEANS-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wade Chandler closed NETBEANS-124. -- Resolution: Workaround Closing as done by [~vieiro] with AsciiDoc and other scripts. > Create Groovy script to generated required YAML side car files (meta-data) > for content, and strip content from old site files > - > > Key: NETBEANS-124 > URL: https://issues.apache.org/jira/browse/NETBEANS-124 > Project: NetBeans > Issue Type: Task > Components: website >Reporter: Wade Chandler >Assignee: Wade Chandler >Priority: Major > > The new NetBeans statically generated website being developed at > https://github.com/wadechandler/netbeans-static-site uses JBake and Gradle to > build the site. It uses certain YAML files as "sidecar" files to the content > files which explain to a template the type of file it is along with other > meta-data, such as the document title etc. The new site uses Groovy templates > to allow for common headers, footers, and side bars. > These sidecar files, along with the main body content, allow for templates to > be matched to the content type of a file, and then for that file to have > everything it requires embedded inside of it to be served as a "static" web > site with no server side component dynamically binding the information at > runtime. This is a requirement of Apache projects web sites; to be static. > The Groovy script described in this issue will: > * Pull information such as the title, keywords, description, and other > meta-data which may be embedded in HTML or other file types, and place that > into the required sidecar YAML files of the build system > * Pull out the main body content from the the original HTML file and place it > into a file of the same name to match the YAML sidecar file per the new site > naming conventions (see the README.md file) > * Choose a template type for the content based on its file system hierarchy > which seems representative of the way current NetBeans website is laid out; > notice depending on the drill down into the web site, that certain side bars, > headers, etc differ or are enabled or disabled. The new site does this based > on the page/template type > This Groovy script is a development time tool which is used to transform the > old content into the format now needed. Once the conversion is done, then it > should no longer be needed. It will be able to be run from the Gradle build > like other aspects of the new sites build system; see buildSrc which is a > good place for this Groovy script to be placed as a Groovy class. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-125) Enumerate the template types needed for the new site based on various sections of the web site; this data will be used by the Groovy script which needs to be aid in c
[ https://issues.apache.org/jira/browse/NETBEANS-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16333596#comment-16333596 ] Wade Chandler commented on NETBEANS-125: Found while working on the Groovy scripting and also placed in that issues comments... A list of possible sections (or the sections) which should/could have special templates follows, trimmed from the above using a simple text editor since the lines were ordered. This represents 74 sections for which to have different template styles which the content processing script will place into the associated YAML files as it creates them (which could be further trimmed): ./about ./books ./community ./community/articles ./community/articles/interviews ./community/articles/javaone ./community/contribute ./community/guidelines ./community/kb ./community/lists ./community/lists/chats ./community/magazine ./community/netcat ./community/news ./community/news/newsletter ./community/partners ./community/photos ./community/releases ./community/sources ./community/teams ./community/teams/dev ./community/teams/evangelism ./community/teams/evangelism/docs ./community/teams/marketing ./community/teams/web ./downloads ./evangelism ./features ./features/cpp ./features/groovy ./features/html5 ./features/ide ./features/java ./features/java-on-client ./features/java-on-server ./features/javafx ./features/javame ./features/javascript ./features/php ./features/platform ./features/ruby ./features/scripting ./features/uml ./features/web ./kb ./kb/archive ./kb/articles ./kb/docs ./kb/docs/cnd ./kb/docs/ide ./kb/docs/java ./kb/docs/javaee ./kb/docs/javame ./kb/docs/php ./kb/docs/web ./kb/docs/webclient ./kb/docs/websvc ./kb/faqs ./kb/samples ./kb/trails ./platform ./platform/articles ./platform/articles/nbm_interviews ./platform/faqs ./platform/guide ./platform/guidelines ./platform/samples ./platform/tutorials ./platform/welcome ./platform/whatsnew ./switch ./uigestures ./updates > Enumerate the template types needed for the new site based on various > sections of the web site; this data will be used by the Groovy script which > needs to be aid in conversion > --- > > Key: NETBEANS-125 > URL: https://issues.apache.org/jira/browse/NETBEANS-125 > Project: NetBeans > Issue Type: Task > Components: website >Reporter: Wade Chandler >Assignee: Wade Chandler >Priority: Major > > We need to create templates, and give them an identifier, to be used by > content and sidecar files, and eventually by JBake. These templates need to > be based or derived from the current sections of the new site which we wish > to keep. We need to map these to sections of the old site by relative paths. > These relative paths can then be used by the Groovy script which will process > the content in the hierarchy to correctly match up the page/template type for > the various content pages and sidecar files. This will cause the new site to > include the required content and structure for the specific content as the > static site is generated. > As an example, the new site has the platform top level domain files under the > "platform" directory. This pattern could then be mapped to > /platform/tutorials > https://platform.netbeans.org/tutorials/nbm-quick-start.html or perhaps > something else. > There is also the kb which has structures like this > https://netbeans.org/kb/docs/javaee and https://netbeans.org/kb/docs/java. > These can be linked to /kb/docs/java and kb/docs/javaee. These different > "sections", can have subtly different headers or footers as well as different > side bars which link to relevant other content. > The specifics of the templates themselves do not have to be worked out just > yet, but the names of them, which are valid values to be used by JBake, and > in the YAML sidecar files, do. The various templates can then be worked up as > needed after the list and requirements are determined. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
