You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Dave Brondsema <da...@brondsema.net> on 2003/11/25 22:04:43 UTC
website updates
AFAICT, the forrest website has not been updated lately. Can this be
done? There have been changes to the FAQ, for example, that don't do much
good if they're only on the forrestbot site.
Additionally, I will start documenting to the new forrestbot soon, but
obviously we don't want that to appear on the public site yet. I propose
that the public website use a cvs tag, like 'publish' to pull the correct
documents. In this way, most documents can be updated and 'publish'ed and
seen on the web relatively soon and documentation that is still under
development can be hidden from the public site.
--
Dave Brondsema
dave@brondsema.net
http://www.brondsema.net - personal
http://www.splike.com - programming
http://csx.calvin.edu - Calvin club
Re: website updates
Posted by David Crossley <cr...@indexgeo.com.au>.
Here are some quick notes to get you going. (...in a rush today.)
Use forrest-0.5 and build Forrest docs as usual.
'cvs checkout xml-site/targets/forrest'
copy stuff from xml-forrest/build/site to xml-site/targets/forrest
'cvs add' any new files.
cvs commit xml-site/targets/forrest
There is a cron job on minotaur (= cvs.apache.org = www.apache,org)
as 'rubys' that does a cvs checkout into /www/xml.apache.org/forrest/
... I think that this happens every six hours.
Done.
If you need to do an urgent update, then you can do:
ssh cvs.apache.org
cd /www/xml.apache.org/forrest/
... ensure 'umask 0002' to make files group writable
cvs update -Pd
... see the Cocoon Wiki page for guidance
http://wiki.cocoondev.org/Wiki.jsp?page=CocoonWebsiteUpdate
--David
Re: website updates
Posted by Dave Brondsema <da...@brondsema.net>.
Quoting David Crossley <cr...@indexgeo.com.au>:
> Dave Brondsema wrote:
> > AFAICT, the forrest website has not been updated lately.
> > Can this be done?
>
> Yes, it can be done. Do you know how? I can explain if you
> do not know. At one stage i think that we had the forrestbot
> doing it automatically, but AFAICT it is not happening now.
No, I don't know how.
> I do not have a problem with us publishing docs that are under
> development - just put a Warning notice at the top.
>
> I suppose that you want to update the current "forrestbot.html"
> and friends to reflect the new forrestbot, yet we still need to
> keep the docs about the old forrestbot for the meantime. Is that
> the dilemma? Perhaps we could just copy the current doc to say
> "forrestbot-old.html" and make some links and notices.
>
Good idea; I will do that.
--
Dave Brondsema
dave@brondsema.net
http://www.brondsema.net - personal
http://www.splike.com - programming
http://csx.calvin.edu - student org
Re: website updates
Posted by David Crossley <cr...@indexgeo.com.au>.
Dave Brondsema wrote:
> AFAICT, the forrest website has not been updated lately.
> Can this be done?
Yes, it can be done. Do you know how? I can explain if you
do not know. At one stage i think that we had the forrestbot
doing it automatically, but AFAICT it is not happening now.
I see discussions happening on various Apache mailing lists
(especially infrastructure@) about ways to automate and stage
the publishing. A few of us should participate there.
In the meantime there is a way that we can semi-automate
our website publish. Some projects have a cron job on
www.apache.org that does the final 'cvs update'. You can see
an example in my home bin directory. Actually, i just
investigated further and see that Sam Ruby (rubys) has one of
these for Forrest. So all that we should need is to cvs commit
our built html/pdf into the xml-site/targets/forrest module.
> There have been changes to the FAQ, for example, that
> don't do much good if they're only on the forrestbot site.
I have been updating certain pages one-by-one as needed.
The FAQ was done recently (Nov 22), so that was a poor example,
but i do get your drift.
> Additionally, I will start documenting to the new forrestbot soon, but
> obviously we don't want that to appear on the public site yet. I propose
> that the public website use a cvs tag, like 'publish' to pull the correct
> documents. In this way, most documents can be updated and 'publish'ed and
> seen on the web relatively soon and documentation that is still under
> development can be hidden from the public site.
The trouble with cvs tags is that people forget to update them.
I do not have a problem with us publishing docs that are under
development - just put a Warning notice at the top.
I suppose that you want to update the current "forrestbot.html"
and friends to reflect the new forrestbot, yet we still need to
keep the docs about the old forrestbot for the meantime. Is that
the dilemma? Perhaps we could just copy the current doc to say
"forrestbot-old.html" and make some links and notices.
--David
Different hostname for a TAB
Posted by Clay Leeds <cl...@medata.com>.
DISCLAIMER: I hope I'm using the correct terminology.
I want to have the tabs at the top of my Forrest web site to go to
different hostnames. They will all be based off of Forrest, although
they may have different "colors" based on which "tab" is selected.
The tabs will lolok like this (best viewed w/ monospace-font):
________ ________ _______
| Medata | Upload | Store |
================================
When "Medata" is selected (as above) the browser will be surfing
<http://www.medata.com/>. When "Upload" is selected (as below), the
browser will be surfing <https://upload.medata.com/>, and the tabs will
look like something this:
________ ________ _______
| Medata | Upload | Store |
========== ========================
When "Store" is selected (as below), the browser will be surfing
<https://stote.medata.com/>, and the tabs will look like something
this:
________ ________ _______
| Medata | Upload | Store |
=================== ================
Is this currently possible with Forrest? Any ideas are appreciated.
Thanks!
--
Clay Leeds - cleeds@medata.com
Web Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>