g to use GitHub Pages for the live site. These seem to conflict
> >>> as
> >>> GitHub pages wants the site in the /docs directory while pypubsub seems to
> >>> imply it needs to be in the root directory.
> >>>>
> >>>> I am able to get
iew
>>> site on the asf-staging branch and the live site at master. However, the
>>> instructions for the staging site seem to imply using pypubsub where I am
>>> attempting to use GitHub Pages for the live site. These seem to conflict as
>>> GitHub pages wants the site in the /do
>> https://apache.github.io/logging-site> but it is not being reflected at
>>> https://logging.apache.org <https://logging.apache.org/>.
>>>>
>>>> At this point without clearer instructions from infra I am not sure
>>> where to go to ma
irectory.
> > >>>>
> > >>>> I am able to get a site up at https://apache.github.io/logging-site <
> > https://apache.github.io/logging-site> but it is not being reflected at
> > https://logging.apache.org <https://logging.apache.org/>.
> >
he/logging-site>. I used jbake to generate the
> >
> > >> CMS portion of the site. It is pretty easy. All you have to do is
> >
> > >>>>>>
> >
> > >>>>>> cd sources
> >
> > >>>>>> Make the required changes
gt; > where to go to make the site live.
> > >
> > > I have started a confluence page to document managing the site but it
> > seems much easier than using the CMS.
> > >
> > > Ralph
> > >
> > >
> > >
> > >> On Aug 5,
>>>>>>
>
> >>>>>> You will then have a viewable site in the /docs directory and can
>
> >> view it by opening docs/index.html in the browser.
>
> >>>>>>
>
> >>>>>> I created a .asf.yaml
gt;>> Make the required changes
>
> >>>>>> mvn install
>
> >>>>>>
>
> >>>>>> You will then have a viewable site in the /docs directory and can
>
> >> view it by opening docs/index.html in the browser.
>
> >>>
se listed on this
> >> page [1] on managing project websites. Infra is assembling a Wiki page
> [2]
> >> on migrating a website from the CMS, and is looking forward to helping
> >> projects with this transition.
> >>
> >> Please let me know whether
em to conflict as
>> GitHub pages wants the site in the /docs directory while pypubsub seems to
>> imply it needs to be in the root directory.
>>>>>>
>>>>>> I am able to get a site up at https://apache.github.io/logging-site <
>> https://apach
>> instructions for the staging site seem to imply using pypubsub where I am
>> attempting to use GitHub Pages for the live site. These seem to conflict as
>> GitHub pages wants the site in the /docs directory while pypubsub seems to
>> imply it needs to be in the root directory
ument managing the site but it
>>>>> seems much easier than using the CMS.
>>>>>
>>>>> Ralph
>>>>>
>>>>>
>>>>>
>>>>>> On Aug 5, 2020, at 5:30 AM, Andrew Wetmore
>> I am able to get a site up at https://apache.github.io/logging-site <
> https://apache.github.io/logging-site> but it is not being reflected at
> https://logging.apache.org <https://logging.apache.org/>.
> >>>>
> >>>> At this point without clearer ins
directory.
>>>>
>>>> I am able to get a site up at https://apache.github.io/logging-site
>>>> <https://apache.github.io/logging-site> but it is not being reflected at
>>>> https://logging.apache.org <https://logging.apache.org/>.
>&g
tps://logging.apache.org/>.
> >>
> >> At this point without clearer instructions from infra I am not sure where
> >> to go to make the site live.
> >>
> >> I have started a confluence page to document managing the site but it
> >>
to make the site live.
>>
>> I have started a confluence page to document managing the site but it seems
>> much easier than using the CMS.
>>
>> Ralph
>>
>>
>>
>>> On Aug 5, 2020, at 5:30 AM, Andrew Wetmore wrote:
>>>
>&g
ve.
>
> I have started a confluence page to document managing the site but it seems
> much easier than using the CMS.
>
> Ralph
>
>
>
>> On Aug 5, 2020, at 5:30 AM, Andrew Wetmore wrote:
>>
>> Hi:
>>
>> I am part of the Infrastructure team
site but it seems
much easier than using the CMS.
Ralph
> On Aug 5, 2020, at 5:30 AM, Andrew Wetmore wrote:
>
> Hi:
>
> I am part of the Infrastructure team, and am writing to ask whether your
> project is still using the Apache CMS for your project website. As you
>
rt of the Infrastructure team, and am writing to ask whether your
> project is still using the Apache CMS for your project website. As you
> know, the CMS is reaching end-of-life, and we need projects to move their
> websites onto a different option within the next few weeks.
>
> There
ated.
>>>
>>> On Wed, 5 Aug 2020 at 07:31, Andrew Wetmore wrote:
>>>>
>>>> Hi:
>>>>
>>>> I am part of the Infrastructure team, and am writing to ask whether your
>>>> project is still using the Apache CMS for your pr
e (which might take less time to upload), too, but I think that's
> > unrelated.
> >
> > On Wed, 5 Aug 2020 at 07:31, Andrew Wetmore wrote:
> >>
> >> Hi:
> >>
> >> I am part of the Infrastructure team, and am writing to ask whethe
, but I think that's
> unrelated.
>
> On Wed, 5 Aug 2020 at 07:31, Andrew Wetmore wrote:
>>
>> Hi:
>>
>> I am part of the Infrastructure team, and am writing to ask whether your
>> project is still using the Apache CMS for your project website. As you
blishing the
site (which might take less time to upload), too, but I think that's
unrelated.
On Wed, 5 Aug 2020 at 07:31, Andrew Wetmore wrote:
>
> Hi:
>
> I am part of the Infrastructure team, and am writing to ask whether your
> project is still using the Apache CMS for your pr
Hi:
I am part of the Infrastructure team, and am writing to ask whether your
project is still using the Apache CMS for your project website. As you
know, the CMS is reaching end-of-life, and we need projects to move their
websites onto a different option within the next few weeks.
There are
24 matches
Mail list logo
