<div dir="ltr">WildScribe is the kind of thing that could be generated and pushed somewhere within a GitHub action.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Feb 18, 2020 at 7:29 PM Brian Stansberry <<a href="mailto:brian.stansberry@redhat.com">brian.stansberry@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-family:"trebuchet ms",sans-serif">So AIUI once we do this, the <a href="https://wildscribe.github.io/" target="_blank">https://wildscribe.github.io/</a> site will get no further updates for WF, and the text in the middle will be updated to note that model reference docs for later versions can now be found on <a href="http://docs.wildfly.org" target="_blank">docs.wildfly.org</a>, probably with an example link to <a href="http://docs.wildfly.org/19/#model-reference" target="_blank">docs.wildfly.org/19/#model-reference</a> page.</div><div class="gmail_default" style="font-family:"trebuchet ms",sans-serif"><br></div><div class="gmail_default" style="font-family:"trebuchet ms",sans-serif">Which sounds fine.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Feb 18, 2020 at 12:10 PM James Perkins <<a href="mailto:jperkins@redhat.com" target="_blank">jperkins@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hello All,<br><div>It's been some time since I brought up adding the Wildscribe documentation to the WildFly docs. I've got a <a href="https://github.com/wildfly/wildfly/pull/12934" target="_blank">draft PR</a> up [1] which implements this idea. You can see the results at <a href="https://jamezp.github.io/wildfly.github.io/19/#model-reference" target="_blank">https://jamezp.github.io/wildfly.github.io/19/#model-reference</a>.</div><div><br></div><div>Does anyone have any concerns or further ideas about adding the Wildscribe documentation do <a href="http://docs.wildfly.org" target="_blank">docs.wildfly.org</a>? Any input is welcome.</div><div><br></div><div>[1]: <a href="https://github.com/wildfly/wildfly/pull/12934" target="_blank">https://github.com/wildfly/wildfly/pull/12934</a></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Nov 1, 2019 at 12:17 PM James Perkins <<a href="mailto:jperkins@redhat.com" target="_blank">jperkins@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hello All,<div>I assume everyone is aware of what Wildscribe [1] is. I've had a thought that instead of having this massive site that will keep growing with each version of WildFly released that we start adding this model documentation on the WildFly Documentation site [2]. The idea is to just add a link on each releases index page with a link to the model descriptions.</div><div><br></div><div>This would be automated as well with the docs project within WildFly. It means that as part of the release process when building the docs the Wildscribe model pages would be generated automatically.</div><div><br></div><div>My proposal would be for WildFly 19+ we would no longer update the Wildscribe website. As you can see on the site if you click on versions it's getting quite long :). All new Wildsribe pages would be present on the main documentation for that version. The Wildscribe site would have a note about where the documentation would now be for newer releases.</div><div><br></div><div>Any thoughts or concerns about this? If not objections I'll file a JIRA and do some work on this as it shouldn't take all that long.</div><div><br></div><div>[1]: <a href="https://wildscribe.github.io/" target="_blank">https://wildscribe.github.io/</a></div><div>[2]: <a href="https://docs.wildfly.org" target="_blank">https://docs.wildfly.org</a> <br clear="all"><div><br></div>-- <br><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div>James R. Perkins</div><div>JBoss by Red Hat</div></div></div></div></div></div></div>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div>James R. Perkins</div><div>JBoss by Red Hat</div></div></div></div></div>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a></blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr"><div dir="ltr">Brian Stansberry<div>Manager, Senior Principal Software Engineer</div><div>Red Hat</div></div></div>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a></blockquote></div>