You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Dave Fisher <wa...@apache.org> on 2021/06/28 21:44:56 UTC
Working on Refresh of openoffice.apache.org
Hi -
I’ve created a feature branch of the project website at https://github.com/apache/openoffice-project/tree/preview/refresh
I’ve updated it to use the ASF Pelican features as developed for the CMS Migration of www.apache.org and ten project websites just being completed.
One feature that returns is {#elementid} and permalink support.
Intermediate results are here: https://openoffice-refresh.staged.apache.org
I plan to swap from left navigation to top navigation next along with other enhancements.
Feel free to contribute page updates, new pages, and content removals via changes to the ‘feature/refresh’ branch.
I would prefer to discuss your ideas for css, javascript, and layout changes in this thread although I’m going to “Just Do It".
Infra has documentation that starts here: https://infra.apache.org/asf-pelican-gettingstarted.html
Here we are working on a preview branch: https://infra.apache.org/asf-pelican-branches.html
But ask here on this thread as I’ve now worked on 15 pelican websites.
All The Best,
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Working on Refresh of openoffice.apache.org
Posted by Matthias Seidel <ma...@hamburg.de>.
Hi Dave,
Am 28.06.21 um 23:44 schrieb Dave Fisher:
> Hi -
>
> I’ve created a feature branch of the project website at https://github.com/apache/openoffice-project/tree/preview/refresh
Thank you for the ongoing work!
>
> I’ve updated it to use the ASF Pelican features as developed for the CMS Migration of www.apache.org and ten project websites just being completed.
>
> One feature that returns is {#elementid} and permalink support.
>
> Intermediate results are here: https://openoffice-refresh.staged.apache.org
>
> I plan to swap from left navigation to top navigation next along with other enhancements.
I am not sure how top navigation would look like (menubar)? But I will
have a look when it is in feature/refresh.
Regards,
Matthias
>
> Feel free to contribute page updates, new pages, and content removals via changes to the ‘feature/refresh’ branch.
>
> I would prefer to discuss your ideas for css, javascript, and layout changes in this thread although I’m going to “Just Do It".
>
> Infra has documentation that starts here: https://infra.apache.org/asf-pelican-gettingstarted.html
>
> Here we are working on a preview branch: https://infra.apache.org/asf-pelican-branches.html
>
> But ask here on this thread as I’ve now worked on 15 pelican websites.
>
> All The Best,
> Dave
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
Re: Working on Refresh of openoffice.apache.org
Posted by Dave Fisher <wa...@apache.org>.
Top Post.
I’ve created a table of the site pages, menu items, and internal footer links.
https://github.com/apache/openoffice-project/blob/preview/refresh/PAGES.md
There is commentary for some of the pages.
Regards,
Dave
> On Jun 29, 2021, at 9:57 AM, Dave Fisher <wa...@apache.org> wrote:
>
>
>
>> On Jun 29, 2021, at 9:48 AM, Marcus <ma...@wtnet.de> wrote:
>>
>> Am 28.06.21 um 23:44 schrieb Dave Fisher:
>>> I’ve created a feature branch of the project website at https://github.com/apache/openoffice-project/tree/preview/refresh
>>> I’ve updated it to use the ASF Pelican features as developed for the CMS Migration of www.apache.org and ten project websites just being completed.
>>> One feature that returns is {#elementid} and permalink support.
>>> Intermediate results are here: https://openoffice-refresh.staged.apache.org
>>
>> when comparing this with "https://openoffice.apache.org/" I don't see any changes. Are there already changes to be noticed?
>
> The only changes to be noticed is the formatting for the three [TOC]
>
>>
>> Thanks
>>
>>> I plan to swap from left navigation to top navigation next along with other enhancements.
>>
>> That means all links under General, Community, Develoment ... are horizontal links, right?
>
> Yes, and they will collapse to a menu on narrow screens / mobile
>
>>
>> On the example page "https://template.staged.apache.org/" I can see how it can look like. However, we have a lot of links more, so how would it look like for us?
>
> Two things.
>
> (1) That’s a limited sample. Each menu will have however many menu items we want.
> (2) I think we should revisit the menus on a case by case and page by page basis.
>
> We have 46 pages:
> ./orientation/intro-marketing.md
> ./orientation/how-aoo-project-works.md
> ./orientation/intro-doc.md
> ./orientation/decision-making.md
> ./orientation/intro-qa.md
> ./orientation/index.md
> ./orientation/intro-l10n.md
> ./orientation/infrastructure.md
> ./orientation/intro-development.md
> ./orientation/intro-contributing.md
> ./get-involved.md
> ./license.md
> ./style-test.md
> ./mission.md
> ./people.md
> ./press.md
> ./bug-tracking.md
> ./qa.md
> ./source.md
> ./contact.md
> ./mailing-lists.md
> ./website-native.md
> ./privacy.md
> ./community-faqs.md
> ./get-involved-de.md
> ./students.md
> ./contributing-code.md
> ./docs/edit-cms.md
> ./docs/governance/voting.md
> ./docs/governance/consensusBuilding.md
> ./docs/governance/lazyConsensus.md
> ./social.md
> ./svn-basics.md
> ./pmc-faqs.md
> ./website-local.md
> ./native-lang.md
> ./index.md
> ./terms.md
> ./translate.md
> ./list-conduct.md
> ./downloads.md
> ./events.md
> ./get-it-here.md
> ./developer-faqs.md
> ./security.md
> ./trademarks.md
>
> Some of these are obsolete and many could use a review.
>
> We might want to add an “Orientation” menu.
>
> I think my next step is to make a table of the pages.
>
> Regards,
> Dave
>
>>
>> Thanks
>>
>> Marcus
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Working on Refresh of openoffice.apache.org
Posted by Dave Fisher <wa...@apache.org>.
Hi -
The refresh is now completed and merged into the main branch.
I’ll be working on text describing the websites. The README.md is already changed.
Regards,
Dave
> On Jun 30, 2021, at 8:23 PM, Peter Kovacs <pe...@Apache.org> wrote:
>
>
> On 01.07.21 03:11, Dave Fisher wrote:
>>
>>> On Jun 30, 2021, at 3:33 PM, Marcus <ma...@wtnet.de> wrote:
>>>
>>> Am 30.06.21 um 23:47 schrieb Carl Marcum:
>>>> I think it looks great!
>>>> I've tested mobile with Firefox's developer tools and my iPhone 11 with Firefox and that looks great too.
>>> I had a look on my desktop with Firefox and the difference now - compared with the first steps - is increadible.
>>>
>>> The menu / nav now looks more sorted and clear. The menu items are well aligned and personally I don't miss any icons for them.
>>>
>>> Maybe you can reduce the font size and margins a bit as currently less content is fitting on the page than before without the need to scroll.
>> I reduced the base font size from 18px to 16px. Tweaked a lot of other margin related items slightly. I think we now have a website that reads well even on a small iPhone.
>>
>> Unless there are objections I’ll put it in production in my morning tomorrow.
> +1, please go ahead. It looks great to me. My suggestions are only suggestions and taste.
>>
>>>> Thanks for your work on this!
>>> Yes, thanks a lot for making this possible.
>> My pleasure.
>>
>> FYI - We can start one content updates once the new design is in production.
>>
>> Regards,
>> Dave
>>
>>> Marcus
>>>
>>>
>>>
>>>> On 6/30/21 5:13 PM, Dave Fisher wrote:
>>>>> Hi -
>>>>>
>>>>> I like where everything is now. When I run google’s Lightroom tool in a Chrome Incognito window I get scores of 94, 97, 100, and 100.
>>>>>
>>>>>> On Jun 30, 2021, at 1:40 PM, Peter Kovacs <pe...@apache.org> wrote:
>>>>>>
>>>>>>
>>>>>> On 30.06.21 20:17, Dave Fisher wrote:
>>>>>>>> On Jun 30, 2021, at 11:12 AM, Peter Kovacs <pe...@apache.org> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>> On 30.06.21 19:25, Dave Fisher wrote:
>>>>>>>>> I like the look at https://openoffice-refresh.staged.apache.org/. Please review.
>>>>>>>> +1, maybe can we have some icons in front of a menu point? like the ASF feather in front of the ASF?
>>>>>>> The feather in front of “The ASF” is possible.
>>>>>>>
>>>>>>>> And maybe an indication which menu point we currently see. Maybe an arrow? (if you visit the link and you click on General you would see a -> in front of the menu point "About".)
>>>>>>> I’m counting on bootstrap for the nav menus and I don’t think that is at all easy. It would likely require keeping information about what menu a page is part of in the page along with making sure that the page is on the menu.
>>>>>> I thought of something like this pseudocode:
>>>>>>
>>>>>> if (window.location.href = this.dropdown-item.href) then this.css = "selected" else this.css = "unselected"?
>>>>> I get your idea and it could be a way to do it and there is a way to make bootstrap menu items inactive.
>>>>>
>>>>> There may be some issues with the comparison as the window.location.href is fully qualified while we do not want to use fully qualified urls for the dropdown-item hrefs (makes testing the site painful.)
>>>>>
>>>>>> Hmm, bummer seems not that easy.
>>>>>>
>>>>>> So maybe something like:
>>>>>>
>>>>>> const boxes = document....ui.dropdown-menu.show.querySelectorAll('#dropdown-item');
>>>>>>
>>>>>> boxes.forEach(box => {
>>>>>> if (window.location.href = box.dropdown-item.href) then box.css = "selected" else box.css = "unselected"?
>>>>>>
>>>>>> }
>>>>>>
>>>>>> Well something along those lines. I really suck at JS, i just try to write something so you have a better Idea what I thought of. Could well (likely) be this is rubbish.
>>>>>>
>>>>>> So for the pages I tried this approach seem to be pretty neat. Pages that are not listed on the menue, maybe it is the qwuestion where they belong, anyhow.
>>>>> Actually, I would want to learn how to customize Bootstrap 5 first, but I’m not going to do that right now.
>>>>>
>>>>>>>>> There were numerous tweaks needed. The current site did not catch the rename of volunteer@ to recruitment@.
>>>>>>>>>
>>>>>>>>> Unless there are objections I plan to squash & merge after I get the mobile view better.
>>>>>>>> I tried earlier today on my phone and it did look promising already. The Desktop does also look great.
>>>>>>> Do you have an android phone, or iPhone?
>>>>>> I tried from an Android phone. Sony Xperia XA2 and now Samsung S8 to be exact. I use a Firefox browser.
>>>>>>
>>>>>> Now I see a hamburger menu, nice. However the feather makes the menu look unaligned. it is great on the desktop.
>>>>>>
>>>>>> I am not a gui developer so I am not sure what is state of the art on hamburger menus is, but i would intend the other menus, with the goal that the text starts always at same point.
>>>>> IMO the feather is good in the hamburger menu. All of the ASF menu items leave the site.
>>>>>
>>>>> I’m done with UI work for now. It is time to update content. See https://github.com/apache/openoffice-project/blob/preview/refresh/PAGES.md
>>>>>
>>>>> All The Best,
>>>>> Dave
>>>>>
>>>>>>>> I really like the fact that it incorporates the UI approach we are using.
>>>>>>> Thanks!
>>>>>>> Dave
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>
> --
> This is the Way! http://www.apache.org/theapacheway/index.html
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Working on Refresh of openoffice.apache.org
Posted by Peter Kovacs <pe...@apache.org>.
On 01.07.21 03:11, Dave Fisher wrote:
>
>> On Jun 30, 2021, at 3:33 PM, Marcus <ma...@wtnet.de> wrote:
>>
>> Am 30.06.21 um 23:47 schrieb Carl Marcum:
>>> I think it looks great!
>>> I've tested mobile with Firefox's developer tools and my iPhone 11 with Firefox and that looks great too.
>> I had a look on my desktop with Firefox and the difference now - compared with the first steps - is increadible.
>>
>> The menu / nav now looks more sorted and clear. The menu items are well aligned and personally I don't miss any icons for them.
>>
>> Maybe you can reduce the font size and margins a bit as currently less content is fitting on the page than before without the need to scroll.
> I reduced the base font size from 18px to 16px. Tweaked a lot of other margin related items slightly. I think we now have a website that reads well even on a small iPhone.
>
> Unless there are objections I’ll put it in production in my morning tomorrow.
+1, please go ahead. It looks great to me. My suggestions are only
suggestions and taste.
>
>>> Thanks for your work on this!
>> Yes, thanks a lot for making this possible.
> My pleasure.
>
> FYI - We can start one content updates once the new design is in production.
>
> Regards,
> Dave
>
>> Marcus
>>
>>
>>
>>> On 6/30/21 5:13 PM, Dave Fisher wrote:
>>>> Hi -
>>>>
>>>> I like where everything is now. When I run google’s Lightroom tool in a Chrome Incognito window I get scores of 94, 97, 100, and 100.
>>>>
>>>>> On Jun 30, 2021, at 1:40 PM, Peter Kovacs <pe...@apache.org> wrote:
>>>>>
>>>>>
>>>>> On 30.06.21 20:17, Dave Fisher wrote:
>>>>>>> On Jun 30, 2021, at 11:12 AM, Peter Kovacs <pe...@apache.org> wrote:
>>>>>>>
>>>>>>>
>>>>>>> On 30.06.21 19:25, Dave Fisher wrote:
>>>>>>>> I like the look at https://openoffice-refresh.staged.apache.org/. Please review.
>>>>>>> +1, maybe can we have some icons in front of a menu point? like the ASF feather in front of the ASF?
>>>>>> The feather in front of “The ASF” is possible.
>>>>>>
>>>>>>> And maybe an indication which menu point we currently see. Maybe an arrow? (if you visit the link and you click on General you would see a -> in front of the menu point "About".)
>>>>>> I’m counting on bootstrap for the nav menus and I don’t think that is at all easy. It would likely require keeping information about what menu a page is part of in the page along with making sure that the page is on the menu.
>>>>> I thought of something like this pseudocode:
>>>>>
>>>>> if (window.location.href = this.dropdown-item.href) then this.css = "selected" else this.css = "unselected"?
>>>> I get your idea and it could be a way to do it and there is a way to make bootstrap menu items inactive.
>>>>
>>>> There may be some issues with the comparison as the window.location.href is fully qualified while we do not want to use fully qualified urls for the dropdown-item hrefs (makes testing the site painful.)
>>>>
>>>>> Hmm, bummer seems not that easy.
>>>>>
>>>>> So maybe something like:
>>>>>
>>>>> const boxes = document....ui.dropdown-menu.show.querySelectorAll('#dropdown-item');
>>>>>
>>>>> boxes.forEach(box => {
>>>>> if (window.location.href = box.dropdown-item.href) then box.css = "selected" else box.css = "unselected"?
>>>>>
>>>>> }
>>>>>
>>>>> Well something along those lines. I really suck at JS, i just try to write something so you have a better Idea what I thought of. Could well (likely) be this is rubbish.
>>>>>
>>>>> So for the pages I tried this approach seem to be pretty neat. Pages that are not listed on the menue, maybe it is the qwuestion where they belong, anyhow.
>>>> Actually, I would want to learn how to customize Bootstrap 5 first, but I’m not going to do that right now.
>>>>
>>>>>>>> There were numerous tweaks needed. The current site did not catch the rename of volunteer@ to recruitment@.
>>>>>>>>
>>>>>>>> Unless there are objections I plan to squash & merge after I get the mobile view better.
>>>>>>> I tried earlier today on my phone and it did look promising already. The Desktop does also look great.
>>>>>> Do you have an android phone, or iPhone?
>>>>> I tried from an Android phone. Sony Xperia XA2 and now Samsung S8 to be exact. I use a Firefox browser.
>>>>>
>>>>> Now I see a hamburger menu, nice. However the feather makes the menu look unaligned. it is great on the desktop.
>>>>>
>>>>> I am not a gui developer so I am not sure what is state of the art on hamburger menus is, but i would intend the other menus, with the goal that the text starts always at same point.
>>>> IMO the feather is good in the hamburger menu. All of the ASF menu items leave the site.
>>>>
>>>> I’m done with UI work for now. It is time to update content. See https://github.com/apache/openoffice-project/blob/preview/refresh/PAGES.md
>>>>
>>>> All The Best,
>>>> Dave
>>>>
>>>>>>> I really like the fact that it incorporates the UI approach we are using.
>>>>>> Thanks!
>>>>>> Dave
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
--
This is the Way! http://www.apache.org/theapacheway/index.html
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Working on Refresh of openoffice.apache.org
Posted by Dave Fisher <wa...@apache.org>.
> On Jun 30, 2021, at 3:33 PM, Marcus <ma...@wtnet.de> wrote:
>
> Am 30.06.21 um 23:47 schrieb Carl Marcum:
>> I think it looks great!
>> I've tested mobile with Firefox's developer tools and my iPhone 11 with Firefox and that looks great too.
>
> I had a look on my desktop with Firefox and the difference now - compared with the first steps - is increadible.
>
> The menu / nav now looks more sorted and clear. The menu items are well aligned and personally I don't miss any icons for them.
>
> Maybe you can reduce the font size and margins a bit as currently less content is fitting on the page than before without the need to scroll.
I reduced the base font size from 18px to 16px. Tweaked a lot of other margin related items slightly. I think we now have a website that reads well even on a small iPhone.
Unless there are objections I’ll put it in production in my morning tomorrow.
>
>> Thanks for your work on this!
>
> Yes, thanks a lot for making this possible.
My pleasure.
FYI - We can start one content updates once the new design is in production.
Regards,
Dave
>
> Marcus
>
>
>
>> On 6/30/21 5:13 PM, Dave Fisher wrote:
>>> Hi -
>>>
>>> I like where everything is now. When I run google’s Lightroom tool in a Chrome Incognito window I get scores of 94, 97, 100, and 100.
>>>
>>>> On Jun 30, 2021, at 1:40 PM, Peter Kovacs <pe...@apache.org> wrote:
>>>>
>>>>
>>>> On 30.06.21 20:17, Dave Fisher wrote:
>>>>>> On Jun 30, 2021, at 11:12 AM, Peter Kovacs <pe...@apache.org> wrote:
>>>>>>
>>>>>>
>>>>>> On 30.06.21 19:25, Dave Fisher wrote:
>>>>>>> I like the look at https://openoffice-refresh.staged.apache.org/. Please review.
>>>>>> +1, maybe can we have some icons in front of a menu point? like the ASF feather in front of the ASF?
>>>>> The feather in front of “The ASF” is possible.
>>>>>
>>>>>> And maybe an indication which menu point we currently see. Maybe an arrow? (if you visit the link and you click on General you would see a -> in front of the menu point "About".)
>>>>> I’m counting on bootstrap for the nav menus and I don’t think that is at all easy. It would likely require keeping information about what menu a page is part of in the page along with making sure that the page is on the menu.
>>>> I thought of something like this pseudocode:
>>>>
>>>> if (window.location.href = this.dropdown-item.href) then this.css = "selected" else this.css = "unselected"?
>>> I get your idea and it could be a way to do it and there is a way to make bootstrap menu items inactive.
>>>
>>> There may be some issues with the comparison as the window.location.href is fully qualified while we do not want to use fully qualified urls for the dropdown-item hrefs (makes testing the site painful.)
>>>
>>>> Hmm, bummer seems not that easy.
>>>>
>>>> So maybe something like:
>>>>
>>>> const boxes = document....ui.dropdown-menu.show.querySelectorAll('#dropdown-item');
>>>>
>>>> boxes.forEach(box => {
>>>> if (window.location.href = box.dropdown-item.href) then box.css = "selected" else box.css = "unselected"?
>>>>
>>>> }
>>>>
>>>> Well something along those lines. I really suck at JS, i just try to write something so you have a better Idea what I thought of. Could well (likely) be this is rubbish.
>>>>
>>>> So for the pages I tried this approach seem to be pretty neat. Pages that are not listed on the menue, maybe it is the qwuestion where they belong, anyhow.
>>> Actually, I would want to learn how to customize Bootstrap 5 first, but I’m not going to do that right now.
>>>
>>>>>>> There were numerous tweaks needed. The current site did not catch the rename of volunteer@ to recruitment@.
>>>>>>>
>>>>>>> Unless there are objections I plan to squash & merge after I get the mobile view better.
>>>>>> I tried earlier today on my phone and it did look promising already. The Desktop does also look great.
>>>>> Do you have an android phone, or iPhone?
>>>> I tried from an Android phone. Sony Xperia XA2 and now Samsung S8 to be exact. I use a Firefox browser.
>>>>
>>>> Now I see a hamburger menu, nice. However the feather makes the menu look unaligned. it is great on the desktop.
>>>>
>>>> I am not a gui developer so I am not sure what is state of the art on hamburger menus is, but i would intend the other menus, with the goal that the text starts always at same point.
>>> IMO the feather is good in the hamburger menu. All of the ASF menu items leave the site.
>>>
>>> I’m done with UI work for now. It is time to update content. See https://github.com/apache/openoffice-project/blob/preview/refresh/PAGES.md
>>>
>>> All The Best,
>>> Dave
>>>
>>>>>> I really like the fact that it incorporates the UI approach we are using.
>>>>> Thanks!
>>>>> Dave
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Working on Refresh of openoffice.apache.org
Posted by Marcus <ma...@wtnet.de>.
Am 30.06.21 um 23:47 schrieb Carl Marcum:
> I think it looks great!
>
> I've tested mobile with Firefox's developer tools and my iPhone 11 with
> Firefox and that looks great too.
I had a look on my desktop with Firefox and the difference now -
compared with the first steps - is increadible.
The menu / nav now looks more sorted and clear. The menu items are well
aligned and personally I don't miss any icons for them.
Maybe you can reduce the font size and margins a bit as currently less
content is fitting on the page than before without the need to scroll.
> Thanks for your work on this!
Yes, thanks a lot for making this possible.
Marcus
> On 6/30/21 5:13 PM, Dave Fisher wrote:
>> Hi -
>>
>> I like where everything is now. When I run google’s Lightroom tool in
>> a Chrome Incognito window I get scores of 94, 97, 100, and 100.
>>
>>> On Jun 30, 2021, at 1:40 PM, Peter Kovacs <pe...@apache.org> wrote:
>>>
>>>
>>> On 30.06.21 20:17, Dave Fisher wrote:
>>>>> On Jun 30, 2021, at 11:12 AM, Peter Kovacs <pe...@apache.org> wrote:
>>>>>
>>>>>
>>>>> On 30.06.21 19:25, Dave Fisher wrote:
>>>>>> I like the look at https://openoffice-refresh.staged.apache.org/.
>>>>>> Please review.
>>>>> +1, maybe can we have some icons in front of a menu point? like the
>>>>> ASF feather in front of the ASF?
>>>> The feather in front of “The ASF” is possible.
>>>>
>>>>> And maybe an indication which menu point we currently see. Maybe an
>>>>> arrow? (if you visit the link and you click on General you would
>>>>> see a -> in front of the menu point "About".)
>>>> I’m counting on bootstrap for the nav menus and I don’t think that
>>>> is at all easy. It would likely require keeping information about
>>>> what menu a page is part of in the page along with making sure that
>>>> the page is on the menu.
>>> I thought of something like this pseudocode:
>>>
>>> if (window.location.href = this.dropdown-item.href) then this.css =
>>> "selected" else this.css = "unselected"?
>> I get your idea and it could be a way to do it and there is a way to
>> make bootstrap menu items inactive.
>>
>> There may be some issues with the comparison as the
>> window.location.href is fully qualified while we do not want to use
>> fully qualified urls for the dropdown-item hrefs (makes testing the
>> site painful.)
>>
>>> Hmm, bummer seems not that easy.
>>>
>>> So maybe something like:
>>>
>>> const boxes =
>>> document....ui.dropdown-menu.show.querySelectorAll('#dropdown-item');
>>>
>>> boxes.forEach(box => {
>>> if (window.location.href = box.dropdown-item.href) then box.css =
>>> "selected" else box.css = "unselected"?
>>>
>>> }
>>>
>>> Well something along those lines. I really suck at JS, i just try to
>>> write something so you have a better Idea what I thought of. Could
>>> well (likely) be this is rubbish.
>>>
>>> So for the pages I tried this approach seem to be pretty neat. Pages
>>> that are not listed on the menue, maybe it is the qwuestion where
>>> they belong, anyhow.
>> Actually, I would want to learn how to customize Bootstrap 5 first,
>> but I’m not going to do that right now.
>>
>>>>>> There were numerous tweaks needed. The current site did not catch
>>>>>> the rename of volunteer@ to recruitment@.
>>>>>>
>>>>>> Unless there are objections I plan to squash & merge after I get
>>>>>> the mobile view better.
>>>>> I tried earlier today on my phone and it did look promising
>>>>> already. The Desktop does also look great.
>>>> Do you have an android phone, or iPhone?
>>> I tried from an Android phone. Sony Xperia XA2 and now Samsung S8 to
>>> be exact. I use a Firefox browser.
>>>
>>> Now I see a hamburger menu, nice. However the feather makes the menu
>>> look unaligned. it is great on the desktop.
>>>
>>> I am not a gui developer so I am not sure what is state of the art on
>>> hamburger menus is, but i would intend the other menus, with the goal
>>> that the text starts always at same point.
>> IMO the feather is good in the hamburger menu. All of the ASF menu
>> items leave the site.
>>
>> I’m done with UI work for now. It is time to update content. See
>> https://github.com/apache/openoffice-project/blob/preview/refresh/PAGES.md
>>
>>
>> All The Best,
>> Dave
>>
>>>>> I really like the fact that it incorporates the UI approach we are
>>>>> using.
>>>> Thanks!
>>>> Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Working on Refresh of openoffice.apache.org
Posted by Carl Marcum <cm...@apache.org>.
Hi Dave,
I think it looks great!
I've tested mobile with Firefox's developer tools and my iPhone 11 with
Firefox and that looks great too.
Thanks for your work on this!
Best regards,
Carl
On 6/30/21 5:13 PM, Dave Fisher wrote:
> Hi -
>
> I like where everything is now. When I run google’s Lightroom tool in a Chrome Incognito window I get scores of 94, 97, 100, and 100.
>
>> On Jun 30, 2021, at 1:40 PM, Peter Kovacs <pe...@apache.org> wrote:
>>
>>
>> On 30.06.21 20:17, Dave Fisher wrote:
>>>> On Jun 30, 2021, at 11:12 AM, Peter Kovacs <pe...@apache.org> wrote:
>>>>
>>>>
>>>> On 30.06.21 19:25, Dave Fisher wrote:
>>>>> I like the look at https://openoffice-refresh.staged.apache.org/. Please review.
>>>> +1, maybe can we have some icons in front of a menu point? like the ASF feather in front of the ASF?
>>> The feather in front of “The ASF” is possible.
>>>
>>>> And maybe an indication which menu point we currently see. Maybe an arrow? (if you visit the link and you click on General you would see a -> in front of the menu point "About".)
>>> I’m counting on bootstrap for the nav menus and I don’t think that is at all easy. It would likely require keeping information about what menu a page is part of in the page along with making sure that the page is on the menu.
>> I thought of something like this pseudocode:
>>
>> if (window.location.href = this.dropdown-item.href) then this.css = "selected" else this.css = "unselected"?
> I get your idea and it could be a way to do it and there is a way to make bootstrap menu items inactive.
>
> There may be some issues with the comparison as the window.location.href is fully qualified while we do not want to use fully qualified urls for the dropdown-item hrefs (makes testing the site painful.)
>
>> Hmm, bummer seems not that easy.
>>
>> So maybe something like:
>>
>> const boxes = document....ui.dropdown-menu.show.querySelectorAll('#dropdown-item');
>>
>> boxes.forEach(box => {
>> if (window.location.href = box.dropdown-item.href) then box.css = "selected" else box.css = "unselected"?
>>
>> }
>>
>> Well something along those lines. I really suck at JS, i just try to write something so you have a better Idea what I thought of. Could well (likely) be this is rubbish.
>>
>> So for the pages I tried this approach seem to be pretty neat. Pages that are not listed on the menue, maybe it is the qwuestion where they belong, anyhow.
> Actually, I would want to learn how to customize Bootstrap 5 first, but I’m not going to do that right now.
>
>>>>> There were numerous tweaks needed. The current site did not catch the rename of volunteer@ to recruitment@.
>>>>>
>>>>> Unless there are objections I plan to squash & merge after I get the mobile view better.
>>>> I tried earlier today on my phone and it did look promising already. The Desktop does also look great.
>>> Do you have an android phone, or iPhone?
>> I tried from an Android phone. Sony Xperia XA2 and now Samsung S8 to be exact. I use a Firefox browser.
>>
>> Now I see a hamburger menu, nice. However the feather makes the menu look unaligned. it is great on the desktop.
>>
>> I am not a gui developer so I am not sure what is state of the art on hamburger menus is, but i would intend the other menus, with the goal that the text starts always at same point.
> IMO the feather is good in the hamburger menu. All of the ASF menu items leave the site.
>
> I’m done with UI work for now. It is time to update content. See https://github.com/apache/openoffice-project/blob/preview/refresh/PAGES.md
>
> All The Best,
> Dave
>
>>>> I really like the fact that it incorporates the UI approach we are using.
>>> Thanks!
>>> Dave
>>>
>>>> --
>>>> This is the Way! http://www.apache.org/theapacheway/index.html
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>
>> --
>> This is the Way! http://www.apache.org/theapacheway/index.html
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Working on Refresh of openoffice.apache.org
Posted by Dave Fisher <wa...@apache.org>.
Hi -
I like where everything is now. When I run google’s Lightroom tool in a Chrome Incognito window I get scores of 94, 97, 100, and 100.
> On Jun 30, 2021, at 1:40 PM, Peter Kovacs <pe...@apache.org> wrote:
>
>
> On 30.06.21 20:17, Dave Fisher wrote:
>>
>>> On Jun 30, 2021, at 11:12 AM, Peter Kovacs <pe...@apache.org> wrote:
>>>
>>>
>>> On 30.06.21 19:25, Dave Fisher wrote:
>>>> I like the look at https://openoffice-refresh.staged.apache.org/. Please review.
>>> +1, maybe can we have some icons in front of a menu point? like the ASF feather in front of the ASF?
>> The feather in front of “The ASF” is possible.
>>
>>> And maybe an indication which menu point we currently see. Maybe an arrow? (if you visit the link and you click on General you would see a -> in front of the menu point "About".)
>> I’m counting on bootstrap for the nav menus and I don’t think that is at all easy. It would likely require keeping information about what menu a page is part of in the page along with making sure that the page is on the menu.
> I thought of something like this pseudocode:
>
> if (window.location.href = this.dropdown-item.href) then this.css = "selected" else this.css = "unselected"?
I get your idea and it could be a way to do it and there is a way to make bootstrap menu items inactive.
There may be some issues with the comparison as the window.location.href is fully qualified while we do not want to use fully qualified urls for the dropdown-item hrefs (makes testing the site painful.)
>
> Hmm, bummer seems not that easy.
>
> So maybe something like:
>
> const boxes = document....ui.dropdown-menu.show.querySelectorAll('#dropdown-item');
>
> boxes.forEach(box => {
> if (window.location.href = box.dropdown-item.href) then box.css = "selected" else box.css = "unselected"?
>
> }
>
> Well something along those lines. I really suck at JS, i just try to write something so you have a better Idea what I thought of. Could well (likely) be this is rubbish.
>
> So for the pages I tried this approach seem to be pretty neat. Pages that are not listed on the menue, maybe it is the qwuestion where they belong, anyhow.
Actually, I would want to learn how to customize Bootstrap 5 first, but I’m not going to do that right now.
>
>>
>>>> There were numerous tweaks needed. The current site did not catch the rename of volunteer@ to recruitment@.
>>>>
>>>> Unless there are objections I plan to squash & merge after I get the mobile view better.
>>> I tried earlier today on my phone and it did look promising already. The Desktop does also look great.
>> Do you have an android phone, or iPhone?
>
> I tried from an Android phone. Sony Xperia XA2 and now Samsung S8 to be exact. I use a Firefox browser.
>
> Now I see a hamburger menu, nice. However the feather makes the menu look unaligned. it is great on the desktop.
>
> I am not a gui developer so I am not sure what is state of the art on hamburger menus is, but i would intend the other menus, with the goal that the text starts always at same point.
IMO the feather is good in the hamburger menu. All of the ASF menu items leave the site.
I’m done with UI work for now. It is time to update content. See https://github.com/apache/openoffice-project/blob/preview/refresh/PAGES.md
All The Best,
Dave
>
>>
>>> I really like the fact that it incorporates the UI approach we are using.
>> Thanks!
>> Dave
>>
>>>
>>> --
>>> This is the Way! http://www.apache.org/theapacheway/index.html
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>
> --
> This is the Way! http://www.apache.org/theapacheway/index.html
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Working on Refresh of openoffice.apache.org
Posted by Peter Kovacs <pe...@apache.org>.
On 30.06.21 20:17, Dave Fisher wrote:
>
>> On Jun 30, 2021, at 11:12 AM, Peter Kovacs <pe...@apache.org> wrote:
>>
>>
>> On 30.06.21 19:25, Dave Fisher wrote:
>>> I like the look at https://openoffice-refresh.staged.apache.org/. Please review.
>> +1, maybe can we have some icons in front of a menu point? like the ASF feather in front of the ASF?
> The feather in front of “The ASF” is possible.
>
>> And maybe an indication which menu point we currently see. Maybe an arrow? (if you visit the link and you click on General you would see a -> in front of the menu point "About".)
> I’m counting on bootstrap for the nav menus and I don’t think that is at all easy. It would likely require keeping information about what menu a page is part of in the page along with making sure that the page is on the menu.
I thought of something like this pseudocode:
if (window.location.href = this.dropdown-item.href) then this.css =
"selected" else this.css = "unselected"?
Hmm, bummer seems not that easy.
So maybe something like:
const boxes =
document....ui.dropdown-menu.show.querySelectorAll('#dropdown-item');
boxes.forEach(box => {
if (window.location.href = box.dropdown-item.href) then box.css =
"selected" else box.css = "unselected"?
}
Well something along those lines. I really suck at JS, i just try to
write something so you have a better Idea what I thought of. Could well
(likely) be this is rubbish.
So for the pages I tried this approach seem to be pretty neat. Pages
that are not listed on the menue, maybe it is the qwuestion where they
belong, anyhow.
>
>>> There were numerous tweaks needed. The current site did not catch the rename of volunteer@ to recruitment@.
>>>
>>> Unless there are objections I plan to squash & merge after I get the mobile view better.
>> I tried earlier today on my phone and it did look promising already. The Desktop does also look great.
> Do you have an android phone, or iPhone?
I tried from an Android phone. Sony Xperia XA2 and now Samsung S8 to be
exact. I use a Firefox browser.
Now I see a hamburger menu, nice. However the feather makes the menu
look unaligned. it is great on the desktop.
I am not a gui developer so I am not sure what is state of the art on
hamburger menus is, but i would intend the other menus, with the goal
that the text starts always at same point.
>
>> I really like the fact that it incorporates the UI approach we are using.
> Thanks!
> Dave
>
>>
>> --
>> This is the Way! http://www.apache.org/theapacheway/index.html
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
--
This is the Way! http://www.apache.org/theapacheway/index.html
Re: Working on Refresh of openoffice.apache.org
Posted by Dave Fisher <wa...@apache.org>.
> On Jun 30, 2021, at 11:12 AM, Peter Kovacs <pe...@apache.org> wrote:
>
>
> On 30.06.21 19:25, Dave Fisher wrote:
>> I like the look at https://openoffice-refresh.staged.apache.org/. Please review.
>
> +1, maybe can we have some icons in front of a menu point? like the ASF feather in front of the ASF?
The feather in front of “The ASF” is possible.
>
> And maybe an indication which menu point we currently see. Maybe an arrow? (if you visit the link and you click on General you would see a -> in front of the menu point "About".)
I’m counting on bootstrap for the nav menus and I don’t think that is at all easy. It would likely require keeping information about what menu a page is part of in the page along with making sure that the page is on the menu.
>
>>
>> There were numerous tweaks needed. The current site did not catch the rename of volunteer@ to recruitment@.
>>
>> Unless there are objections I plan to squash & merge after I get the mobile view better.
>
> I tried earlier today on my phone and it did look promising already. The Desktop does also look great.
Do you have an android phone, or iPhone?
>
> I really like the fact that it incorporates the UI approach we are using.
Thanks!
Dave
>
>
> --
> This is the Way! http://www.apache.org/theapacheway/index.html
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Working on Refresh of openoffice.apache.org
Posted by Peter Kovacs <pe...@apache.org>.
On 30.06.21 19:25, Dave Fisher wrote:
> I like the look at https://openoffice-refresh.staged.apache.org/. Please review.
+1, maybe can we have some icons in front of a menu point? like the ASF
feather in front of the ASF?
And maybe an indication which menu point we currently see. Maybe an
arrow? (if you visit the link and you click on General you would see a
-> in front of the menu point "About".)
>
> There were numerous tweaks needed. The current site did not catch the rename of volunteer@ to recruitment@.
>
> Unless there are objections I plan to squash & merge after I get the mobile view better.
I tried earlier today on my phone and it did look promising already. The
Desktop does also look great.
I really like the fact that it incorporates the UI approach we are using.
--
This is the Way! http://www.apache.org/theapacheway/index.html
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Working on Refresh of openoffice.apache.org
Posted by Dave Fisher <wa...@apache.org>.
I like the look at https://openoffice-refresh.staged.apache.org/. Please review.
There were numerous tweaks needed. The current site did not catch the rename of volunteer@ to recruitment@.
Unless there are objections I plan to squash & merge after I get the mobile view better.
> On Jun 29, 2021, at 9:35 PM, Dave Fisher <wa...@apache.org> wrote:
>
> Top again.
>
> There is now a top navigation menu on https://openoffice-refresh.staged.apache.org/
>
> To dos:
>
> - Color matching with logo and navigation bar.
Done
> - AOO logo as svg.
Staying with PNG
> - Mobile display scale.
Working on this aspect today.
>
> Then content updates.
>
> Regards,
> Dave
>
>> On Jun 29, 2021, at 3:30 PM, Marcus <ma...@wtnet.de> wrote:
>>
>> Am 29.06.21 um 18:57 schrieb Dave Fisher:
>>>> On Jun 29, 2021, at 9:48 AM, Marcus <ma...@wtnet.de> wrote:
>>>> Am 28.06.21 um 23:44 schrieb Dave Fisher:
>>>>> I’ve created a feature branch of the project website at https://github.com/apache/openoffice-project/tree/preview/refresh
>>>>> I’ve updated it to use the ASF Pelican features as developed for the CMS Migration of www.apache.org and ten project websites just being completed.
>>>>> One feature that returns is {#elementid} and permalink support.
>>>>> Intermediate results are here: https://openoffice-refresh.staged.apache.org
>>>>
>>>> when comparing this with "https://openoffice.apache.org/" I don't see any changes. Are there already changes to be noticed?
>>> The only changes to be noticed is the formatting for the three [TOC]
>>
>> after you last changes I can see now more.
>> In general, the vertical margins between headlines are wider.
>>
>>>> Thanks
>>>>
>>>>> I plan to swap from left navigation to top navigation next along with other enhancements.
>>>>
>>>> That means all links under General, Community, Develoment ... are horizontal links, right?
>>> Yes, and they will collapse to a menu on narrow screens / mobile
>>
>> OK, then the number of items doesn't matter.
>>
>>>> On the example page "https://template.staged.apache.org/" I can see how it can look like. However, we have a lot of links more, so how would it look like for us?
>>> Two things.
>>> (1) That’s a limited sample. Each menu will have however many menu items we want.
>>> (2) I think we should revisit the menus on a case by case and page by page basis.
>>> We have 46 pages:
>>> [...]
>>> Some of these are obsolete and many could use a review.
>>> We might want to add an “Orientation” menu.
>>> I think my next step is to make a table of the pages.
>>
>> Yes, even with only 46 pages an update sounds reasonable.
>>
>> Marcus
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Working on Refresh of openoffice.apache.org
Posted by Dave Fisher <wa...@apache.org>.
Top again.
There is now a top navigation menu on https://openoffice-refresh.staged.apache.org/
To dos:
- Color matching with logo and navigation bar.
- AOO logo as svg.
- Mobile display scale.
Then content updates.
Regards,
Dave
> On Jun 29, 2021, at 3:30 PM, Marcus <ma...@wtnet.de> wrote:
>
> Am 29.06.21 um 18:57 schrieb Dave Fisher:
>>> On Jun 29, 2021, at 9:48 AM, Marcus <ma...@wtnet.de> wrote:
>>> Am 28.06.21 um 23:44 schrieb Dave Fisher:
>>>> I’ve created a feature branch of the project website at https://github.com/apache/openoffice-project/tree/preview/refresh
>>>> I’ve updated it to use the ASF Pelican features as developed for the CMS Migration of www.apache.org and ten project websites just being completed.
>>>> One feature that returns is {#elementid} and permalink support.
>>>> Intermediate results are here: https://openoffice-refresh.staged.apache.org
>>>
>>> when comparing this with "https://openoffice.apache.org/" I don't see any changes. Are there already changes to be noticed?
>> The only changes to be noticed is the formatting for the three [TOC]
>
> after you last changes I can see now more.
> In general, the vertical margins between headlines are wider.
>
>>> Thanks
>>>
>>>> I plan to swap from left navigation to top navigation next along with other enhancements.
>>>
>>> That means all links under General, Community, Develoment ... are horizontal links, right?
>> Yes, and they will collapse to a menu on narrow screens / mobile
>
> OK, then the number of items doesn't matter.
>
>>> On the example page "https://template.staged.apache.org/" I can see how it can look like. However, we have a lot of links more, so how would it look like for us?
>> Two things.
>> (1) That’s a limited sample. Each menu will have however many menu items we want.
>> (2) I think we should revisit the menus on a case by case and page by page basis.
>> We have 46 pages:
>> [...]
>> Some of these are obsolete and many could use a review.
>> We might want to add an “Orientation” menu.
>> I think my next step is to make a table of the pages.
>
> Yes, even with only 46 pages an update sounds reasonable.
>
> Marcus
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Working on Refresh of openoffice.apache.org
Posted by Marcus <ma...@wtnet.de>.
Am 29.06.21 um 18:57 schrieb Dave Fisher:
>> On Jun 29, 2021, at 9:48 AM, Marcus <ma...@wtnet.de> wrote:
>> Am 28.06.21 um 23:44 schrieb Dave Fisher:
>>> I’ve created a feature branch of the project website at https://github.com/apache/openoffice-project/tree/preview/refresh
>>> I’ve updated it to use the ASF Pelican features as developed for the CMS Migration of www.apache.org and ten project websites just being completed.
>>> One feature that returns is {#elementid} and permalink support.
>>> Intermediate results are here: https://openoffice-refresh.staged.apache.org
>>
>> when comparing this with "https://openoffice.apache.org/" I don't see any changes. Are there already changes to be noticed?
>
> The only changes to be noticed is the formatting for the three [TOC]
after you last changes I can see now more.
In general, the vertical margins between headlines are wider.
>> Thanks
>>
>>> I plan to swap from left navigation to top navigation next along with other enhancements.
>>
>> That means all links under General, Community, Develoment ... are horizontal links, right?
>
> Yes, and they will collapse to a menu on narrow screens / mobile
OK, then the number of items doesn't matter.
>> On the example page "https://template.staged.apache.org/" I can see how it can look like. However, we have a lot of links more, so how would it look like for us?
>
> Two things.
>
> (1) That’s a limited sample. Each menu will have however many menu items we want.
> (2) I think we should revisit the menus on a case by case and page by page basis.
>
> We have 46 pages:
> [...]
>
> Some of these are obsolete and many could use a review.
>
> We might want to add an “Orientation” menu.
>
> I think my next step is to make a table of the pages.
Yes, even with only 46 pages an update sounds reasonable.
Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Working on Refresh of openoffice.apache.org
Posted by Dave Fisher <wa...@apache.org>.
> On Jun 29, 2021, at 9:48 AM, Marcus <ma...@wtnet.de> wrote:
>
> Am 28.06.21 um 23:44 schrieb Dave Fisher:
>> I’ve created a feature branch of the project website at https://github.com/apache/openoffice-project/tree/preview/refresh
>> I’ve updated it to use the ASF Pelican features as developed for the CMS Migration of www.apache.org and ten project websites just being completed.
>> One feature that returns is {#elementid} and permalink support.
>> Intermediate results are here: https://openoffice-refresh.staged.apache.org
>
> when comparing this with "https://openoffice.apache.org/" I don't see any changes. Are there already changes to be noticed?
The only changes to be noticed is the formatting for the three [TOC]
>
> Thanks
>
>> I plan to swap from left navigation to top navigation next along with other enhancements.
>
> That means all links under General, Community, Develoment ... are horizontal links, right?
Yes, and they will collapse to a menu on narrow screens / mobile
>
> On the example page "https://template.staged.apache.org/" I can see how it can look like. However, we have a lot of links more, so how would it look like for us?
Two things.
(1) That’s a limited sample. Each menu will have however many menu items we want.
(2) I think we should revisit the menus on a case by case and page by page basis.
We have 46 pages:
./orientation/intro-marketing.md
./orientation/how-aoo-project-works.md
./orientation/intro-doc.md
./orientation/decision-making.md
./orientation/intro-qa.md
./orientation/index.md
./orientation/intro-l10n.md
./orientation/infrastructure.md
./orientation/intro-development.md
./orientation/intro-contributing.md
./get-involved.md
./license.md
./style-test.md
./mission.md
./people.md
./press.md
./bug-tracking.md
./qa.md
./source.md
./contact.md
./mailing-lists.md
./website-native.md
./privacy.md
./community-faqs.md
./get-involved-de.md
./students.md
./contributing-code.md
./docs/edit-cms.md
./docs/governance/voting.md
./docs/governance/consensusBuilding.md
./docs/governance/lazyConsensus.md
./social.md
./svn-basics.md
./pmc-faqs.md
./website-local.md
./native-lang.md
./index.md
./terms.md
./translate.md
./list-conduct.md
./downloads.md
./events.md
./get-it-here.md
./developer-faqs.md
./security.md
./trademarks.md
Some of these are obsolete and many could use a review.
We might want to add an “Orientation” menu.
I think my next step is to make a table of the pages.
Regards,
Dave
>
> Thanks
>
> Marcus
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Working on Refresh of openoffice.apache.org
Posted by Marcus <ma...@wtnet.de>.
Am 28.06.21 um 23:44 schrieb Dave Fisher:
> I’ve created a feature branch of the project website at https://github.com/apache/openoffice-project/tree/preview/refresh
>
> I’ve updated it to use the ASF Pelican features as developed for the CMS Migration of www.apache.org and ten project websites just being completed.
>
> One feature that returns is {#elementid} and permalink support.
>
> Intermediate results are here: https://openoffice-refresh.staged.apache.org
when comparing this with "https://openoffice.apache.org/" I don't see
any changes. Are there already changes to be noticed?
Thanks
> I plan to swap from left navigation to top navigation next along with other enhancements.
That means all links under General, Community, Develoment ... are
horizontal links, right?
On the example page "https://template.staged.apache.org/" I can see how
it can look like. However, we have a lot of links more, so how would it
look like for us?
Thanks
Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org