You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juneau.apache.org by "John D. Ament" <jo...@apache.org> on 2016/07/01 23:48:13 UTC
Juneau website source code
Hey guys
Finally getting some traction on our infra tickets. Is the source code for
the juneau proposed website sitting anywhere? E.g. github or somewhere
else?
Do you happen to have the pre-re-branded website around? If so can you get
a zip together or something?
John
Re: Juneau website source code
Posted by James Bognar <ja...@salesforce.com>.
Let's just start with this for now. It's ugly, but it's a start.
On Sat, Jul 2, 2016 at 12:12 PM, John D. Ament <jo...@apache.org>
wrote:
> On Sat, Jul 2, 2016 at 11:45 AM James Bognar <ja...@salesforce.com>
> wrote:
>
> > We don't really have a pre-made website ready for upload. Here's what
> > we've got...
> >
> > A google site (WYSIWYG) - https://sites.google.com/site/apachejuneau/
>
>
> Would it be possible to get the source code for this, and deploy as is?
> Even as a first step.
>
>
> >
> >
> > Javadocs hosted via gh-pages -
> > http://jamesbognar.github.io/juneau-docs/doc/index.html
>
>
> We can definitely include this.
>
>
> >
> >
> > A getting-started wiki for devs -
> >
> >
> https://github.com/jamesbognar/juneau/wiki/Getting-started-for-Collaborators
>
>
> Do we want to request a wiki? I'm assuming confluence would be OK.
>
>
> >
> >
> > I was actually hoping there would be a template site we could use to get
> > started that would help match the look-and-feel of other Apache projects.
> >
>
> Thats the thing. Apache projects each have their own website, using a wide
> variety of technologies to power them.
>
> We used to have a SVN based CMS. This has been deprecated. If you recall,
> one of the things I was proposing was to leverage gitpubsub for the new
> website. We can deploy some manual static content for now, while working
> on a different build tool. The concept is similar to how github pages
> work. The build tool is therefore arbitrary, sine developers push to a
> branch when their changes are ready. Jekyll is apparently used often in
> this structure.
>
>
> > My general vision was...
> > 1) A sparse website consisting of a quick description and links (similar
> to
> > the existing Google Site).
> > 2) All documentation maintained in Javadocs.
> > 3) Design documents maintained in Wikis.
> >
>
> All three of these sound about right.
>
>
> >
> > Are there any particularly nice webpages for other Apache projects that
> we
> > might be able to steal as a starting point?
> >
>
> I'd personally rather not. Though you may want to reach out to the general
> incubator list, basically with a help wanted on webpage design.
>
>
> >
> >
> > On a side note, I'll be traveling this weekend so I may not respond to
> > emails until late Monday.
> >
> > On Sat, Jul 2, 2016 at 2:42 AM, Jochen Wiedmann <
> jochen.wiedmann@gmail.com
> > >
> > wrote:
> >
> > > On Sat, Jul 2, 2016 at 3:10 AM, Stian Soiland-Reyes <st...@apache.org>
> > > wrote:
> > >
> > > > What publishing mechanism have Juneau decided on? Do you know what
> > > > INFRA offers at the moment?
> > > >
> > > > I believe cms.apache.org is now deprecated.
> > >
> > > I don't recall a decision. However, I take
> > > https://issues.apache.org/jira/browse/INFRA-12171 to mean, that the
> > > site is git based.
> > >
> > > That means, it should be possible to import the existing site with no
> > > problems.
> > >
> > > Jochen
> > >
> > > --
> > > The next time you hear: "Don't reinvent the wheel!"
> > >
> > >
> > >
> >
> http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg
> > >
> >
> >
> >
> > --
> > James Bognar
> >
>
--
James Bognar
Re: Juneau website source code
Posted by "John D. Ament" <jo...@apache.org>.
On Sat, Jul 2, 2016 at 11:45 AM James Bognar <ja...@salesforce.com>
wrote:
> We don't really have a pre-made website ready for upload. Here's what
> we've got...
>
> A google site (WYSIWYG) - https://sites.google.com/site/apachejuneau/
Would it be possible to get the source code for this, and deploy as is?
Even as a first step.
>
>
> Javadocs hosted via gh-pages -
> http://jamesbognar.github.io/juneau-docs/doc/index.html
We can definitely include this.
>
>
> A getting-started wiki for devs -
>
> https://github.com/jamesbognar/juneau/wiki/Getting-started-for-Collaborators
Do we want to request a wiki? I'm assuming confluence would be OK.
>
>
> I was actually hoping there would be a template site we could use to get
> started that would help match the look-and-feel of other Apache projects.
>
Thats the thing. Apache projects each have their own website, using a wide
variety of technologies to power them.
We used to have a SVN based CMS. This has been deprecated. If you recall,
one of the things I was proposing was to leverage gitpubsub for the new
website. We can deploy some manual static content for now, while working
on a different build tool. The concept is similar to how github pages
work. The build tool is therefore arbitrary, sine developers push to a
branch when their changes are ready. Jekyll is apparently used often in
this structure.
> My general vision was...
> 1) A sparse website consisting of a quick description and links (similar to
> the existing Google Site).
> 2) All documentation maintained in Javadocs.
> 3) Design documents maintained in Wikis.
>
All three of these sound about right.
>
> Are there any particularly nice webpages for other Apache projects that we
> might be able to steal as a starting point?
>
I'd personally rather not. Though you may want to reach out to the general
incubator list, basically with a help wanted on webpage design.
>
>
> On a side note, I'll be traveling this weekend so I may not respond to
> emails until late Monday.
>
> On Sat, Jul 2, 2016 at 2:42 AM, Jochen Wiedmann <jochen.wiedmann@gmail.com
> >
> wrote:
>
> > On Sat, Jul 2, 2016 at 3:10 AM, Stian Soiland-Reyes <st...@apache.org>
> > wrote:
> >
> > > What publishing mechanism have Juneau decided on? Do you know what
> > > INFRA offers at the moment?
> > >
> > > I believe cms.apache.org is now deprecated.
> >
> > I don't recall a decision. However, I take
> > https://issues.apache.org/jira/browse/INFRA-12171 to mean, that the
> > site is git based.
> >
> > That means, it should be possible to import the existing site with no
> > problems.
> >
> > Jochen
> >
> > --
> > The next time you hear: "Don't reinvent the wheel!"
> >
> >
> >
> http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg
> >
>
>
>
> --
> James Bognar
>
Re: Juneau website source code
Posted by Jochen Wiedmann <jo...@gmail.com>.
On Sat, Jul 2, 2016 at 5:45 PM, James Bognar
<ja...@salesforce.com> wrote:
> We don't really have a pre-made website ready for upload. Here's what
> we've got...
Looks good to me, except that it should obviously be "Apache Juneau"
now, rather than "Juneau".
Jochen
--
The next time you hear: "Don't reinvent the wheel!"
http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg
Re: Juneau website source code
Posted by James Bognar <ja...@salesforce.com>.
We don't really have a pre-made website ready for upload. Here's what
we've got...
A google site (WYSIWYG) - https://sites.google.com/site/apachejuneau/
Javadocs hosted via gh-pages -
http://jamesbognar.github.io/juneau-docs/doc/index.html
A getting-started wiki for devs -
https://github.com/jamesbognar/juneau/wiki/Getting-started-for-Collaborators
I was actually hoping there would be a template site we could use to get
started that would help match the look-and-feel of other Apache projects.
My general vision was...
1) A sparse website consisting of a quick description and links (similar to
the existing Google Site).
2) All documentation maintained in Javadocs.
3) Design documents maintained in Wikis.
Are there any particularly nice webpages for other Apache projects that we
might be able to steal as a starting point?
On a side note, I'll be traveling this weekend so I may not respond to
emails until late Monday.
On Sat, Jul 2, 2016 at 2:42 AM, Jochen Wiedmann <jo...@gmail.com>
wrote:
> On Sat, Jul 2, 2016 at 3:10 AM, Stian Soiland-Reyes <st...@apache.org>
> wrote:
>
> > What publishing mechanism have Juneau decided on? Do you know what
> > INFRA offers at the moment?
> >
> > I believe cms.apache.org is now deprecated.
>
> I don't recall a decision. However, I take
> https://issues.apache.org/jira/browse/INFRA-12171 to mean, that the
> site is git based.
>
> That means, it should be possible to import the existing site with no
> problems.
>
> Jochen
>
> --
> The next time you hear: "Don't reinvent the wheel!"
>
>
> http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg
>
--
James Bognar
Re: Juneau website source code
Posted by Jochen Wiedmann <jo...@gmail.com>.
On Sat, Jul 2, 2016 at 3:10 AM, Stian Soiland-Reyes <st...@apache.org> wrote:
> What publishing mechanism have Juneau decided on? Do you know what
> INFRA offers at the moment?
>
> I believe cms.apache.org is now deprecated.
I don't recall a decision. However, I take
https://issues.apache.org/jira/browse/INFRA-12171 to mean, that the
site is git based.
That means, it should be possible to import the existing site with no problems.
Jochen
--
The next time you hear: "Don't reinvent the wheel!"
http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg
Re: Juneau website source code
Posted by Stian Soiland-Reyes <st...@apache.org>.
On 2 July 2016 at 00:48, John D. Ament <jo...@apache.org> wrote:
> Finally getting some traction on our infra tickets. Is the source code for
> the juneau proposed website sitting anywhere? E.g. github or somewhere
> else?
What publishing mechanism have Juneau decided on? Do you know what
INFRA offers at the moment?
I believe cms.apache.org is now deprecated.
Many of the new projects use Jekyll, but I think unlike GitHub Pages
that would require running the jekyll manually and then pushing either
with svn or git. A win here is that if you need to do an experiment,
the setup could work also as gh-pages. One potential problem is if
people end up with different versions of Jekyll installed and someone
gets fancy with the features :)
You can also use Maven Site with various templates/styles, which can
then do the git/svn push for you, but might not be as fancy as the
Jekyll. (Still, you can do Markdown!). Less flexibility, but the
advantage here is that you don't need to worry about version
incompatibility and you only need Java to preview/publish.
In both cases it would be good to have it set up so it's easy for
third-parties to contribute fixes to the website, e.g. as GitHub pull
requests.
--
Stian Soiland-Reyes
Apache Taverna (incubating), Apache Commons
http://orcid.org/0000-0001-9842-9718