3:14 p.m.
Hi all,
As promised I started work on the new website. After some good experiences with it for the
Arquillian website we decided to use Awestruct for this. This basically allows you to do
some "dynamic" things like templating while the result is still plain HTML.
For the look&feel I used the Bootstrap library. We still have a lot of work to do, but
I did set up the structure of the site. Now it's just adding more and more content.
There are a few things to look at:
1) The front page
It contains a news section which is aggregated from the "news" directory. The
pages within the news directory must have the format of yyyy-MM-dd-post-pagetitle.textile
to be picked up.
2) The documentation page
The documentation pages have their own template which creates the menu structure:
_layouts/docs.html.haml. If a new page is added we need to add it to the menu too (this
can probably be automated).
You can preview the site here: http://jboss-forge.s3.amazonaws.com/index.html and the
sources are on github: https://github.com/forge/website
I will continue adding content myself, but please contribute on this. You can simply send
pull requests on git like always. The most important at this point is to migrate the
documentation.
Paul
5:29 p.m.
Site's not really mobile friendly, FYI.
Sent from my iPhone
On Mar 17, 2012, at 8:14, Paul Bakker <paul.bakker.nl(a)gmail.com> wrote:
Hi all,
As promised I started work on the new website. After some good experiences with it for
the Arquillian website we decided to use Awestruct for this. This basically allows you to
do some "dynamic" things like templating while the result is still plain HTML.
For the look&feel I used the Bootstrap library. We still have a lot of work to do,
but I did set up the structure of the site. Now it's just adding more and more
content.
There are a few things to look at:
1) The front page
It contains a news section which is aggregated from the "news" directory. The
pages within the news directory must have the format of yyyy-MM-dd-post-pagetitle.textile
to be picked up.
2) The documentation page
The documentation pages have their own template which creates the menu structure:
_layouts/docs.html.haml. If a new page is added we need to add it to the menu too (this
can probably be automated).
You can preview the site here: http://jboss-forge.s3.amazonaws.com/index.html and the
sources are on github: https://github.com/forge/website
I will continue adding content myself, but please contribute on this. You can simply send
pull requests on git like always. The most important at this point is to migrate the
documentation.
Paul
_______________________________________________
forge-dev mailing list
forge-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev
1:23 p.m.
Thanks for testing, it should work a lot better now!
Paul
On Mar 17, 2012, at 17:29 , Jason Porter wrote:
Site's not really mobile friendly, FYI.
Sent from my iPhone
On Mar 17, 2012, at 8:14, Paul Bakker <paul.bakker.nl(a)gmail.com> wrote:
> Hi all,
>
> As promised I started work on the new website. After some good experiences with it
for the Arquillian website we decided to use Awestruct for this. This basically allows you
to do some "dynamic" things like templating while the result is still plain
HTML.
> For the look&feel I used the Bootstrap library. We still have a lot of work to
do, but I did set up the structure of the site. Now it's just adding more and more
content.
>
> There are a few things to look at:
> 1) The front page
> It contains a news section which is aggregated from the "news" directory.
The pages within the news directory must have the format of
yyyy-MM-dd-post-pagetitle.textile to be picked up.
>
> 2) The documentation page
> The documentation pages have their own template which creates the menu structure:
_layouts/docs.html.haml. If a new page is added we need to add it to the menu too (this
can probably be automated).
>
> You can preview the site here: http://jboss-forge.s3.amazonaws.com/index.html and the
sources are on github: https://github.com/forge/website
>
> I will continue adding content myself, but please contribute on this. You can simply
send pull requests on git like always. The most important at this point is to migrate the
documentation.
>
> Paul
> _______________________________________________
> forge-dev mailing list
> forge-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
_______________________________________________
forge-dev mailing list
forge-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev
5:22 a.m.
Hey Paul,
Did you start with a fresh Awestruct instance, or did you take things from
Arquillian? I think it would be a good idea to look at what they have done
before we get too far on creating our own. In fact, they have been working
extensively to make their system reusable for many projects!
~Lincoln
On Sun, Mar 18, 2012 at 8:23 AM, Paul Bakker <paul.bakker.nl(a)gmail.com>wrote:
Thanks for testing, it should work a lot better now!
Paul
On Mar 17, 2012, at 17:29 , Jason Porter wrote:
> Site's not really mobile friendly, FYI.
>
> Sent from my iPhone
>
> On Mar 17, 2012, at 8:14, Paul Bakker <paul.bakker.nl(a)gmail.com> wrote:
>
>> Hi all,
>>
>> As promised I started work on the new website. After some good
experiences with it for the Arquillian website we decided to use Awestruct
for this. This basically allows you to do some "dynamic" things like
templating while the result is still plain HTML.
>> For the look&feel I used the Bootstrap library. We still have a lot of
work to do, but I did set up the structure of the site. Now it's just
adding more and more content.
>>
>> There are a few things to look at:
>> 1) The front page
>> It contains a news section which is aggregated from the "news"
directory. The pages within the news directory must have the format of
yyyy-MM-dd-post-pagetitle.textile to be picked up.
>>
>> 2) The documentation page
>> The documentation pages have their own template which creates the menu
structure: _layouts/docs.html.haml. If a new page is added we need to add
it to the menu too (this can probably be automated).
>>
>> You can preview the site here:
http://jboss-forge.s3.amazonaws.com/index.html and the sources are on
github: https://github.com/forge/website
>>
>> I will continue adding content myself, but please contribute on this.
You can simply send pull requests on git like always. The most important at
this point is to migrate the documentation.
>>
>> Paul
>> _______________________________________________
>> forge-dev mailing list
>> forge-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/forge-dev
>
> _______________________________________________
> forge-dev mailing list
> forge-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
_______________________________________________
forge-dev mailing list
forge-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
7:24 a.m.
Started fresh, so we can build it up step by step. They built a bunch of plugins that we
should reuse though.
Sent from my iPhone
On 20 mrt. 2012, at 05:22, "Lincoln Baxter, III" <lincolnbaxter(a)gmail.com>
wrote:
Hey Paul,
Did you start with a fresh Awestruct instance, or did you take things from Arquillian? I
think it would be a good idea to look at what they have done before we get too far on
creating our own. In fact, they have been working extensively to make their system
reusable for many projects!
~Lincoln
On Sun, Mar 18, 2012 at 8:23 AM, Paul Bakker <paul.bakker.nl(a)gmail.com> wrote:
Thanks for testing, it should work a lot better now!
Paul
On Mar 17, 2012, at 17:29 , Jason Porter wrote:
> Site's not really mobile friendly, FYI.
>
> Sent from my iPhone
>
> On Mar 17, 2012, at 8:14, Paul Bakker <paul.bakker.nl(a)gmail.com> wrote:
>
>> Hi all,
>>
>> As promised I started work on the new website. After some good experiences with
it for the Arquillian website we decided to use Awestruct for this. This basically allows
you to do some "dynamic" things like templating while the result is still plain
HTML.
>> For the look&feel I used the Bootstrap library. We still have a lot of work
to do, but I did set up the structure of the site. Now it's just adding more and more
content.
>>
>> There are a few things to look at:
>> 1) The front page
>> It contains a news section which is aggregated from the "news"
directory. The pages within the news directory must have the format of
yyyy-MM-dd-post-pagetitle.textile to be picked up.
>>
>> 2) The documentation page
>> The documentation pages have their own template which creates the menu
structure: _layouts/docs.html.haml. If a new page is added we need to add it to the menu
too (this can probably be automated).
>>
>> You can preview the site here: http://jboss-forge.s3.amazonaws.com/index.html
and the sources are on github: https://github.com/forge/website
>>
>> I will continue adding content myself, but please contribute on this. You can
simply send pull requests on git like always. The most important at this point is to
migrate the documentation.
>>
>> Paul
>> _______________________________________________
>> forge-dev mailing list
>> forge-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/forge-dev
>
> _______________________________________________
> forge-dev mailing list
> forge-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
_______________________________________________
forge-dev mailing list
forge-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
_______________________________________________
forge-dev mailing list
forge-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev
11:57 p.m.
Hey Paul,
I installed awestruct and added a documentation page:
https://docs.jboss.org/author/display/FORGE/Give+your+Plugin+a+name
However, when I go to the documentation index page (
http://localhost:4242/docs/index.html), I don't see my newly added document
in the list on the left. I see an HTML generated
under _site\docs\plugin_development. But nothing refers to it.
Do I miss something? I've attached my textile file.
Thanks,
Ivan
On Tue, Mar 20, 2012 at 8:24 AM, Paul Bakker <paul.bakker.nl(a)gmail.com>wrote:
Started fresh, so we can build it up step by step. They built a bunch
of
plugins that we should reuse though.
Sent from my iPhone
On 20 mrt. 2012, at 05:22, "Lincoln Baxter, III"
<lincolnbaxter(a)gmail.com>
wrote:
Hey Paul,
Did you start with a fresh Awestruct instance, or did you take things from
Arquillian? I think it would be a good idea to look at what they have done
before we get too far on creating our own. In fact, they have been working
extensively to make their system reusable for many projects!
~Lincoln
On Sun, Mar 18, 2012 at 8:23 AM, Paul Bakker <paul.bakker.nl(a)gmail.com>wrote:
> Thanks for testing, it should work a lot better now!
>
> Paul
>
> On Mar 17, 2012, at 17:29 , Jason Porter wrote:
>
> > Site's not really mobile friendly, FYI.
> >
> > Sent from my iPhone
> >
> > On Mar 17, 2012, at 8:14, Paul Bakker <paul.bakker.nl(a)gmail.com> wrote:
> >
> >> Hi all,
> >>
> >> As promised I started work on the new website. After some good
> experiences with it for the Arquillian website we decided to use Awestruct
> for this. This basically allows you to do some "dynamic" things like
> templating while the result is still plain HTML.
> >> For the look&feel I used the Bootstrap library. We still have a lot of
> work to do, but I did set up the structure of the site. Now it's just
> adding more and more content.
> >>
> >> There are a few things to look at:
> >> 1) The front page
> >> It contains a news section which is aggregated from the "news"
> directory. The pages within the news directory must have the format of
> yyyy-MM-dd-post-pagetitle.textile to be picked up.
> >>
> >> 2) The documentation page
> >> The documentation pages have their own template which creates the menu
> structure: _layouts/docs.html.haml. If a new page is added we need to add
> it to the menu too (this can probably be automated).
> >>
> >> You can preview the site here:
> http://jboss-forge.s3.amazonaws.com/index.html and the sources are on
> github: https://github.com/forge/website
> >>
> >> I will continue adding content myself, but please contribute on this.
> You can simply send pull requests on git like always. The most important at
> this point is to migrate the documentation.
> >>
> >> Paul
> >> _______________________________________________
> >> forge-dev mailing list
> >> forge-dev(a)lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/forge-dev
> >
> > _______________________________________________
> > forge-dev mailing list
> > forge-dev(a)lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/forge-dev
>
>
> _______________________________________________
> forge-dev mailing list
> forge-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
>
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
_______________________________________________
forge-dev mailing list
forge-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev
_______________________________________________
forge-dev mailing list
forge-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev
6:41 a.m.
Hi Ivan,
Thanks for helping on the site!
The Textile file looks ok. For some changes you have to force Awestruct to re-generate the
site. In this case it doesn't regenerate the index page because it is unchanged
itself. Remove the _site directory and restart Awestruct to make sure everything is
generated.
Paul
On Apr 2, 2012, at 23:57 , Ivan St. Ivanov wrote:
Hey Paul,
I installed awestruct and added a documentation page:
https://docs.jboss.org/author/display/FORGE/Give+your+Plugin+a+name
However, when I go to the documentation index page
(http://localhost:4242/docs/index.html), I don't see my newly added document in the
list on the left. I see an HTML generated under _site\docs\plugin_development. But nothing
refers to it.
Do I miss something? I've attached my textile file.
Thanks,
Ivan
On Tue, Mar 20, 2012 at 8:24 AM, Paul Bakker <paul.bakker.nl(a)gmail.com> wrote:
Started fresh, so we can build it up step by step. They built a bunch of plugins that we
should reuse though.
Sent from my iPhone
On 20 mrt. 2012, at 05:22, "Lincoln Baxter, III"
<lincolnbaxter(a)gmail.com> wrote:
> Hey Paul,
>
> Did you start with a fresh Awestruct instance, or did you take things from
Arquillian? I think it would be a good idea to look at what they have done before we get
too far on creating our own. In fact, they have been working extensively to make their
system reusable for many projects!
>
> ~Lincoln
>
> On Sun, Mar 18, 2012 at 8:23 AM, Paul Bakker <paul.bakker.nl(a)gmail.com> wrote:
> Thanks for testing, it should work a lot better now!
>
> Paul
>
> On Mar 17, 2012, at 17:29 , Jason Porter wrote:
>
> > Site's not really mobile friendly, FYI.
> >
> > Sent from my iPhone
> >
> > On Mar 17, 2012, at 8:14, Paul Bakker <paul.bakker.nl(a)gmail.com> wrote:
> >
> >> Hi all,
> >>
> >> As promised I started work on the new website. After some good experiences
with it for the Arquillian website we decided to use Awestruct for this. This basically
allows you to do some "dynamic" things like templating while the result is still
plain HTML.
> >> For the look&feel I used the Bootstrap library. We still have a lot of
work to do, but I did set up the structure of the site. Now it's just adding more and
more content.
> >>
> >> There are a few things to look at:
> >> 1) The front page
> >> It contains a news section which is aggregated from the "news"
directory. The pages within the news directory must have the format of
yyyy-MM-dd-post-pagetitle.textile to be picked up.
> >>
> >> 2) The documentation page
> >> The documentation pages have their own template which creates the menu
structure: _layouts/docs.html.haml. If a new page is added we need to add it to the menu
too (this can probably be automated).
> >>
> >> You can preview the site here:
http://jboss-forge.s3.amazonaws.com/index.html and the sources are on github:
https://github.com/forge/website
> >>
> >> I will continue adding content myself, but please contribute on this. You
can simply send pull requests on git like always. The most important at this point is to
migrate the documentation.
> >>
> >> Paul
> >> _______________________________________________
> >> forge-dev mailing list
> >> forge-dev(a)lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/forge-dev
> >
> > _______________________________________________
> > forge-dev mailing list
> > forge-dev(a)lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/forge-dev
>
>
> _______________________________________________
> forge-dev mailing list
> forge-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
>
>
>
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
> _______________________________________________
> forge-dev mailing list
> forge-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
_______________________________________________
forge-dev mailing list
forge-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev
<give-your-plugin-name.textile>_______________________________________________
forge-dev mailing list
forge-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev
9:55 p.m.
Awesome! Maybe that should go in the Awestruct FAQ on our quickstart.
On Tue, Apr 3, 2012 at 12:41 AM, Paul Bakker <paul.bakker.nl(a)gmail.com>wrote:
Hi Ivan,
Thanks for helping on the site!
The Textile file looks ok. For some changes you have to force Awestruct to
re-generate the site. In this case it doesn't regenerate the index page
because it is unchanged itself. Remove the _site directory and restart
Awestruct to make sure everything is generated.
Paul
On Apr 2, 2012, at 23:57 , Ivan St. Ivanov wrote:
Hey Paul,
I installed awestruct and added a documentation page:
https://docs.jboss.org/author/display/FORGE/Give+your+Plugin+a+name
However, when I go to the documentation index page (
http://localhost:4242/docs/index.html), I don't see my newly added
document in the list on the left. I see an HTML generated
under _site\docs\plugin_development. But nothing refers to it.
Do I miss something? I've attached my textile file.
Thanks,
Ivan
On Tue, Mar 20, 2012 at 8:24 AM, Paul Bakker <paul.bakker.nl(a)gmail.com>wrote:
> Started fresh, so we can build it up step by step. They built a bunch of
> plugins that we should reuse though.
>
> Sent from my iPhone
>
> On 20 mrt. 2012, at 05:22, "Lincoln Baxter, III"
<lincolnbaxter(a)gmail.com>
> wrote:
>
> Hey Paul,
>
> Did you start with a fresh Awestruct instance, or did you take things
> from Arquillian? I think it would be a good idea to look at what they have
> done before we get too far on creating our own. In fact, they have been
> working extensively to make their system reusable for many projects!
>
> ~Lincoln
>
> On Sun, Mar 18, 2012 at 8:23 AM, Paul Bakker <paul.bakker.nl(a)gmail.com>wrote:
>
>> Thanks for testing, it should work a lot better now!
>>
>> Paul
>>
>> On Mar 17, 2012, at 17:29 , Jason Porter wrote:
>>
>> > Site's not really mobile friendly, FYI.
>> >
>> > Sent from my iPhone
>> >
>> > On Mar 17, 2012, at 8:14, Paul Bakker <paul.bakker.nl(a)gmail.com>
>> wrote:
>> >
>> >> Hi all,
>> >>
>> >> As promised I started work on the new website. After some good
>> experiences with it for the Arquillian website we decided to use Awestruct
>> for this. This basically allows you to do some "dynamic" things like
>> templating while the result is still plain HTML.
>> >> For the look&feel I used the Bootstrap library. We still have a lot
>> of work to do, but I did set up the structure of the site. Now it's just
>> adding more and more content.
>> >>
>> >> There are a few things to look at:
>> >> 1) The front page
>> >> It contains a news section which is aggregated from the
"news"
>> directory. The pages within the news directory must have the format of
>> yyyy-MM-dd-post-pagetitle.textile to be picked up.
>> >>
>> >> 2) The documentation page
>> >> The documentation pages have their own template which creates the
>> menu structure: _layouts/docs.html.haml. If a new page is added we need to
>> add it to the menu too (this can probably be automated).
>> >>
>> >> You can preview the site here:
>> http://jboss-forge.s3.amazonaws.com/index.html and the sources are on
>> github: https://github.com/forge/website
>> >>
>> >> I will continue adding content myself, but please contribute on this.
>> You can simply send pull requests on git like always. The most important at
>> this point is to migrate the documentation.
>> >>
>> >> Paul
>> >> _______________________________________________
>> >> forge-dev mailing list
>> >> forge-dev(a)lists.jboss.org
>> >> https://lists.jboss.org/mailman/listinfo/forge-dev
>> >
>> > _______________________________________________
>> > forge-dev mailing list
>> > forge-dev(a)lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/forge-dev
>>
>>
>> _______________________________________________
>> forge-dev mailing list
>> forge-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/forge-dev
>>
>
>
>
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
>
> _______________________________________________
> forge-dev mailing list
> forge-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
>
>
> _______________________________________________
> forge-dev mailing list
> forge-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
>
>
<give-your-plugin-name.textile>
_______________________________________________
forge-dev mailing list
forge-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev
_______________________________________________
forge-dev mailing list
forge-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
11:47 p.m.
Yes, sounds fine. I have also something for setting up Awestruct on
Windows. Before you install the Awestruct gem, you need to install DevKit,
as described here:
https://github.com/oneclick/rubyinstaller/wiki/Development-Kit. This worked
out of the box with Ruby, but not with JRuby (to be honest, I didn't spend
too much time to research why).
I have some questions about Textile. Do you know how I can escape a
character? For example -- is translated into dash. However, I want exactly
double hyphen and not dash. Is there a way to escape the translation?
Backslash doesn't help.
Is there also something that corresponds to the wiki's tip tag? The closest
I found was bq, but i don't really want to quote someone, I rather want to
provide a tip.
Cheers,
Ivan
On Tue, Apr 3, 2012 at 10:55 PM, Lincoln Baxter, III <
lincolnbaxter(a)gmail.com> wrote:
Awesome! Maybe that should go in the Awestruct FAQ on our
quickstart.
On Tue, Apr 3, 2012 at 12:41 AM, Paul Bakker <paul.bakker.nl(a)gmail.com>wrote:
> Hi Ivan,
>
> Thanks for helping on the site!
> The Textile file looks ok. For some changes you have to force Awestruct
> to re-generate the site. In this case it doesn't regenerate the index page
> because it is unchanged itself. Remove the _site directory and restart
> Awestruct to make sure everything is generated.
>
> Paul
>
> On Apr 2, 2012, at 23:57 , Ivan St. Ivanov wrote:
>
> Hey Paul,
>
> I installed awestruct and added a documentation page:
> https://docs.jboss.org/author/display/FORGE/Give+your+Plugin+a+name
>
> However, when I go to the documentation index page (
> http://localhost:4242/docs/index.html), I don't see my newly added
> document in the list on the left. I see an HTML generated
> under _site\docs\plugin_development. But nothing refers to it.
>
> Do I miss something? I've attached my textile file.
>
> Thanks,
> Ivan
>
> On Tue, Mar 20, 2012 at 8:24 AM, Paul Bakker <paul.bakker.nl(a)gmail.com>wrote:
>
>> Started fresh, so we can build it up step by step. They built a bunch of
>> plugins that we should reuse though.
>>
>> Sent from my iPhone
>>
>> On 20 mrt. 2012, at 05:22, "Lincoln Baxter, III" <
>> lincolnbaxter(a)gmail.com> wrote:
>>
>> Hey Paul,
>>
>> Did you start with a fresh Awestruct instance, or did you take things
>> from Arquillian? I think it would be a good idea to look at what they have
>> done before we get too far on creating our own. In fact, they have been
>> working extensively to make their system reusable for many projects!
>>
>> ~Lincoln
>>
>> On Sun, Mar 18, 2012 at 8:23 AM, Paul Bakker
<paul.bakker.nl(a)gmail.com>wrote:
>>
>>> Thanks for testing, it should work a lot better now!
>>>
>>> Paul
>>>
>>> On Mar 17, 2012, at 17:29 , Jason Porter wrote:
>>>
>>> > Site's not really mobile friendly, FYI.
>>> >
>>> > Sent from my iPhone
>>> >
>>> > On Mar 17, 2012, at 8:14, Paul Bakker <paul.bakker.nl(a)gmail.com>
>>> wrote:
>>> >
>>> >> Hi all,
>>> >>
>>> >> As promised I started work on the new website. After some good
>>> experiences with it for the Arquillian website we decided to use Awestruct
>>> for this. This basically allows you to do some "dynamic" things
like
>>> templating while the result is still plain HTML.
>>> >> For the look&feel I used the Bootstrap library. We still have a
lot
>>> of work to do, but I did set up the structure of the site. Now it's just
>>> adding more and more content.
>>> >>
>>> >> There are a few things to look at:
>>> >> 1) The front page
>>> >> It contains a news section which is aggregated from the
"news"
>>> directory. The pages within the news directory must have the format of
>>> yyyy-MM-dd-post-pagetitle.textile to be picked up.
>>> >>
>>> >> 2) The documentation page
>>> >> The documentation pages have their own template which creates the
>>> menu structure: _layouts/docs.html.haml. If a new page is added we need to
>>> add it to the menu too (this can probably be automated).
>>> >>
>>> >> You can preview the site here:
>>> http://jboss-forge.s3.amazonaws.com/index.html and the sources are on
>>> github: https://github.com/forge/website
>>> >>
>>> >> I will continue adding content myself, but please contribute on
>>> this. You can simply send pull requests on git like always. The most
>>> important at this point is to migrate the documentation.
>>> >>
>>> >> Paul
>>> >> _______________________________________________
>>> >> forge-dev mailing list
>>> >> forge-dev(a)lists.jboss.org
>>> >> https://lists.jboss.org/mailman/listinfo/forge-dev
>>> >
>>> > _______________________________________________
>>> > forge-dev mailing list
>>> > forge-dev(a)lists.jboss.org
>>> > https://lists.jboss.org/mailman/listinfo/forge-dev
>>>
>>>
>>> _______________________________________________
>>> forge-dev mailing list
>>> forge-dev(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/forge-dev
>>>
>>
>>
>>
>> --
>> Lincoln Baxter, III
>> http://ocpsoft.org
>> "Simpler is better."
>>
>> _______________________________________________
>> forge-dev mailing list
>> forge-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/forge-dev
>>
>>
>> _______________________________________________
>> forge-dev mailing list
>> forge-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/forge-dev
>>
>>
> <give-your-plugin-name.textile>
> _______________________________________________
>
> forge-dev mailing list
> forge-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
>
>
>
> _______________________________________________
> forge-dev mailing list
> forge-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
>
>
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
_______________________________________________
forge-dev mailing list
forge-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev
4399
days inactive
4416
days old
8 comments
4 participants
participants (4)
-
Ivan St. Ivanov -
Jason Porter -
Lincoln Baxter, III -
Paul Bakker