Wade Chandler created NETBEANS-125:
--------------------------------------
Summary: Enumerated 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
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
(v6.4.14#64029)
