Yup! Like this, there are some small tweaks needed to bring the page into
something consumable.

One of my little concerns is the navbar. I tried "dropdown-menu-right" on
the "About" for our links, but that didn't work. I'm missing something. If
somebody can find the right tweak, that'd be great.

I haven't done a deep dive into the github-markdown-css that we're
including. It's there, but dunno its effects, and haven't done a
side-by-side of "preview" and "on-site". We're darned close, so it's also a
minor issue.

Point being: I've done all my editing and file creation on github.com. Our
website workflow is easy-peasy, as I had hoped.

Cheers,
-g


On Mon, Dec 9, 2019 at 8:05 PM Dave Fisher <[email protected]> wrote:

> That’s the way!
>
> Sent from my iPhone
>
> > On Dec 9, 2019, at 5:29 PM, [email protected] wrote:
> >
> > This is an automated email from the ASF dual-hosted git repository.
> >
> > gstein pushed a commit to branch master
> > in repository https://gitbox.apache.org/repos/asf/petri-site.git
> >
> >
> > The following commit(s) were added to refs/heads/master by this push:
> >     new 751b1f4  put the page content into a bootstrap container
> > 751b1f4 is described below
> >
> > commit 751b1f44d35c4596b8762ef898b7c45398cfea8c
> > Author: Greg Stein <[email protected]>
> > AuthorDate: Mon Dec 9 19:29:10 2019 -0600
> >
> >    put the page content into a bootstrap container
> > ---
> > theme/apache/templates/base.html | 6 ++++--
> > 1 file changed, 4 insertions(+), 2 deletions(-)
> >
> > diff --git a/theme/apache/templates/base.html
> b/theme/apache/templates/base.html
> > index 639bc92..c1dd2de 100644
> > --- a/theme/apache/templates/base.html
> > +++ b/theme/apache/templates/base.html
> > @@ -81,8 +81,10 @@
> >
> >     </nav>
> >
> > -    {% block content %}
> > -    {% endblock %}
> > +    <div class="container">
> > +      {% block content %}
> > +      {% endblock %}
> > +    </div>
> >
> >     <footer class="navbar-expand-lg navbar-light bg-light">
> >       <div class="footer" id="footer">
> >
>
>

Reply via email to