<!-- 
RSS generated by JIRA (1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d) at Thu Feb 08 23:07:49 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary add field=key&field=summary to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>FOLIO Jira</title>
    <link>https://folio-org.atlassian.net</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>1001.0.0-SNAPSHOT</version>
        <build-number>100246</build-number>
        <build-date>07-02-2024</build-date>
    </build-info>

<item>
            <title>[FOLIO-714] Utilise the FOLIO Common Top Navigation Bar for dev.f.o</title>
                <link>https://folio-org.atlassian.net/browse/FOLIO-714</link>
                <project id="10290" key="FOLIO">FOLIO</project>
                    <description>&lt;p&gt;FOLIO partners agreed on a top navigation bar for the site.  The partners would like dev.folio.org to use the common top navigation bar so that dev.folio.org aligns with the rest of the FOLIO site.&lt;/p&gt;
</description>
                <environment></environment>
        <key id="80334">FOLIO-714</key>
            <summary>Utilise the FOLIO Common Top Navigation Bar for dev.f.o</summary>
                <type id="10003" iconUrl="https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium">Task</type>
                                            <priority id="10002" iconUrl="https://dev.folio.org/assets/jira-priority/jira-p3.svg">P3</priority>
                        <status id="6" iconUrl="https://folio-org.atlassian.net/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10003">Done</resolution>
                                                        <assignee accountid="-1">Unassigned</assignee>
                                                                <reporter accountid="5af5ea1ed95cfc55bfb76c8d">Patricia DeStefano</reporter>
                                    <labels>
                            <label>devweb</label>
                    </labels>
                <created>Wed, 12 Jul 2017 19:02:46 +0000</created>
                <updated>Mon, 12 Nov 2018 14:23:38 +0000</updated>
                            <resolved>Wed, 2 May 2018 15:13:14 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                    <timespent seconds="111600">3 days, 7 hours</timespent>
                                <comments>
                                                            <comment id="188767" author="5af5ea1ed95cfc55bfb76c8d" created="Wed, 12 Jul 2017 19:04:43 +0000"  >&lt;p&gt;Investigating how to implement the common navigation bar using Jekyll.&lt;/p&gt;</comment>
                                                            <comment id="188769" author="5af5ea1ed95cfc55bfb76c8d" created="Wed, 13 Sep 2017 20:05:36 +0000"  >&lt;p&gt;The EBSCO marketing web team and other partners had further recommendations for the top common navigation bar.  I have attached the latest v1 design.  I am changing the POC that I am working on to accommodate the changes.&lt;/p&gt;</comment>
                                                            <comment id="188771" author="61cd0ca0bce5e00069e98be7" created="Thu, 16 Nov 2017 19:46:51 +0000"  >&lt;p&gt;Copied and attached the new topnav-20171116.png from 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-817&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-817&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Investigate another jekyll theme&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            FOLIO-817
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
&lt;/p&gt;</comment>
                                                            <comment id="188772" author="61cd0ca0bce5e00069e98be7" created="Wed, 4 Apr 2018 01:55:41 +0000"  >&lt;p&gt;(Connecting comments.) There is a revised top navigation bar shown today in 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-817&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-817&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Investigate another jekyll theme&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            FOLIO-817
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
.&lt;/p&gt;</comment>
                                                            <comment id="188774" author="61cd0ca0bce5e00069e98be7" created="Fri, 6 Apr 2018 15:09:45 +0000"  >&lt;p&gt;There is a great suggestion from &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ced27478b03050f27825a93&quot; class=&quot;user-hover&quot; rel=&quot;5ced27478b03050f27825a93&quot; data-account-id=&quot;5ced27478b03050f27825a93&quot; accountid=&quot;5ced27478b03050f27825a93&quot; rel=&quot;noreferrer&quot;&gt;Peter Murray&lt;/a&gt; in 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-817&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-817&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Investigate another jekyll theme&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            FOLIO-817
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
 to provide a completely stand-alone common FOLIO navbar to address this need.&lt;/p&gt;

