You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@netbeans.apache.org by "Wade Chandler (JIRA)" <ji...@apache.org> on 2018/03/25 15:09:00 UTC
[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 conversion
[ 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-unsubscribe@netbeans.apache.org
For additional commands, e-mail: commits-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists