Hi Steve, yes I understand you just want to write some content.
But then why not give the approach I just mentioned a try?
You can totally skip the staging branch and docker stuff.
I will *personally* keep using staging when I'm not sure about formatting
and/or am working on something which I want to shape visually. I wouldn't
have this option on github pages as its support for style is way more
limited, but having more options doesn't seem like a drawback.
If you just want to update some text, go ahead on production directly.
Heck, worst case a mistake can be fixed or reverted.. at least it's
versioned ;)
On 22 Apr 2016 16:15, "Steve Ebersole" <steve(a)hibernate.org> wrote:
Right, this is actually exactly what I end up doing for any dealing
with
hibernate.org or in.relation.to...
Keep in mind I just want to author come content :)
Personally I find the whole process just gets in the way. Generally right
out of the chute we have to deal with forced pushes on staging and getting
that all straightened out. Then I have to locally fight docker, etc to get
the site built and hosted. It just feels like a lot (to me) to author some
content.
On Fri, Apr 22, 2016 at 5:30 AM Sanne Grinovero <sanne(a)hibernate.org>
wrote:
> There's a middle-ground strategy which might be cool to try.
>
> Go here:
> -
>
https://github.com/hibernate/hibernate.org/edit/production/orm/roadmap.adoc
>
> edit the doc within the browser, confirm the changes with a brief
> commit message and CI should pick it up, then publish within 5
> minutes.
>
> I just did this for the Search roadmap, although I opted for the
> 'staging' branch to try it out.. and because I regularly screw up the
> syntax.
>
> -- Sanne
>
>
> On 21 April 2016 at 23:57, Davide D'Alto <daltodavide(a)gmail.com> wrote:
> > Hi Steve,
> > what problems are you having with hibernate.org?
> > I agree with Gunnar that we should try to stick with one look & feel if
> > possible.
> >
> > On Thu, Apr 21, 2016 at 9:00 PM, Steve Ebersole <steve(a)hibernate.org>
> wrote:
> >
> >> Because I find it incredibly easier to work with GitHub wiki as
> opposed to
> >>
hibernate.org for authoring.
> >>
> >> On Thu, Apr 21, 2016, 12:42 PM Gunnar Morling <gunnar(a)hibernate.org>
> >> wrote:
> >>
> >> > Hey,
> >> >
> >> > What's the reason for maintaining the roadmap in the wiki rather
than
> >> >
hibernate.org itself?
> >> >
> >> > I hoped we'd centralize this kind of information on
hibernate.org;
> Looks
> >> > a tad more professional to have everything with the same look &
field
> >> > rather than pointing to other resources as the wiki... Also
> searchability
> >> > benefits, should we once have a site search.
> >> >
> >> > --Gunnar
> >> >
> >> >
> >> >
> >> > 2016-04-21 19:36 GMT+02:00 Steve Ebersole <steve(a)hibernate.org>:
> >> >
> >> >> I have started maintaining[1] the ORM Roadmap external to
>
hibernate.org
> >> >> itself. I'd like to adjust the link to when under orm/ to
point to
> this
> >> >> external URL rather than the parameterized {project}/roadmap
> target. Is
> >> >> that possible? And if so, how?
> >> >>
> >> >> [1]
https://github.com/hibernate/hibernate-orm/wiki/Roadmap
> >> >>
> >> > _______________________________________________
> >> >> hibernate-dev mailing list
> >> >> hibernate-dev(a)lists.jboss.org
> >> >>
https://lists.jboss.org/mailman/listinfo/hibernate-dev
> >> >>
> >> >
> >> >
> >> _______________________________________________
> >> hibernate-dev mailing list
> >> hibernate-dev(a)lists.jboss.org
> >>
https://lists.jboss.org/mailman/listinfo/hibernate-dev
> >>
> > _______________________________________________
> > hibernate-dev mailing list
> > hibernate-dev(a)lists.jboss.org
> >
https://lists.jboss.org/mailman/listinfo/hibernate-dev
>