Right, we should make this ourselves, but in the right way, using the right path designed for this. The wheel is already created so we should find how to make the wheel and not trying to reinvent it.
In [1] seems to be the right steps to create a Jekyll theme from scratch. I think we should follow this, and configure our _config.yml with the published result. Before changing more in the page doc example I did in WP, I think we should follow this steps and try to make a theme with that and see the results. Carlos 2018-01-28 8:02 GMT+01:00 Alex Harui <aha...@adobe.com.invalid>: > > > On 1/27/18, 10:37 AM, "Gabe Harbs" <harbs.li...@gmail.com> wrote: > > >Nice direction. I wonder if it makes sense to start with a Jekyll theme > >such as the Jekyll-doc-theme[1] and build off of that. > > IMO, no. I just don't want to spend time chasing down the IP of all of > the bits of these themes. They may say they are MIT, but who knows about > some font or css they've borrowed from somewhere. I think I've done a > pretty good replication of the Royale Website header and footer. If we > can agree on what Carlos proposes or my suggested changes to it, I think I > can have it ready in a couple of hours and then we can just produce > content instead of providing more surface for IP nitpickers. I keep > hoping we will find a simple HTML implementation of what we want so we can > replicate parts of it across all of our web pages, from royale.a.o to > royale-docs to asdoc and the TryItNow app. If we keep using different > themes, we have to try to reproduce the commonality in each of those > themes. > > >The theme I linked to has the advantage of offering simple blogging > >capabilities as well. > > Jekyll was designed for blogs. Again, I think I can take a proposal from > Carlos and get it working in a couple of hours. > > Keep it simple. Less process, more content. We can get fancy later. > > My 2 cents, > -Alex > > -- Carlos Rovira http://about.me/carlosrovira