&lt;p&gt;There is also a branch &lt;a href=&quot;https://github.com/folio-org/folio-org.github.io/tree/FOLIO-714-standalone-navbar&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;FOLIO-714-standalone-navbar&lt;/a&gt; (see &lt;a href=&quot;http://folio-714-standalone-navbar.dev.folio.org.s3-website-us-east-1.amazonaws.com&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;demo&lt;/a&gt; which is based on the current master of the site.&lt;/p&gt;

&lt;p&gt;It uses a semi-standalone navbar, to ensure that this theme&apos;s structure can accommodate it. &lt;/p&gt;

&lt;p&gt;(Of course this demo still uses the CSS-only mechanisms of this site&apos;s theme, so it is not really stand-alone, and it is still connected to the rest of the menu structure.)&lt;/p&gt;

&lt;p&gt;So when a truly stand-alone common FOLIO navbar is developed for the other sites and wiki, then we can slot that in.&lt;/p&gt;</comment>
                                                            <comment id="188776" author="5af5ea1ed95cfc55bfb76c8d" created="Tue, 10 Apr 2018 21:05:41 +0000"  >&lt;p&gt;I think that anything that changes the look and feel of the latest top nav described in 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-817&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-817&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Investigate another jekyll theme&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            FOLIO-817
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
 would have to be run by &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ced27478b03050f27825a93&quot; class=&quot;user-hover&quot; rel=&quot;5ced27478b03050f27825a93&quot; data-account-id=&quot;5ced27478b03050f27825a93&quot; accountid=&quot;5ced27478b03050f27825a93&quot; rel=&quot;noreferrer&quot;&gt;Peter Murray&lt;/a&gt;, &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af9cc1bd1d9445cd3a5faba&quot; class=&quot;user-hover&quot; rel=&quot;5af9cc1bd1d9445cd3a5faba&quot; data-account-id=&quot;5af9cc1bd1d9445cd3a5faba&quot; accountid=&quot;5af9cc1bd1d9445cd3a5faba&quot; rel=&quot;noreferrer&quot;&gt;Rachel Fadlon&lt;/a&gt; and Rachel&apos;s team to verify alignment with the general FOLIO group.  The one thing that worries me about a new standalone nav bar is the responsive behavior.  Guessing the demo above is not finished yet, but the responsive behavior does not work yet.  You could probably get the styling to align with a standalone bar, but the responsive behavior would also need to be considered.  Also, giving up reliable, responsive behavior from a known bar for a newly developed bar should be considered.  Just a thought, but if you are looking for a deliverable in between, you could style the issues, discuss and wiki site purple, add the bee &amp;amp; match fonts to make the transition similar and use the bootstrap bar on the dev site.  I can check with Harry as well.  He is traveling, but I will run it by him. &lt;/p&gt;</comment>
                                                            <comment id="188778" author="61cd0ca0bce5e00069e98be7" created="Wed, 11 Apr 2018 02:40:49 +0000"  >&lt;p&gt;As said in my previous comment, that demo was just to ensure that a truly standalone navbar could potentially be added. Yes it would need to handle its own responsiveness, and that could be difficult.&lt;/p&gt;

&lt;p&gt;I have removed that demo branch, as it is not integrated with the rest, so is just misleading.&lt;/p&gt;</comment>
                                                            <comment id="188780" author="5ced27478b03050f27825a93" created="Wed, 11 Apr 2018 16:26:26 +0000"  >&lt;p&gt;I have a to-do to take what Patti has on her branch and turn it into a stand-alone fragment of HTML/CSS that can be inserted into any of our web sites.&lt;/p&gt;</comment>
                                                            <comment id="188783" author="61cd0ca0bce5e00069e98be7" created="Thu, 12 Apr 2018 05:43:37 +0000"  >&lt;p&gt;See &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-1162?focusedCommentId=191364&amp;amp;page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;FOLIO-1162 comment&lt;/a&gt; which prepares the current site&apos;s top banner area for the new branding. It is fully integrated with the current theme, so we do not require any workarounds.&lt;/p&gt;</comment>
                                                            <comment id="188786" author="5af5ea1ed95cfc55bfb76c8d" created="Fri, 13 Apr 2018 21:19:16 +0000"  >&lt;p&gt;I had already started a standalone version of the POC branch top navigation when &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ced27478b03050f27825a93&quot; class=&quot;user-hover&quot; rel=&quot;5ced27478b03050f27825a93&quot; data-account-id=&quot;5ced27478b03050f27825a93&quot; accountid=&quot;5ced27478b03050f27825a93&quot; rel=&quot;noreferrer&quot;&gt;Peter Murray&lt;/a&gt; suggested it.  So, in case it would help &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ced27478b03050f27825a93&quot; class=&quot;user-hover&quot; rel=&quot;5ced27478b03050f27825a93&quot; data-account-id=&quot;5ced27478b03050f27825a93&quot; accountid=&quot;5ced27478b03050f27825a93&quot; rel=&quot;noreferrer&quot;&gt;Peter Murray&lt;/a&gt;, wanted to get everything that I have done up to github.  I pulled all the javascript out, isolated the nav bar in a jekyll project and re-created the style and responsive behavior.  Most of the css is still external, but all local within the jekyll project.  I thought it was a start and wanted to push it up there in case it could help &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ced27478b03050f27825a93&quot; class=&quot;user-hover&quot; rel=&quot;5ced27478b03050f27825a93&quot; data-account-id=&quot;5ced27478b03050f27825a93&quot; accountid=&quot;5ced27478b03050f27825a93&quot; rel=&quot;noreferrer&quot;&gt;Peter Murray&lt;/a&gt;.  I put it into a separate repo to isolate the nav bar.  Assuming that you have jekyll installed, you can clone my fork and check it out:&lt;/p&gt;

&lt;p&gt;clone the project - git clone &lt;a href=&quot;https://github.com/pdestefano/FOLIO-714-standalone-nav.git&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/pdestefano/FOLIO-714-standalone-nav.git&lt;/a&gt;&lt;br/&gt;
build it - bundle exec jekyll serve&lt;br/&gt;
try it - browse to &lt;a href=&quot;http://localhost:4000&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;http://localhost:4000&lt;/a&gt;&lt;/p&gt;</comment>
                                                            <comment id="188789" author="5ced27478b03050f27825a93" created="Tue, 24 Apr 2018 20:02:40 +0000"  >&lt;p&gt;Unfortunately, that still has the primary and secondary navbar bundled up in one &amp;lt;div&amp;gt;, which makes it impossible to lift the code out and put it on another site.  But it was certainly a helpful place to start.  I&apos;ve pulled out the relevant HTML and CSS to create a pair of stand-alone files:&lt;/p&gt;

&lt;p&gt;  &lt;a href=&quot;https://dev.folio.org/assets/projectwide-navbar/v0.0.1/projectwide-navbar.html&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://dev.folio.org/assets/projectwide-navbar/v0.0.1/projectwide-navbar.html&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The only thing that this version doesn&apos;t do that Patti&apos;s does it use an on-click handler for the drop-down menus.  That got coded using JQuery, which is something that I don&apos;t want to assume is on any of the project&apos;s websites.  What is there now is done with CSS, but some bespoke JavaScript could be whipped up that does the same thing as the JQuery code.&lt;/p&gt;

&lt;p&gt;For a brief period of time, I loaded the project-wide navbar onto wiki.folio.org and took a snapshot:&lt;/p&gt;

&lt;p&gt; &lt;span class=&quot;image-wrap&quot; style=&quot;&quot;&gt;&lt;a id=&quot;63984_thumb&quot; href=&quot;/rest/api/3/attachment/content/63984&quot; title=&quot;wiki-folio-org-screenshot-1.png&quot; file-preview-type=&quot;image&quot; file-preview-id=&quot;63984&quot; file-preview-title=&quot;wiki-folio-org-screenshot-1.png&quot;&gt;&lt;jira-attachment-thumbnail url=&quot;https://folio-org.atlassian.net/rest/api/3/attachment/thumbnail/63984?default=false&quot; jira-url=&quot;https://folio-org.atlassian.net/rest/api/3/attachment/thumbnail/63984&quot; filename=&quot;wiki-folio-org-screenshot-1.png&quot;&gt;&lt;img src=&quot;https://folio-org.atlassian.net/rest/api/3/attachment/thumbnail/63984&quot; data-attachment-name=&quot;wiki-folio-org-screenshot-1.png&quot; data-attachment-type=&quot;thumbnail&quot; data-media-services-id=&quot;da2f7730-7792-4134-a8a1-6cf8df6826aa&quot; data-media-services-type=&quot;file&quot; style=&quot;border: 0px solid black&quot; /&gt;&lt;/jira-attachment-thumbnail&gt;&lt;/a&gt;&lt;/span&gt; &lt;/p&gt;

&lt;p&gt;I think we&apos;ll want to collapse the space between the two navbars, but for now this is a work-in-progress.  The code lives at &lt;a href=&quot;https://github.com/folio-org/folio-org.github.io/tree/master/assets/projectwide-navbar/v0.0.1&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/folio-org.github.io/tree/master/assets/projectwide-navbar/v0.0.1&lt;/a&gt; ... I figure we&apos;ll use semantic versioning in the directory name so we can gracefully rollout new versions.&lt;/p&gt;</comment>
                                                            <comment id="188792" author="5ced27478b03050f27825a93" created="Tue, 24 Apr 2018 23:18:16 +0000"  >&lt;p&gt;Okay &amp;#8211; the lack of that JavaScript capability was really bugging me.  I&apos;ve updated the navbar source with that capability and cleaned up the code some.  You can see what it looks like on this branch of the dev website:&lt;/p&gt;

&lt;p&gt;  &lt;a href=&quot;http://folio-714-standalone-topnav.dev.folio.org.s3-website-us-east-1.amazonaws.com&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;http://folio-714-standalone-topnav.dev.folio.org.s3-website-us-east-1.amazonaws.com&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I think this is ready to go. Thoughts?&lt;/p&gt;</comment>
                                                            <comment id="188794" author="61cd0ca0bce5e00069e98be7" created="Wed, 25 Apr 2018 04:26:45 +0000"  >&lt;p&gt;It is great that you have a stand-alone navbar working in 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-1224&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-1224&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Create standalone HTML/CSS for FOLIO-wide navbar&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            FOLIO-1224
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
.&lt;/p&gt;

&lt;p&gt;However, i do not think that it should be a blocker for this issue 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-714&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-714&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Utilise the FOLIO Common Top Navigation Bar for dev.f.o&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            FOLIO-714
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
, i.e. to apply a common navbar to dev.folio.org site.&lt;/p&gt;

&lt;p&gt;We have options, as shown in 
    &lt;span class=&quot;jira-issue-macro&quot; data-jira-key=&quot;FOLIO-1162&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-1162&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Update branding for dev.f.o&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            FOLIO-1162
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-complete jira-macro-single-issue-export-pdf&quot;&gt;Open&lt;/span&gt;
            &lt;/span&gt;
. There we are just waiting for the colours and logos (which i can probably now get from your branches). In that way the capability is completely integrated. &lt;/p&gt;

&lt;p&gt;The branch demonstration &quot;folio-714-standalone-topnav&quot; has a problem. At narrow browser width the top navbar mangles the rest of the dev.f.o navigation.&lt;/p&gt;

&lt;p&gt;I would like time to explore the alternatives:&lt;/p&gt;

