Hah :)  Thanks Alex!

On Thu, Feb 10, 2011 at 2:35 PM, Alex Salazar <[email protected]> wrote:
> I was thinking of making the whole paragraph an h1. above even the Apache
> Logo :)
>
> Kidding aside, yes it's now at the very bottom of every documentation based
> page.
>
> Alex
>
> On Thu, Feb 10, 2011 at 2:28 PM, Les Hazlewood <[email protected]>wrote:
>
>> My only request is that it goes at the very bottom of each page so as
>> to not interfere with the page content.  I'm assuming that is your
>> intention, but you didn't specify where you would put it, so I thought
>> I'd ask :)
>>
>> Les
>>
>> On Thu, Feb 10, 2011 at 2:09 PM, Alex Salazar <[email protected]>
>> wrote:
>> > Also, it's worth noting that this block is set-up as a separate page in
>> > Confluence so we can edit it one place and avoid having to go to every
>> page
>> > in the wiki.
>> >
>> > Modular programming also works with page content :)
>> >
>> >
>> > On Thu, Feb 10, 2011 at 2:06 PM, Alex Salazar <[email protected]>
>> wrote:
>> >
>> >> Hey folks,
>> >>
>> >> Also, while I'm cleaning up page titles, I'm planning to add the block
>> >> below to each of the documentation pages.  Please let me know if you
>> have
>> >> any comments or thoughts.  Unless I hear otherwise, I will be adding to
>> >> every page in the Documentation tree in the wiki.
>> >>
>> >> Thanks,
>> >>
>> >> Alex
>> >> Lend a hand with documentation
>> >>
>> >> While we hope this documentation helps you with the work you're doing
>> with
>> >> Apache Shiro, it is not a yet a complete guide to all of Shiro's
>> >> functionality. The community is improving and expanding the
>> documentation
>> >> all the time. If you'd like to help the Shiro project, please consider
>> >> writing some documentation where you see a need. Every little bit of
>> help
>> >> you provide expands the community and in turn improves Shiro.
>> >>
>> >> For more information on contributing please check out the How to
>> >> Contribute<
>> https://cwiki.apache.org/confluence/display/SHIRO/How+to+Contribute>
>> >>  page.

Reply via email to