&lt;p&gt;A) Continue 
    &lt;span class=&quot;jira-issue-macro&quot; data-jira-key=&quot;FOLIO-1162&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-1162&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Update branding for dev.f.o&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            FOLIO-1162
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-complete jira-macro-single-issue-export-pdf&quot;&gt;Open&lt;/span&gt;
            &lt;/span&gt;
 to apply a common top navbar in an integrated way. I have been working on the assumption that we need both the dev.f.o menubar, and a project-wide common top one, able to be used for navigation at both wide and narrow widths.&lt;/p&gt;

&lt;p&gt;B) Improve your &quot;folio-714-standalone-topnav&quot; (or a new branch) to better apply the full 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-1224&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-1224&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Create standalone HTML/CSS for FOLIO-wide navbar&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            FOLIO-1224
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
 standalone one. This would assume that it is okay to not have its top navigation menus available at narrow width. Also, there must be a way to add it so that it behaves well with the main dev.f.o navigation. There are also other issues to address, e.g. the rest of the site needs configuration tweaks to accommodate the different height of this top navbar with the fixed top banner (try selecting one of the in-page section links &amp;#8211; the section heading is now partially hidden).&lt;/p&gt;</comment>
                                                            <comment id="188797" author="5ced27478b03050f27825a93" created="Wed, 25 Apr 2018 13:15:36 +0000"  >&lt;p&gt;The point of 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-1224&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-1224&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Create standalone HTML/CSS for FOLIO-wide navbar&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            FOLIO-1224
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
 is to come up with a standalone navbar that would be applied to all FOLIO websites (dev.folio.org, wiki.folio.org, issues.folio.org, ux.folio.org, etc.).  (I created the other issues blocked by 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-1224&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-1224&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Create standalone HTML/CSS for FOLIO-wide navbar&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            FOLIO-1224
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
 to list those cases.  Feel free to add other blockers for other websites that I forgot about.)  So I&apos;m not sure how you see that 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-1224&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-1224&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Create standalone HTML/CSS for FOLIO-wide navbar&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            FOLIO-1224
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
 isn&apos;t a blocker for this.&lt;/p&gt;

&lt;p&gt;Thanks for pointing out the issues at narrower widths; I&apos;ll work on that in 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-1224&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-1224&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Create standalone HTML/CSS for FOLIO-wide navbar&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            FOLIO-1224
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
 today.  &lt;/p&gt;

&lt;p&gt;Please don&apos;t push updates to master that affect the branding (
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-714&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-714&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Utilise the FOLIO Common Top Navigation Bar for dev.f.o&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            FOLIO-714
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
 and 
    &lt;span class=&quot;jira-issue-macro&quot; data-jira-key=&quot;FOLIO-1162&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-1162&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Update branding for dev.f.o&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            FOLIO-1162
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-complete jira-macro-single-issue-export-pdf&quot;&gt;Open&lt;/span&gt;
            &lt;/span&gt;
) until we get this sorted out.&lt;/p&gt;</comment>
                                                            <comment id="188799" author="61cd0ca0bce5e00069e98be7" created="Wed, 25 Apr 2018 13:32:28 +0000"  >&lt;p&gt;Yes i understand about not pushing to master yet.&lt;/p&gt;

&lt;p&gt;I have a branch to address option A above. It still needs some work, but would be possible if we cannot do option B.&lt;/p&gt;

&lt;p&gt;I will work on a new branch for option B. I reckon that the way you have inserted it is not correct.&lt;/p&gt;</comment>
                                                            <comment id="188802" author="61cd0ca0bce5e00069e98be7" created="Thu, 26 Apr 2018 01:57:42 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ced27478b03050f27825a93&quot; class=&quot;user-hover&quot; rel=&quot;5ced27478b03050f27825a93&quot; data-account-id=&quot;5ced27478b03050f27825a93&quot; accountid=&quot;5ced27478b03050f27825a93&quot; rel=&quot;noreferrer&quot;&gt;Peter Murray&lt;/a&gt; I have found joy using a different way to add the projectwide-navbar, using a banner overlay. Will tidy up and push the branch soon. This plays well with the dev navbar.&lt;/p&gt;

&lt;p&gt;(Of course this does not address the issue of the projectwide-navbar handling its menu items in the narrow width.)&lt;/p&gt;</comment>
                                                            <comment id="188804" author="61cd0ca0bce5e00069e98be7" created="Thu, 26 Apr 2018 03:11:02 +0000"  >&lt;p&gt;The branch &lt;a href=&quot;https://github.com/folio-org/folio-org.github.io/tree/FOLIO-714-standalone-navbar-2&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;FOLIO-714-standalone-navbar-2&lt;/a&gt; (see &lt;a href=&quot;http://folio-714-standalone-navbar-2.dev.folio.org.s3-website-us-east-1.amazonaws.com&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;build&lt;/a&gt;) uses a banner overlay which keeps the projectwide-navbar separate.&lt;/p&gt;

&lt;p&gt;The prior work had used a second &quot;menubar&quot; to piggyback on the theme&apos;s facilities. This worked well when we had that integrated with the rest of the theme, but to be truly standalone this seems to be better.&lt;/p&gt;</comment>
                                                            <comment id="188805" author="5ced27478b03050f27825a93" created="Fri, 27 Apr 2018 16:07:10 +0000"  >&lt;p&gt;Hmmm &amp;#8211; yes, that makes sense to me.  Let me see if I can build on that while doing the mobile-friendly version of the project-wide navbar.&lt;/p&gt;</comment>
                                                            <comment id="188807" author="5ced27478b03050f27825a93" created="Fri, 27 Apr 2018 22:20:44 +0000"  >&lt;p&gt;I have a new version build on this branch, but it is getting tripped up by the styling on the container you put it in.  Why did you set &lt;a href=&quot;https://github.com/folio-org/folio-org.github.io/blob/81bd4eea815930ff5be6bd17e5736c77b70c2897/_sass/_folio.scss#L8&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;display of the navbar to `flex`&lt;/a&gt;? If I disable this in the browser inspector, the projectwide navbar works fine.&lt;/p&gt;

&lt;p&gt;In retrospect, I&apos;m not sure what you are aiming to accomplish.  Unless I&apos;m missing something, this should be as easy as sticking a chunk of HTML just after the &amp;lt;body&amp;gt; tag plus including the chunk-of-HTML-specific CSS file.  I&apos;ve added the project navbar to the FOLIO wiki and will leave it there for the weekend.  Confluence inserts a few containing tags, but they have very little styling &amp;#8211; none of which gets in the way of the project navbar.&lt;/p&gt;</comment>
                                                            <comment id="188810" author="61cd0ca0bce5e00069e98be7" created="Sun, 29 Apr 2018 07:59:26 +0000"  >&lt;p&gt;Regarding the &quot;flex&quot;. Ah that is just because i copied an overlay from the theme. It uses various overlays in the banner area (not the dev navbar, but the banner/title/menu-disclosure part) and the theme uses &quot;flex&quot; throughout.&lt;/p&gt;

&lt;p&gt;I did your suggestion locally, to remove that from the commit that you linked. On quick inspection i only see one difference. The projectwide-navbar hits hard up on the right hand edge. But your new version would have improved handling of various stuff, so perhaps that is fixed.&lt;/p&gt;

&lt;p&gt;Please commit any changes that you need to make to this branch. I will follow up to test them.&lt;/p&gt;</comment>
                                                            <comment id="188812" author="61cd0ca0bce5e00069e98be7" created="Sun, 29 Apr 2018 08:00:19 +0000"  >&lt;p&gt;I am trying to accomplish adding the projectwide-navbar without affecting the rest of the theme.&lt;/p&gt;

&lt;p&gt;It also needs to interact well when the browser switches to narrow width.&lt;/p&gt;

&lt;p&gt;Remember that we are trying to insert something that the theme is not expecting, and it has its own way to handle this top-of-page area.&lt;/p&gt;

&lt;p&gt;I will look again for other ways to insert this.&lt;/p&gt;</comment>
                                                            <comment id="188814" author="61cd0ca0bce5e00069e98be7" created="Mon, 30 Apr 2018 11:55:57 +0000"  >&lt;p&gt;As expected, inserting the projectwide-navbar before (and so outside) the banner area causes a new set of difficulties. The extra unexpected height throws off the layout&apos;s placement of its items.&lt;/p&gt;

&lt;p&gt;However, i have been able to achieve a suitable solution.&lt;/p&gt;

&lt;p&gt;See the branch &lt;a href=&quot;https://github.com/folio-org/folio-org.github.io/tree/FOLIO-714-standalone-navbar-3&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;FOLIO-714-standalone-navbar-3&lt;/a&gt; (and its &lt;a href=&quot;http://folio-714-standalone-navbar-3.dev.folio.org.s3-website-us-east-1.amazonaws.com&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;build&lt;/a&gt;).&lt;/p&gt;</comment>
                                                            <comment id="188815" author="5ced27478b03050f27825a93" created="Mon, 30 Apr 2018 20:24:48 +0000"  >&lt;p&gt;Oh!  I see what you are trying to do &amp;#8211; pin the navbar(s) to the top of the page.  Hmm.  If we can find a way to mimic what Confluence is doing on wiki.folio.org (where the projectwide navbar scrolls out of the way and the site-specific navbar gets pinned to the top) that would be best.  I&apos;m not liking the effect where the menus of the project navbar scroll out of view as one goes down the page.&lt;/p&gt;</comment>
                                                            <comment id="188817" author="5ced27478b03050f27825a93" created="Mon, 30 Apr 2018 20:31:44 +0000"  >&lt;p&gt;Oh, and thanks for pointing out that I was missing some styling of the standalone code:&lt;/p&gt;

&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;+#projectwide-navbar {
+  width: 100%;
+  z-index: 10;
+}
+.projectwide-navbar-themenu {
+  padding-right: 8px;
+}
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;I&apos;ll add that and commit a change.&lt;/p&gt;</comment>
                                                            <comment id="188818" author="61cd0ca0bce5e00069e98be7" created="Tue, 1 May 2018 09:22:43 +0000"  >&lt;p&gt;I do not like that &quot;scroll out of view&quot; behaviour either (i.e. the &lt;a href=&quot;http://folio-714-standalone-navbar-3.dev.folio.org.s3-website-us-east-1.amazonaws.com&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;FOLIO-714-standalone-navbar-3 build&lt;/a&gt;). That is the best that can be done with that way of inserting the projectwide-navbar. It also contravenes the mechanisms of the theme.&lt;/p&gt;</comment>
                                                            <comment id="188820" author="61cd0ca0bce5e00069e98be7" created="Tue, 1 May 2018 09:25:16 +0000"  >&lt;p&gt;Anyway i am celebrating. It is now all working properly on branch &lt;a href=&quot;https://github.com/folio-org/folio-org.github.io/tree/FOLIO-714-standalone-navbar-2&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;FOLIO-714-standalone-navbar-2&lt;/a&gt; (and its &lt;a href=&quot;http://folio-714-standalone-navbar-2.dev.folio.org.s3-website-us-east-1.amazonaws.com&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;build&lt;/a&gt;).&lt;/p&gt;

&lt;p&gt;It is an integrated part of the fixed-top banner of the dev site. It will be easy to keep up-to-date when the theme upgrades to newer versions, and easy to accommodate new versions of the projectwide-navbar. I reckon that this is ideal, providing the context with the rest of FOLIO.&lt;/p&gt;</comment>
                                                            <comment id="188822" author="5ced27478b03050f27825a93" created="Tue, 1 May 2018 15:28:39 +0000"  >&lt;p&gt;Congratulations!  That looks great.  I think that is ready to commit to master, yes?&lt;/p&gt;</comment>
                                                            <comment id="188824" author="61cd0ca0bce5e00069e98be7" created="Wed, 2 May 2018 05:36:12 +0000"  >&lt;p&gt;I agree. Then we can follow later to add the further updates for the 
    &lt;span class=&quot;jira-issue-macro&quot; data-jira-key=&quot;FOLIO-1162&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-1162&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Update branding for dev.f.o&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            FOLIO-1162
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-complete jira-macro-single-issue-export-pdf&quot;&gt;Open&lt;/span&gt;
            &lt;/span&gt;
 branding.&lt;/p&gt;</comment>
                                                            <comment id="188826" author="61cd0ca0bce5e00069e98be7" created="Wed, 2 May 2018 15:13:14 +0000"  >&lt;p&gt;Done. Merged in &lt;a href=&quot;https://github.com/folio-org/folio-org.github.io/pull/190&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;pull/190&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Thanks Peter. Very nice.&lt;/p&gt;</comment>
                                                            <comment id="188828" author="61cd0ca0bce5e00069e98be7" created="Tue, 19 Jun 2018 06:32:56 +0000"  >&lt;p&gt;Peter solved the remaining issues with applying this to dev.f.o site, especially in narrow width. See yesterday&apos;s notes at 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-1224&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-1224&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Create standalone HTML/CSS for FOLIO-wide navbar&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            FOLIO-1224
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
. I had tried something similar before, but could not achieve it. Probably removing the fixed-top banner was a part of the solution.&lt;/p&gt;

&lt;p&gt;I followed on in that branch to show the site title. It is shown for all browser widths. Also made it appear to be integrated with the projectwide-navbar, rather than a separate background colour. I like it the way that it is now. However if you feel that the second banner row should be orange, or that it should be removed in widest and medium widths, then please do so.&lt;/p&gt;</comment>
                                                            <comment id="188831" author="5ced27478b03050f27825a93" created="Tue, 19 Jun 2018 13:41:16 +0000"  >&lt;p&gt;Ah, perfect!  Nicely done &amp;#8211; thanks for those additions.  I feel pretty good about calling this done.  I&apos;ll make a pull request to put it on the production site, then update the other sites that are using it now.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                                                <inwardlinks description="is blocked by">
                                        <issuelink>
            <issuekey id="80654">FOLIO-1224</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="80248">FOLIO-643</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="63979" name="navbaro.png" size="24266" author="5af5ea1ed95cfc55bfb76c8d" created="Wed, 12 Jul 2017 18:47:38 +0000"/>
                            <attachment id="63980" name="navbarwebv.png" size="24696" author="5af5ea1ed95cfc55bfb76c8d" created="Wed, 12 Jul 2017 18:55:34 +0000"/>
                            <attachment id="63981" name="topnav-20171116.png" size="32070" author="61cd0ca0bce5e00069e98be7" created="Thu, 16 Nov 2017 19:45:36 +0000"/>
                            <attachment id="63982" name="topnavcv1.jpg" size="39689" author="5af5ea1ed95cfc55bfb76c8d" created="Wed, 13 Sep 2017 20:02:33 +0000"/>
                            <attachment id="63983" name="topnavov1.jpg" size="45381" author="5af5ea1ed95cfc55bfb76c8d" created="Wed, 13 Sep 2017 20:02:36 +0000"/>
                            <attachment id="63984" name="wiki-folio-org-screenshot-1.png" size="312640" author="5ced27478b03050f27825a93" created="Tue, 24 Apr 2018 20:00:30 +0000"/>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10000" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummarycf">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10019" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|hzxqyf:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10020" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10024" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>[CHART] Date of First Response</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Thu, 16 Nov 2017 19:46:51 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10025" key="com.atlassian.jira.ext.charting:timeinstatus">
                        <customfieldname>[CHART] Time in Status</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                    </customfields>
    </item>
</channel>
</rss>