<!-- 
RSS generated by JIRA (1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d) at Thu Feb 08 23:08:32 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-817] Investigate another jekyll theme</title>
                <link>https://folio-org.atlassian.net/browse/FOLIO-817</link>
                <project id="10290" key="FOLIO">FOLIO</project>
                    <description>&lt;p&gt;Investigation to create a custom jekyll theme that will accommodate the styled common top navigation bar for the site, a dev navigation bar, left hand navigation and content bucketing.&lt;/p&gt;</description>
                <environment></environment>
        <key id="80395">FOLIO-817</key>
            <summary>Investigate another jekyll theme</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="5af5ea1ed95cfc55bfb76c8d">Patricia DeStefano</assignee>
                                                                <reporter accountid="61cd0ca0bce5e00069e98be7">David Crossley</reporter>
                                    <labels>
                            <label>devweb</label>
                    </labels>
                <created>Wed, 30 Aug 2017 06:47:46 +0000</created>
                <updated>Mon, 12 Nov 2018 14:23:43 +0000</updated>
                            <resolved>Wed, 22 Aug 2018 06:45:53 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>5</watches>
                                                    <timespent seconds="168900">1 week, 6 hours, 55 minutes</timespent>
                                <comments>
                                                            <comment id="189164" author="5af5ea1ed95cfc55bfb76c8d" created="Tue, 12 Sep 2017 16:59:39 +0000"  >&lt;p&gt;I was just about finished my 3rd branch with 3 options for everyone to look over- one branch with just the common nav bar, one branch with the common nav bar &amp;amp; a 2nd nav bar, and lastly, one branch with with a common nav bar, 2nd dev nav bar &amp;amp; left hand navigation. Then, &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; &amp;amp; I met with the EBSCO marketing web team and other partners. The EBSCO marketing web team also looked over dev.folio.org. They had some recommendations as well. Once I hear back from them to verify how to accommodate the team&apos;s recommendations, I can post the top navigation recommendation (it has changed...) in 
    &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;
 that will need to appear on the dev site as well in order to align with the FOLIO suite of sites. I will then work to incorporate the web team recommendations into the theme that I am working on for you to examine.&lt;/p&gt;</comment>
                                                            <comment id="189167" author="5af5ea1ed95cfc55bfb76c8d" created="Fri, 13 Oct 2017 21:08:58 +0000"  >
&lt;p&gt;I have created a POC for dev.folio.org that incorporates the following FOLIO partner revision recommendations:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Top navigation that is laid out and styled as desired by FOLIO partners to align with the rest of the site.&lt;/li&gt;
	&lt;li&gt;Developer navigation to allow users to explore the developer material broadly.&lt;/li&gt;
	&lt;li&gt;Left hand vertical navigation for scalability, to divide the content and make what is available for content clear to the user.&lt;/li&gt;
	&lt;li&gt;Bucketing content to support chunking theory which is how users browse.&lt;/li&gt;
	&lt;li&gt;Labels match the page titles to make location clear.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;The following recommendations can be added, but are not in the POC now:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Eliminate redundant material - I did eliminate some, but there is still some in there.&lt;/li&gt;
	&lt;li&gt;Rework the copy a bit and add more copy to each section.  Add more sections.&lt;/li&gt;
	&lt;li&gt;Eliminate pointing to github and bring the information into the site.&lt;/li&gt;
	&lt;li&gt;Apply search - can place one in the nav bar - lunrjs?&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;In the POC examples...&lt;br/&gt;
If a developer is interested in learning about a portion of FOLIO -&amp;gt;&lt;br/&gt;
Click &lt;b&gt;Tutorials&lt;/b&gt;&lt;br/&gt;
Click &lt;b&gt;Folio Developer&apos;s Curriculum&lt;/b&gt;&lt;br/&gt;
...we can add more tutorials to the left hand menu as we go.&lt;/p&gt;

&lt;p&gt;If a developer is interested in the Guidelines for Contributing Code -&amp;gt;&lt;br/&gt;
Click &lt;b&gt;Guidelines&lt;/b&gt;&lt;br/&gt;
Click &lt;b&gt;Contributing Code&lt;/b&gt;&lt;br/&gt;
Choose a section to browse&lt;br/&gt;
...other sections of guidelines are visible to the user as the same time.&lt;/p&gt;

&lt;p&gt;Labels, Sections, Nav bars, etc can all be adjusted, deleted and moved around.&lt;/p&gt;

&lt;p&gt;Assuming that you have jekyll installed, you can follow the instructions below to clone my fork and check it out:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;clone the project -  git clone &lt;a href=&quot;https://github.com/pdestefano/folio-org.github.io.git&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/pdestefano/folio-org.github.io.git&lt;/a&gt;&lt;/li&gt;
	&lt;li&gt;switch to the POC branch - git checkout folio-817-top-side-nav&lt;/li&gt;
	&lt;li&gt;build it - bundle exec jekyll serve&lt;/li&gt;
	&lt;li&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;/li&gt;
&lt;/ul&gt;

</comment>
                                                            <comment id="189172" author="61cd0ca0bce5e00069e98be7" created="Tue, 17 Oct 2017 07:32:48 +0000"  >&lt;p&gt;I have commenced investigation. There are many changes. It will take some time to assess.&lt;/p&gt;</comment>
                                                            <comment id="189175" author="61cd0ca0bce5e00069e98be7" created="Tue, 24 Oct 2017 07:29:20 +0000"  >&lt;p&gt;I will gradually add some comments. However not expecting you to modify the PoC.&lt;/p&gt;</comment>
                                                            <comment id="189178" author="61cd0ca0bce5e00069e98be7" created="Tue, 24 Oct 2017 07:30:54 +0000"  >&lt;p&gt;The &lt;a href=&quot;https://github.com/folio-org/curriculum&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;Curriculum&lt;/a&gt; is in a separate repository. When it deploys, it is published to &lt;a href=&quot;http://dev.folio.org/curriculum/&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;dev.folio.org/curriculum/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I gather that this is deliberate, so that it is completely stand-alone and concise.&lt;/p&gt;</comment>
                                                            <comment id="189181" author="61cd0ca0bce5e00069e98be7" created="Tue, 24 Oct 2017 07:32:58 +0000"  >&lt;p&gt;The developers have decided to have the main documentation of each module alongside its code.&lt;/p&gt;

&lt;p&gt;For example the &lt;a href=&quot;https://github.com/folio-org/okapi/blob/master/doc/guide.md&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;Okapi Guide&lt;/a&gt; is at Okapi, the docs for each of the &lt;a href=&quot;https://github.com/folio-org/stripes-components&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;Stripes Components&lt;/a&gt;&lt;br/&gt;
is inside each component, &lt;a href=&quot;https://github.com/folio-org/stripes-core/blob/master/doc/dev-guide.md&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;The Stripes Module Developer&apos;s Guide&lt;/a&gt; is in the stripes-core repository, etc.&lt;/p&gt;

&lt;p&gt;Other high-level documentation is to be here at dev.folio.org, with links to that documentation.&lt;/p&gt;

&lt;p&gt;Yes some of it may be better moved to dev.folio.org, but most will remain together with its code.&lt;/p&gt;</comment>
                                                            <comment id="189184" author="61cd0ca0bce5e00069e98be7" created="Wed, 1 Nov 2017 08:13:23 +0000"  >&lt;p&gt;Regarding the display of logos of key organisations, see a proposal at 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-919&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-919&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Display logos of partner and developer organisations at 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-919
        &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 present those on the new &quot;thanks&quot; page.&lt;/p&gt;

&lt;p&gt;Your PoC has few examples on the bottom of the front page. The proposal would accomodate more.&lt;/p&gt;</comment>
                                                            <comment id="189188" author="61cd0ca0bce5e00069e98be7" created="Wed, 1 Nov 2017 14:36:57 +0000"  >&lt;p&gt;Splitting the documentation into small pieces frightens me. It is not how i read stuff, and not how the developers wrote the Okapi Guide and Stripes Developers docs for example. Perhaps some docs are relevant to keep whole, with links to main sections in the left-side panel.&lt;/p&gt;

&lt;p&gt;Rearrangement will cause many broken links in this documentation and in the docs at each github repository. I suppose that we can cope with that, but there will be problems for a while.&lt;/p&gt;</comment>
                                                            <comment id="189192" author="61cd0ca0bce5e00069e98be7" created="Wed, 1 Nov 2017 14:37:31 +0000"  >&lt;p&gt;I feel that this theme is complex and might be difficult to maintain.&lt;/p&gt;

&lt;p&gt;Is it based on a version of some available product?&lt;/p&gt;</comment>
                                                            <comment id="189195" author="61cd0ca0bce5e00069e98be7" created="Wed, 1 Nov 2017 14:38:41 +0000"  >&lt;p&gt;The site needs to be available to Asian developers, so it currently uses a CDN that is reliable there to get the jQuery JS.&lt;/p&gt;

&lt;p&gt;So do we really need to use Google fonts? That might not be readily available.&lt;/p&gt;</comment>
                                                            <comment id="189197" author="5ced27478b03050f27825a93" created="Wed, 1 Nov 2017 16:36:46 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5ea1ed95cfc55bfb76c8d&quot; class=&quot;user-hover&quot; rel=&quot;5af5ea1ed95cfc55bfb76c8d&quot; data-account-id=&quot;5af5ea1ed95cfc55bfb76c8d&quot; accountid=&quot;5af5ea1ed95cfc55bfb76c8d&quot; rel=&quot;noreferrer&quot;&gt;Patricia DeStefano&lt;/a&gt; - David pointed me to this ticket a little while ago.  The new design is coming along fine.  I can&apos;t recall exactly why I create a separate repository for the curriculum.  I think I had in mind that people who were only tangentially related to the project could submit corrections and pull requests against the curriculum only without having access to the wider dev.folio.org site.  If merges to master are protected here on GitHub, that becomes less of a concern, I suppose.&lt;/p&gt;</comment>
                                                            <comment id="189200" author="5af5ea1ed95cfc55bfb76c8d" created="Wed, 1 Nov 2017 20:48:44 +0000"  >&lt;p&gt;Let me see if I can address some of your comments with regards to the POC. &lt;/p&gt;

&lt;p&gt;The directories in the POC project correspond to the sections on the dev navigation bar.  So, if you are looking to edit a webpage in the guidelines section, the corresponding markdown will be in the _guidelines directory.&lt;/p&gt;

&lt;p&gt;So, to make some common updates...&lt;/p&gt;

&lt;p&gt;To Edit an Existing Page:&lt;br/&gt;
Find the markdown file for the web page in the project directory that corresponds to the page&apos;s dev nav bar section.  Edit the file and rebuild the project.&lt;/p&gt;

&lt;p&gt;To Add a New Page to an Existing Section:&lt;br/&gt;
First, determine the dev nav section that you would like to add the new page to - Getting Started, Reference, Code, etc.  Create a new, empty markdown file in the corresponding directory.  For example, if you would like a web page to appear in the guidelines section, create the markdown file in the _guidelines directory.  Copy the Front Matter from another markdown file in the same directory to your new file and alter accordingly.  The Front Matter layout will stay the same and the permalink should be your file name.  Create an appropriate title and heading for your content.  Create your new markdown content.  Find the yml file for the section that you chose in the _data directory and add your new filename in the list of sections where you would like it to appear.  This places the new file in the left hand nav.  Rebuild the project.  &lt;/p&gt;

&lt;p&gt;Thanks for the access information about the Curriculum repo &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 placed the Curriculum in the Tutorials section for the POC, but it can be placed anywhere you would like.  My thinking was to align it with the rest of the site.  It did lend itself to be dropped very easily in since you already had the left hand nav.  Also, you can place a number of tutorials in that section in the future&#8230;.all unified, in the same place, with the same look and feel.  It can still be placed in a separate repo if you desire, but we may want to apply the theme to the additional repo too so that the user can navigate back.  Either way, we could link out for now to the separate repo if it is an issue and think about it later.  &lt;/p&gt;

&lt;p&gt;Breaking up the documentation into logical smaller sections avoids a wall of text, which can increase bounce rates.  Just to be clear&#8230;this is just for the document site docs&#8230;we are not touching anything in the github source repos in the POC. &lt;/p&gt;

&lt;p&gt;&quot;Rearrangement will cause many broken links in this documentation and in the docs at each github repository.&quot;  Can you give me an example from the POC so that I can address it?  I thought that I checked all of the links, but could have missed something.  I also tried to make sure that all of the information that was in dev.folio.org at the time of my last sync is in the new POC&#8230;.just divided into the different sections.  Any of the sections or content in the sections can be changed if you prefer it a different way&#8230;just let me know...it can easily be adjusted.&lt;/p&gt;

&lt;p&gt;Replaced the jQuery JS with the CDN source&#8230;.will push that up.&lt;/p&gt;

&lt;p&gt;Google Fonts are one of the top sources for typefaces.  That said, if something was to happen, we have several web font fallbacks in line.&lt;/p&gt;

&lt;p&gt;We can table bringing the information from the individual github repos into the site if you would like.  That is not included in this POC&#8230;so, that can be discussed at a later time to see if it is worthwhile.  The links out to the different repos are all still there in the POC.  After we satisfy the first set of recommendations from the partners, we can see where to go next.&lt;/p&gt;

&lt;p&gt;Please let me know if I can help in any way of if you need any further information.&lt;/p&gt;</comment>
                                                            <comment id="189205" author="5ced27478b03050f27825a93" created="Fri, 3 Nov 2017 21:08:50 +0000"  >&lt;p&gt;Thanks for your work on the Proof-of-Concept Patti.  Some comments:&lt;/p&gt;

&lt;h2&gt;&lt;a name=&quot;Leftsidebarnavigation&quot;&gt;&lt;/a&gt;Left sidebar navigation&lt;/h2&gt;
&lt;p&gt;When there is only one page in a section on the left sidebar, one has to click twice to get to it.  For instance, starting at &lt;a href=&quot;http://127.0.0.1:4000/getstarted/index/&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;http://127.0.0.1:4000/getstarted/index/&lt;/a&gt;, one needs to click on &quot;Front End&quot; then &quot;Primer for Front-End Development&quot; to get to the next page.  When there is only one sub-page under a left nav heading, this extra click shouldn&apos;t be necessary.&lt;/p&gt;

&lt;p&gt;The styling of the links in the left navbar is weird.  If I haven&apos;t visited a page on the left navbar, the link text is black.  If I have visited a page, the link text is blue.  I&apos;d prefer black for both.&lt;/p&gt;

&lt;h2&gt;&lt;a name=&quot;URLstructure&quot;&gt;&lt;/a&gt;URL structure&lt;/h2&gt;
&lt;p&gt;The root pages of sections on the top nav bar are inside an &quot;index&quot; directory.  A typical navigation pattern wouldn&apos;t include this.  e.g., rather than &lt;a href=&quot;http://127.0.0.1:4000/getstarted/index/&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;http://127.0.0.1:4000/getstarted/index/&lt;/a&gt; the URL should be &lt;a href=&quot;http://127.0.0.1:4000/getstarted/&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;http://127.0.0.1:4000/getstarted/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The URLs for the curriculum pages are going to change.  I&apos;m not so sure that is a problem as long as they are internally consistent.  On further reflection, I don&apos;t think it is going to be an issue to put the curriculum content into the main folio-org repo and deprecate the existing curriculum repo.&lt;/p&gt;

&lt;h2&gt;&lt;a name=&quot;Projectwidenavigation&quot;&gt;&lt;/a&gt;Project-wide navigation&lt;/h2&gt;
&lt;p&gt;Has this been nailed down yet?  What is in the Proof-of-Concept is missing some top-level headings, no?&lt;/p&gt;

&lt;h2&gt;&lt;a name=&quot;Other&quot;&gt;&lt;/a&gt;Other&lt;/h2&gt;
&lt;p&gt;The &quot;Improve this page&quot; link on the bottom of each page doesn&apos;t seem to go anywhere right now.  Will this point to something when it is live on the GitHub Pages site?&lt;/p&gt;</comment>
                                                            <comment id="189208" author="5ced27478b03050f27825a93" created="Fri, 3 Nov 2017 21:09:37 +0000"  >&lt;p&gt;Oh, missed one thing.  I think using Google Fonts is okay.  It is widely used and degrades nicely if not available.&lt;/p&gt;</comment>
                                                            <comment id="189211" author="5af5ea1ed95cfc55bfb76c8d" created="Fri, 3 Nov 2017 21:50:54 +0000"  >&lt;p&gt;Thank you for the comments &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;.  Will take a look on Monday, but looking at it now...doesn&apos;t look like your requests will be a problem to implement in the theme.  The &quot;Improve this Page&quot; was to be able to directly edit the pages in Github (not linked yet).  Guessing we don&apos;t want to be able to do that at the moment.  So, I can disable that for now.  The top nav was the latest that I had from the FOLIO Marketing Meeting we attended on August 30th at EBSCO, but I can circle back and check that again.  &lt;/p&gt;</comment>
                                                            <comment id="189215" author="61cd0ca0bce5e00069e98be7" created="Mon, 6 Nov 2017 03:25:39 +0000"  >&lt;p&gt;Regarding my past comments about potential difficulty of maintenance.&lt;/p&gt;

&lt;p&gt;With the current theme we know exactly where the theme files come from and which version, i.e. presently classic-jekyll-theme v1.9.3 for our _layouts and _sass directories and other theme files. Any subsequent changes that we may need to make are then clearly documented in our revision control system. Any theme tweaks are isolated into our own SCSS files, etc. Also, when next the upstream theme files are modified, we can follow and update our copies accordingly to synchronise with the new version.&lt;/p&gt;</comment>
                                                            <comment id="189216" author="61cd0ca0bce5e00069e98be7" created="Mon, 6 Nov 2017 05:05:08 +0000"  >&lt;p&gt;In the classic-jekyll-theme, all of the CSS is a separate concern, so it is easy to modify. However this theme has CSS (e.g. for colors and font-sizes) mixed in with the layout and other things. Compare each: &lt;tt&gt;cd _includes; grep &quot;style=&quot; *.html&lt;/tt&gt;&lt;/p&gt;</comment>
                                                            <comment id="189220" author="5ced27478b03050f27825a93" created="Mon, 6 Nov 2017 16:24:24 +0000"  >&lt;blockquote&gt;&lt;p&gt;The &quot;Improve this Page&quot; was to be able to directly edit the pages in Github (not linked yet). Guessing we don&apos;t want to be able to do that at the moment. So, I can disable that for now. &lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Oh!  Okay.  I didn&apos;t see that as I was running Jekyll locally.  &lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;The top nav was the latest that I had from the FOLIO Marketing Meeting we attended on August 30th at EBSCO, but I can circle back and check that again.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Thanks for checking in with the web development team.  The latest version of the wireframes shown at the product council meeting last month had one additional pull-down list &amp;#8211; &quot;Overview&quot; &amp;#8211; to the left of &quot;Developers&quot;.  I think this is getting close to final, but I&apos;m at a loss to say how close.&lt;/p&gt;</comment>
                                                            <comment id="189223" author="5af5ea1ed95cfc55bfb76c8d" created="Mon, 6 Nov 2017 20:35:48 +0000"  >&lt;p&gt;Verifying the latest top nav from the FOLIO partners.  I will address the requests for the theme as well.&lt;/p&gt;</comment>
                                                            <comment id="189224" author="61cd0ca0bce5e00069e98be7" created="Tue, 14 Nov 2017 12:19:05 +0000"  >&lt;p&gt;I have done investigation to find the basis for this theme. It seems to be from &lt;a href=&quot;https://github.com/aksakalli/jekyll-doc-theme&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/aksakalli/jekyll-doc-theme&lt;/a&gt;&lt;/p&gt;</comment>
                                                            <comment id="189227" author="5af5ea1ed95cfc55bfb76c8d" created="Tue, 14 Nov 2017 16:29:18 +0000"  >&lt;p&gt;Yes, that is the theme that I showed to you guys in Ireland.  I thought it was closer to what the FOLIO partners might be looking for then, but does not satisfy our needs.  So, I used the pieces that I liked/could from that theme &amp;amp; the POC ended up being a combination of many things - theme pieces, organization via additional jekyll, and additional styling....whatever was needed to form an organized theme that suits the needs of the FOLIO partners.  Since using an existing theme out of the box will not work to align with the rest of the FOLIO suite of sites, we have to have a theme that will create the custom dev site that the FOLIO partners are looking for and organize the dev docs so that it is easy for a new developer to consume the docs.  If you have any pieces of other jekyll themes (left nav, top nav, etc) that you prefer that will align...just let me know and I can drop them into the POC to check it out.  I am looking at options other than accordion for left nav for the POC....just so we have it available if desired.  This week, I am finishing the adjustments to the POC for Peter&apos;s requests above.  I will comment back when I am finished &amp;amp; you can take a look and see what you think.&lt;/p&gt;</comment>
                                                            <comment id="189231" author="5ced27478b03050f27825a93" created="Tue, 14 Nov 2017 17:01:57 +0000"  >&lt;p&gt;Thanks for the pointer &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=61cd0ca0bce5e00069e98be7&quot; class=&quot;user-hover&quot; rel=&quot;61cd0ca0bce5e00069e98be7&quot; data-account-id=&quot;61cd0ca0bce5e00069e98be7&quot; accountid=&quot;61cd0ca0bce5e00069e98be7&quot; rel=&quot;noreferrer&quot;&gt;David Crossley&lt;/a&gt; &amp;#8211; interesting read.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5ea1ed95cfc55bfb76c8d&quot; class=&quot;user-hover&quot; rel=&quot;5af5ea1ed95cfc55bfb76c8d&quot; data-account-id=&quot;5af5ea1ed95cfc55bfb76c8d&quot; accountid=&quot;5af5ea1ed95cfc55bfb76c8d&quot; rel=&quot;noreferrer&quot;&gt;Patricia DeStefano&lt;/a&gt;: I think I read somewhere that GitHub Pages doesn&apos;t support custom Jekyll themes.  Is this going to push us towards generating the static HTML and serving it up somewhere other than GitHub pages?  If so, I&apos;m okay with that &amp;#8211; we need to get dev.folio.org onto a place with HTTPS support, and that isn&apos;t possible with a custom domain and GitHub pages.  Since we have other resources on AWS, I&apos;d be inclined to do something like &lt;a href=&quot;https://alexbilbie.com/2016/12/codebuild-codepipeline-update-jekyll-website/&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;Using AWS CodePipeline and CodeBuild to update a Jekyll website&lt;/a&gt;.  That mimics how GitHub Pages works, but gives us enough flexibility to customize and do HTTPS.&lt;/p&gt;</comment>
                                                            <comment id="189234" author="5af5ea1ed95cfc55bfb76c8d" created="Tue, 14 Nov 2017 23:54:22 +0000"  >&lt;p&gt;Hi &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;... You are correct.  GitHub pages only supports some gem based themes, but this is just a regular theme in our Jekyll directory.  More info here - &lt;a href=&quot;https://jekyllrb.com/docs/themes/&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://jekyllrb.com/docs/themes/&lt;/a&gt;  I can strip the folio specific docs out of the POC and publish just the un-built theme to my github pages to check it out that way.  I think that we are fine with deploying it to Github pages if desired, but your option to deploy it should definitely be looked at.&lt;/p&gt;</comment>
                                                            <comment id="190098" author="61cd0ca0bce5e00069e98be7" created="Wed, 15 Nov 2017 00:45:16 +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; any theme can be used. GitHub Pages has a set of basic themes that can be used automatically (e.g. when we started we were using &quot;minima&quot;). The theme that we are currently using is not from that set, but is &quot;classic-jekyll-theme&quot; (
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-789&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-789&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Investigate classic-jekyll-theme for use on 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-789
        &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 resolved&quot; data-jira-key=&quot;FOLIO-829&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-829&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Implement classic-jekyll-theme for dev.f.o phase 2&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-829
        &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 get GitHub to build it, we provide any necessary theme files by copying them into our repository.&lt;/p&gt;

&lt;p&gt;Yes there are other reasons that we might consider using a different infrastructure for building and deploying (see 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-832&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-832&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Build and deploy dev website via CI&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10307?size=medium&quot; /&gt;
            FOLIO-832
        &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 resolved&quot; data-jira-key=&quot;FOLIO-291&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-291&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;HTTPS access to developer website&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10322?size=medium&quot; /&gt;
            FOLIO-291
        &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="190099" author="61cd0ca0bce5e00069e98be7" created="Wed, 15 Nov 2017 00:46:08 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5ea1ed95cfc55bfb76c8d&quot; class=&quot;user-hover&quot; rel=&quot;5af5ea1ed95cfc55bfb76c8d&quot; data-account-id=&quot;5af5ea1ed95cfc55bfb76c8d&quot; accountid=&quot;5af5ea1ed95cfc55bfb76c8d&quot; rel=&quot;noreferrer&quot;&gt;Patricia DeStefano&lt;/a&gt; thanks for the explanation of the theme. I do recall your brief chance to demonstrate in Dublin. I have been asking since where it came from, as i am very concerned about ongoing maintenance and development, especially of a piecemeal theme. We are a small group and need to focus on content.&lt;/p&gt;</comment>
                                                            <comment id="190100" author="5af5ea1ed95cfc55bfb76c8d" created="Wed, 15 Nov 2017 03:43:39 +0000"  >&lt;p&gt;No problem &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=61cd0ca0bce5e00069e98be7&quot; class=&quot;user-hover&quot; rel=&quot;61cd0ca0bce5e00069e98be7&quot; data-account-id=&quot;61cd0ca0bce5e00069e98be7&quot; accountid=&quot;61cd0ca0bce5e00069e98be7&quot; rel=&quot;noreferrer&quot;&gt;David Crossley&lt;/a&gt;, but please base your investigations on what you see in the actual POC theme because it follows the layout/design that the FOLIO partners decided on.  I organized the POC theme keeping in mind both theme usage and the end result website design.  Please let me know if I can provide any further usage descriptions.  Yes, I agree, content is always the focus, but the larger group wants it organized differently and needs to see the navigation align with the rest of the sites. &lt;/p&gt;</comment>
                                                            <comment id="190101" author="5af5ea1ed95cfc55bfb76c8d" created="Thu, 16 Nov 2017 14:19:01 +0000"  >&lt;p&gt;I circled back to the web team and they sent me the latest top navigation wireframe from your product council meeting &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 attached it here with the new drop down open. &lt;span class=&quot;image-wrap&quot; style=&quot;&quot;&gt;&lt;img src=&quot;/rest/api/3/attachment/content/63988&quot; style=&quot;border: 0px solid black&quot; /&gt;&lt;/span&gt;&lt;/p&gt;

&lt;p&gt;I should have all your requests and the new top nav incorporated into the POC today.&lt;/p&gt;</comment>
                                                            <comment id="190102" author="5ced27478b03050f27825a93" created="Thu, 16 Nov 2017 14:47:40 +0000"  >&lt;p&gt;Perfect!  Thanks, &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5ea1ed95cfc55bfb76c8d&quot; class=&quot;user-hover&quot; rel=&quot;5af5ea1ed95cfc55bfb76c8d&quot; data-account-id=&quot;5af5ea1ed95cfc55bfb76c8d&quot; accountid=&quot;5af5ea1ed95cfc55bfb76c8d&quot; rel=&quot;noreferrer&quot;&gt;Patricia DeStefano&lt;/a&gt;!&lt;/p&gt;</comment>
                                                            <comment id="190103" author="5ced27478b03050f27825a93" created="Thu, 16 Nov 2017 19:57:25 +0000"  >&lt;p&gt;I&apos;m probably jumping the gun here &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5ea1ed95cfc55bfb76c8d&quot; class=&quot;user-hover&quot; rel=&quot;5af5ea1ed95cfc55bfb76c8d&quot; data-account-id=&quot;5af5ea1ed95cfc55bfb76c8d&quot; accountid=&quot;5af5ea1ed95cfc55bfb76c8d&quot; rel=&quot;noreferrer&quot;&gt;Patricia DeStefano&lt;/a&gt;, but I love the latest changes to your dev.folio.org branch.  The URLs are cleaner, and the left sidebar function is more intuitive.  &lt;/p&gt;</comment>
                                                            <comment id="190104" author="5af5ea1ed95cfc55bfb76c8d" created="Thu, 16 Nov 2017 20:04:12 +0000"  >&lt;p&gt;Finished the requests 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; and have pushed the changes to my fork.&lt;/p&gt;

&lt;p&gt;Assuming that you have jekyll installed, you can follow the instructions below to clone my fork and check it out:&lt;br/&gt;
clone the project - git clone &lt;a href=&quot;https://github.com/pdestefano/folio-org.github.io.git&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/pdestefano/folio-org.github.io.git&lt;/a&gt;&lt;br/&gt;
switch to the POC branch - git checkout folio-817-top-side-nav&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;

&lt;p&gt;Included in the changes:&lt;/p&gt;

&lt;p&gt;1 - When there is only one item in a section, I eliminated the accordion resulting in less clicks.   You can choose now in the yml if you would like an accordion heading or not.&lt;/p&gt;

&lt;p&gt;2 - Changed everything to black visited, etc. in the left hand nav.&lt;/p&gt;

&lt;p&gt;3 - Removed the reference to index in the subdirectories.  I agree, that was confusing.&lt;/p&gt;

&lt;p&gt;4 - Adjusted the top navigation to align with the FOLIO requirements - images changed a bit, added a drop down and right aligned the dev nav bar.&lt;/p&gt;

&lt;p&gt;5 - Removed the &quot;Improve this page&quot; link from the bottom of each page.&lt;/p&gt;

&lt;p&gt;Please let me know if you have any questions or anything else that you would like changed.&lt;/p&gt;</comment>
                                                            <comment id="190105" author="5af5ea1ed95cfc55bfb76c8d" created="Thu, 16 Nov 2017 20:33:42 +0000"  >&lt;p&gt;Thanks &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;!  Could you check the Overview links?  I know they will probably change as the other sites develop, but for now...let me know if you guys would like anything different there.  Also, the accordions in the left hand nav are beneficial for mobile devices because they save space, but to save clicks we could look at non accordion left hand nav to compare. I could place one left hand nav in a section as non accordion to see what all of you would like it better...could simplify it a bit if that is a concern.  Just let me know if you have any other changes that you would like me to include.    &lt;/p&gt;</comment>
                                                            <comment id="190106" author="61cd0ca0bce5e00069e98be7" created="Wed, 22 Nov 2017 14:43:38 +0000"  >&lt;p&gt;The left-hand menus do seem to be an improvement on your previous PoC.&lt;/p&gt;</comment>
                                                            <comment id="190107" author="61cd0ca0bce5e00069e98be7" created="Wed, 22 Nov 2017 14:44:19 +0000"  >&lt;p&gt;There is something that i find confusing with the documents now being individual pieces and having strange URLs. For example consider the &quot;Release procedures&quot; document. With the current site, we go to the whole document at &quot;/doc/release-procedures&quot; and go to a specific section, e.g. &quot;/doc/release-procedures#gradle-based-modules&quot;. With this PoC, we go to the initial part at &quot;/devguides/release-procedures/&quot; and to that other part at &quot;/devguides/gradle/&quot; (so it has lost the context of &quot;release-procedures&quot;). I would expect &quot;/devguides/release-procedures/gradle/&quot; etc.&lt;/p&gt;</comment>
                                                            <comment id="190108" author="61cd0ca0bce5e00069e98be7" created="Wed, 22 Nov 2017 14:45:32 +0000"  >&lt;p&gt;With the current site, we have a useful &quot;html/head/title&quot; for each page (it uses Liquid in _includes/head.html to compose that). For example &quot;FOLIO Developer | Release procedures&quot;.&lt;/p&gt;

&lt;p&gt;This has various benefits:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;When viewing the browser&apos;s &quot;Window&quot; menu for the list of open windows, it is easy to find the relevant one.&lt;/li&gt;
	&lt;li&gt;With multiple tabs in a browser window, can select the relevant one.&lt;/li&gt;
	&lt;li&gt;With Google search, the page title is used for the list of results.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;However with this PoC, there are multiple ones that just have &quot;FOLIO Developer | Introduction&quot;. Not sure how to fix that.&lt;/p&gt;</comment>
                                                            <comment id="190109" author="61cd0ca0bce5e00069e98be7" created="Wed, 22 Nov 2017 14:46:39 +0000"  >&lt;p&gt;With a usual browser window width of 1024px (e.g. GitHub size) then the top navbars do fit okay. We still need to add a &quot;Search&quot; menu. So maybe need one less, or perhaps change text of &quot;Getting Started&quot; to just &quot;Start&quot;, to make some room.&lt;/p&gt;

&lt;p&gt;Shrinking the browser window width just a little, then the top navbars expand to three lines. (The classic-jekyll-theme handles this better.) There is still horizontal space available, so i wonder if it can be better utilised.&lt;/p&gt;</comment>
                                                            <comment id="190110" author="61cd0ca0bce5e00069e98be7" created="Wed, 22 Nov 2017 14:47:08 +0000"  >&lt;p&gt;I am not expert at git-branch-and-merge. I wonder how we can get your branch (or branches) into the main repository so that they can be built with Peter&apos;s upcoming AWS build infrastructure (
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-832&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-832&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Build and deploy dev website via CI&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10307?size=medium&quot; /&gt;
            FOLIO-832
        &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="190111" author="5ced27478b03050f27825a93" created="Wed, 22 Nov 2017 15:18:17 +0000"  >&lt;p&gt;&amp;gt;  I am not expert at git-branch-and-merge. I wonder how we can get your branch (or branches) into the main repository so that they can be built with Peter&apos;s upcoming AWS build infrastructure (
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-832&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-832&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Build and deploy dev website via CI&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10307?size=medium&quot; /&gt;
            FOLIO-832
        &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;The way I&apos;m structuring it, the only thing that would be required is to create a branch on the folio-org/folio-org.github.io repository.  Patti: I think you have permissions to push a branch to that repo; if not, let me know and I can make that happen.&lt;/p&gt;</comment>
                                                            <comment id="190112" author="5af5ea1ed95cfc55bfb76c8d" created="Wed, 22 Nov 2017 18:55:26 +0000"  >&lt;p&gt;I am off most of today until Monday for the holiday, but just wanted to leave a quick comment.  I can look at all David&apos;s comments from today on the POC and accommodate and/or comment next week.  &lt;/p&gt;

&lt;p&gt;To get my branch into the main project repo -  In your local directory for the main project - I think that you guys can set a remote to my forked repo.  Then, pull my branch into your local directory for the main project repo.  Then, push my branch up to the main project repo.&lt;/p&gt;

&lt;p&gt;Happy Thanksgiving!&lt;/p&gt;</comment>
                                                            <comment id="190113" author="5ced27478b03050f27825a93" created="Mon, 27 Nov 2017 19:05:00 +0000"  >&lt;p&gt;The AWS-based system isn&apos;t quite ready yet.  I made it mostly to the end, but now I realize I have to back-track a little bit in order to get the GitHub Status API calls done efficiently/correctly.  (It means I&apos;m going to have to break up my existing all-in-one AWS Lambda into at least two parts.)  Hoping to have this ready this week.  Then we can bring &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5ea1ed95cfc55bfb76c8d&quot; class=&quot;user-hover&quot; rel=&quot;5af5ea1ed95cfc55bfb76c8d&quot; data-account-id=&quot;5af5ea1ed95cfc55bfb76c8d&quot; accountid=&quot;5af5ea1ed95cfc55bfb76c8d&quot; rel=&quot;noreferrer&quot;&gt;Patricia DeStefano&lt;/a&gt;&apos;s branch onto AWS.&lt;/p&gt;</comment>
                                                            <comment id="190114" author="5af5ea1ed95cfc55bfb76c8d" created="Fri, 1 Dec 2017 21:24:28 +0000"  >&lt;p&gt;It was mentioned that it would be desirable to have the secondary top navigation bar also collapse for mobile.  I put that functionality into the POC branch today and will push it up to my fork branch on Monday. &lt;/p&gt;</comment>
                                                            <comment id="190115" author="5ced27478b03050f27825a93" created="Mon, 4 Dec 2017 01:11:32 +0000"  >&lt;p&gt;Sounds good &amp;#8211; thanks, Patti.&lt;/p&gt;</comment>
                                                            <comment id="190116" author="5af5ea1ed95cfc55bfb76c8d" created="Mon, 4 Dec 2017 22:14:34 +0000"  >&lt;p&gt;Collapsing secondary top navigation is now in the POC branch.&lt;/p&gt;

&lt;p&gt;Assuming that you have jekyll installed, you can follow the instructions below to clone my fork and check it out:&lt;br/&gt;
clone the project - git clone &lt;a href=&quot;https://github.com/pdestefano/folio-org.github.io.git&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/pdestefano/folio-org.github.io.git&lt;/a&gt;&lt;br/&gt;
switch to the POC branch - git checkout folio-817-top-side-nav&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="190117" author="5ced27478b03050f27825a93" created="Mon, 4 Dec 2017 23:29:32 +0000"  >&lt;p&gt;Thanks, Patti.  Once I get 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-964&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-964&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Enable clean extension-less URLs&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10300?size=medium&quot; /&gt;
            FOLIO-964
        &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;
 done, I&apos;ll push up a branch to folio-org/folio-org.github.io containing your changes so it can get a broader audience.&lt;/p&gt;</comment>
                                                            <comment id="190118" author="5ced27478b03050f27825a93" created="Fri, 8 Dec 2017 21:20:34 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5ea1ed95cfc55bfb76c8d&quot; class=&quot;user-hover&quot; rel=&quot;5af5ea1ed95cfc55bfb76c8d&quot; data-account-id=&quot;5af5ea1ed95cfc55bfb76c8d&quot; accountid=&quot;5af5ea1ed95cfc55bfb76c8d&quot; rel=&quot;noreferrer&quot;&gt;Patricia DeStefano&lt;/a&gt;: I got your branch up on the main site.  I had to add `buildspec.yml` (for the AWS CodeBuild processor) and update `Gemfile.lock` in order to get it to build in AWS.  Those files are in the branch I pushed up to GitHub:  &lt;a href=&quot;https://github.com/folio-org/folio-org.github.io/tree/folio-817-top-side-nav&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/folio-org.github.io/tree/folio-817-top-side-nav&lt;/a&gt;&lt;/p&gt;</comment>
                                                            <comment id="190119" author="5af5ea1ed95cfc55bfb76c8d" created="Fri, 8 Dec 2017 22:24:14 +0000"  >&lt;p&gt;Thanks &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 think that the best link to get an idea is &lt;a href=&quot;http://folio-817-top-side-nav.dev.folio.org.s3-website-us-east-1.amazonaws.com/tutorials/foliocurriculumintro/&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;http://folio-817-top-side-nav.dev.folio.org.s3-website-us-east-1.amazonaws.com/tutorials/foliocurriculumintro/&lt;/a&gt; because the shorter sections need more content.  I mentioned that if you would like to use the left hand navigation to go up and down one page instead of page to page, we can try that...seems like it might be a good compromise.  It would require some more work on my POC, but if you would like to try it...let me know and I will check here.&lt;/p&gt;</comment>
                                                            <comment id="190120" author="5ced27478b03050f27825a93" created="Mon, 11 Dec 2017 17:03:09 +0000"  >&lt;p&gt;Please take a look at that, Patti.  The overwhelming number of comments seem to favor longer pages with a table-of-contents widget over more shorter pages.&lt;/p&gt;</comment>
                                                            <comment id="190121" author="5af5ea1ed95cfc55bfb76c8d" created="Mon, 11 Dec 2017 22:53:42 +0000"  >&lt;p&gt;Sure Peter.  Just commented in Slack as well...I did not have navigation up and down the page, but figured every visible section in the POC would be full of content...sorry if that was not clear in the POC...I was basically creating the theme &amp;amp; only divided the content...did not add any.  I think that looking at the tiny pages might have threw people off...those were intended to be full of content.  I think that I can accommodate everyone. &lt;img class=&quot;emoticon&quot; src=&quot;/images/icons/emoticons/smile.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt;&lt;/p&gt;

&lt;p&gt;My proposal at this point...So, the secondary navigation bar serves as the toc headers...so, I will leave that for now. In each toc section (Getting Started, Guides, etc), I will make the shorter pages into longer and change the sidebar to be fixed and navigate up and down the longer section. I can play with putting the toc headers from the secondary nav bar into the sidebar as well if we desire, but if we already have them in the secondary nav bar it might be a bit redundant.  I also just put the search back in for the entire project...I put it back in as search box directly in the secondary nav bar.  So, the secondary nav serves another purpose as well.  I have not pushed that to my branch yet, but will.&lt;/p&gt;</comment>
                                                            <comment id="190122" author="61cd0ca0bce5e00069e98be7" created="Tue, 12 Dec 2017 04:52:04 +0000"  >&lt;p&gt;I do not think that it was the tiny content of some pages being misleading for people. They much prefer using one page per topic.&lt;/p&gt;

&lt;p&gt;Please be careful adding extra actual content to this PoC at this stage.&lt;/p&gt;</comment>
                                                            <comment id="190123" author="61cd0ca0bce5e00069e98be7" created="Mon, 18 Dec 2017 03:50:14 +0000"  >&lt;p&gt;The demonstration is at &lt;a href=&quot;http://folio-817-top-side-nav.dev.folio.org.s3-website-us-east-1.amazonaws.com&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;folio-817-top-side-nav&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;(Not meaning to rush you with any pending improvements, just updating all related issues.)&lt;/p&gt;</comment>
                                                            <comment id="190124" author="5af5ea1ed95cfc55bfb76c8d" created="Sat, 6 Jan 2018 02:25:48 +0000"  >&lt;p&gt;Have been making updates for the left hand menu to the forked version:&lt;/p&gt;

&lt;p&gt;clone the project - git clone &lt;a href=&quot;https://github.com/pdestefano/folio-org.github.io.git&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/pdestefano/folio-org.github.io.git&lt;/a&gt;&lt;br/&gt;
switch to the POC branch - git checkout folio-817-top-side-nav&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="190125" author="61cd0ca0bce5e00069e98be7" created="Tue, 9 Jan 2018 06:56:32 +0000"  >&lt;p&gt;There are many changes in one commit, so it is difficult to keep up. I provide some comments below.&lt;/p&gt;

&lt;p&gt;I do appreciate your efforts.&lt;/p&gt;</comment>
                                                            <comment id="190126" author="61cd0ca0bce5e00069e98be7" created="Tue, 9 Jan 2018 06:58:10 +0000"  >&lt;p&gt;I had been trying to use a minimum of JavaScript. Now there is lots. (But okay if that is what is needed.)&lt;/p&gt;

&lt;p&gt;I am concerned that this is using a very old version of &quot;jquery-ui&quot;.&lt;/p&gt;

&lt;p&gt;Also the &quot;tocify&quot; seems to be a non-responsive and old repository. I had considered it a while ago, but stopped. Following some of its open issues led to the stand-alone &quot;tocbot&quot; instead (see some investigation in our &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-978&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;FOLIO-978&lt;/a&gt;).&lt;/p&gt;</comment>
                                                            <comment id="190127" author="5af5ea1ed95cfc55bfb76c8d" created="Tue, 9 Jan 2018 22:07:28 +0000"  >&lt;p&gt;Sure, I can address your concerns and look at versions, options for toc generation etc.  I am just in the midst of getting this version completely styled, adding the new requested functionality and latest content.  As soon as I am finished with that, I will move onto your concerns as well.&lt;/p&gt;</comment>
                                                            <comment id="190128" author="61cd0ca0bce5e00069e98be7" created="Wed, 24 Jan 2018 07:42:37 +0000"  >&lt;p&gt;Today i updated the master to incorporate the changes from 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-978&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-978&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Investigate solutions for page table-of-contents 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-978
        &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;
 (using tocbot and using fixed header). The main changes that might affect your PoC fork are:&lt;/p&gt;

&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
_config.yml (minor)
_includes/head.html (minor)
_includes/footer.html (minor)
_layouts/page.html (&lt;span class=&quot;code-keyword&quot;&gt;new&lt;/span&gt;)
_sass/_folio.scss
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;No changes to Gemfile.&lt;/p&gt;

&lt;p&gt;The directory &lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;_sass/classic/&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt; is not needed since early December, as we use &quot;jekyll-remote-theme&quot; plugin.&lt;/p&gt;

&lt;p&gt;Updates to actual content are minor, mostly related to frontmatter for that theme&apos;s menus.&lt;/p&gt;</comment>
                                                            <comment id="190129" author="5af5ea1ed95cfc55bfb76c8d" created="Wed, 24 Jan 2018 21:20:01 +0000"  >&lt;p&gt;Thanks for the update.  I should have two POC branches pushed up to my fork tomorrow with my updates.&lt;/p&gt;</comment>
                                                            <comment id="190130" author="61cd0ca0bce5e00069e98be7" created="Thu, 25 Jan 2018 04:54:33 +0000"  >&lt;p&gt;Beaut, thanks. I will be away for the next few days, so will investigate next week.&lt;/p&gt;</comment>
                                                            <comment id="190131" author="5af5ea1ed95cfc55bfb76c8d" created="Thu, 25 Jan 2018 22:01:11 +0000"  >&lt;p&gt;I have pushed up a new POC branch to my fork.  &lt;/p&gt;

&lt;p&gt;Assuming that you have jekyll installed, you can follow the instructions below to 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-org.github.io.git&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/pdestefano/folio-org.github.io.git&lt;/a&gt;&lt;br/&gt;
switch to the POC branch once in the project - git checkout folio-817-hor-vert-navb&lt;br/&gt;
***&lt;b&gt;Note&lt;/b&gt;***- please make sure you have a &lt;font color=&quot;red&quot;&gt;b&lt;/font&gt; on the end of the branch name or you will get the wrong branch&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;

&lt;p&gt;POC folio-817-hor-vert-navb Branch Summary:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Fixed top and dev navigation&lt;/li&gt;
	&lt;li&gt;Top navigation styled and aligns with partner requests&lt;/li&gt;
	&lt;li&gt;Uses tocbot for left navigation&lt;/li&gt;
	&lt;li&gt;Responsive - responsive left menu appears and disappears with the click of the orange menu button...this can really be done any way desired, but thought this was a simple solution that looked decent for now.&lt;/li&gt;
	&lt;li&gt;Search in the top navigation bar - results appear at the top of the page above the current content (responsive as well)&lt;/li&gt;
	&lt;li&gt;Multipage support in the left navigation&lt;/li&gt;
	&lt;li&gt;Support for lengthy left hand navigation&lt;/li&gt;
	&lt;li&gt;The latest content is included - just chunked differently into the different categories.  I did not change any wording.  Just divided the sections into the different categories.  This can be done any way that is desired.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;A little about the custom theme/framework...&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Content is divided into categories on the dev navigation bar - can be changed to whatever is desired.  Each category corresponds to a folder in the jekyll site.  So, content is neatly divided into markdown files in topic/category folders for easy editing...makes it easier for a novice to find just the content and not worry about the framework.&lt;/li&gt;
	&lt;li&gt;Each category has left hand navigation.  Every content file in the category folder is represented in the left hand navigation - as mentioned above...support for multipage left hand navigation (guides and guidelines categories).&lt;/li&gt;
	&lt;li&gt;Little to no styling/theme (top matter) in the content markdown - editing content is just content...no worrying about the theme when you just need access to the content.&lt;/li&gt;
	&lt;li&gt;I can fully describe the framework/theme in a future document if desired...&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;I can make my other POC branch using tocify look and function the same as this branch using tocbot if desired.  Since it seems that tocbot is preferred, I decided not to take the time to update the tocify branch unless it is desired.&lt;/p&gt;

&lt;p&gt;Please let me know if you have any questions.&lt;/p&gt;
</comment>
                                                            <comment id="190133" author="61cd0ca0bce5e00069e98be7" created="Tue, 30 Jan 2018 15:07:04 +0000"  >&lt;p&gt;Thanks. This is much improved. The navigation presentation is more compact, now fitting the ideal browser window width.&lt;/p&gt;

&lt;p&gt;I do have some general concerns about CSS style, but will leave those until later (e.g. in-line code elements are too emphatic; lost API table formatting; why coloured headings).&lt;/p&gt;

&lt;p&gt;Not expecting all of the following items to be fixed in this proof-of-concept. But we do need to be sure that they can be handled.&lt;/p&gt;</comment>
                                                            <comment id="190135" author="61cd0ca0bce5e00069e98be7" created="Tue, 30 Jan 2018 15:07:56 +0000"  >&lt;p&gt;The once-separate documents are being merged into single large documents (e.g. into /reference/refinfo/ and /guidelines/communityguidelines/ etc.). I reckon that that will not be as useable, regarding: browsing, referencing, maintenance, and searching.&lt;/p&gt;

&lt;p&gt;For example, the separate pages &lt;a href=&quot;http://dev.folio.org/doc/glossary/&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;FOLIO Glossary&lt;/a&gt; and &lt;a href=&quot;http://dev.folio.org/doc/api/&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;API documentation&lt;/a&gt; are being merged into &quot;_reference/refinfo.md&quot;&lt;/p&gt;

&lt;p&gt;Is there a reason for such amalgamation, or perhaps it is just to demonstrate theme ability?&lt;/p&gt;</comment>
                                                            <comment id="190137" author="61cd0ca0bce5e00069e98be7" created="Tue, 30 Jan 2018 15:08:35 +0000"  >&lt;p&gt;Tutorials:&lt;/p&gt;

&lt;p&gt;Need the infrastructure for multiple tutorials, and each potentially having multiple pages (see 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-984&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-984&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Merge curriculum into dev.folio.org site&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-984
        &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="190138" author="61cd0ca0bce5e00069e98be7" created="Tue, 30 Jan 2018 15:09:34 +0000"  >&lt;p&gt;Each directory is missing its landing page, e.g. /reference/ and /tutorials/ etc. Each needs an index.html&lt;/p&gt;</comment>
                                                            <comment id="190139" author="61cd0ca0bce5e00069e98be7" created="Tue, 30 Jan 2018 15:10:16 +0000"  >&lt;p&gt;We have some documents that are not linked into the navigation menus, yet should appear to belong to a certain area of the site. For example, &lt;a href=&quot;http://dev.folio.org/doc/code-analysis/&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;http://dev.folio.org/doc/code-analysis/&lt;/a&gt; has the &quot;Documentation&quot; area highlighted at the top and left-hand navigation menus.&lt;/p&gt;

&lt;p&gt;(That is actually not a good example, as it will get linked to the menus when the re-arrangement happens. But this does show the feature.)&lt;/p&gt;

&lt;p&gt;As we get even more documents, they will not all be able to be linked as part of the menus, but need this indication of which section they belong to.&lt;/p&gt;

&lt;p&gt;Is this theme able to handle such?&lt;/p&gt;</comment>
                                                            <comment id="190140" author="61cd0ca0bce5e00069e98be7" created="Tue, 30 Jan 2018 15:11:25 +0000"  >&lt;p&gt;Search:&lt;/p&gt;

&lt;p&gt;Inserting the results panel onto the current page seems strange.&lt;/p&gt;

&lt;p&gt;Search box is fiddly.&lt;/p&gt;

&lt;p&gt;Why not just use a separate page, as with the current site? This enables results to be clearly listed. It also enables search instructions to be provided.&lt;/p&gt;

&lt;p&gt;Lost the other search page which provides various GitHub searches. Also later we expect to have various different searches, e.g. using GraphQL.&lt;/p&gt;

&lt;p&gt;So need the infrastructure to enable separate additional search pages.&lt;/p&gt;</comment>
                                                            <comment id="190141" author="61cd0ca0bce5e00069e98be7" created="Tue, 30 Jan 2018 15:11:57 +0000"  >&lt;p&gt;Lost the ability to run the bin/htmlproofer.sh facility. Locally restored it in Gemfile. It does report new issues.&lt;/p&gt;</comment>
                                                            <comment id="190142" author="61cd0ca0bce5e00069e98be7" created="Tue, 30 Jan 2018 15:14:43 +0000"  >&lt;p&gt;I do have concerns about maintenance. With the current classic-jekyll-theme we have a minimum of extra stuff to maintain. With this theme we have much more.&lt;/p&gt;

&lt;p&gt;There is lots of use of &quot;style&quot; attributes in html markup, rather than separation of CSS.&lt;/p&gt;

&lt;p&gt;There is code duplication in &quot;_layouts&quot; and &quot;_includes&quot;.&lt;/p&gt;

&lt;p&gt;Is there a need to have a copy of Bootstrap in the _sass directory?&lt;/p&gt;</comment>
                                                            <comment id="190143" author="5ced27478b03050f27825a93" created="Tue, 30 Jan 2018 20:51:14 +0000"  >&lt;p&gt;I pushed this up to the main GitHub repo as a branch, which caused a version of it to build on AWS: &lt;a href=&quot;http://folio-817-hor-vert-navb.dev.folio.org.s3-website-us-east-1.amazonaws.com/&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;http://folio-817-hor-vert-navb.dev.folio.org.s3-website-us-east-1.amazonaws.com/&lt;/a&gt;.  Note that a &lt;a href=&quot;https://github.com/folio-org/folio-org.github.io/commit/3e8edd09e882df47c5126d35f527de609b5a3cdb&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;change to Gemfile.lock&lt;/a&gt; was required.&lt;/p&gt;</comment>
                                                            <comment id="190144" author="5af5ea1ed95cfc55bfb76c8d" created="Tue, 30 Jan 2018 21:55:36 +0000"  >&lt;p&gt;Thanks for taking a look...  I can address all of your concerns...here are a few...will try to get to more tomorrow.  I was under a time constraint...so I don&apos;t think inline CSS should be of concern in the short term.  The CSS can be more streamlined and pulled external if you decide to use this.  _layouts and _includes directories are the way they are meant to be.  Each category has its own layout so that if down the road you would like a different layout for each category, you have that flexibility.  The _includes directory contains portions of each layout... header, footer and navigation.  Since there are other link checkers out there, I removed html-proofer because it caused an error in my environment when building.  I work on a windows machine and libcurl is not by default installed.  html-proofer depends on typhoneous which depends on libcurl.  So, anyone trying to build the project on windows and has not already installed libcurl will hit an error.  Any dependency that goes back to libcurl will cause a windows developer to hit an error if they have not previously installed libcurl - jekyll-remote-theme also depends on libcurl being installed on your machine.  Just wanted to mention why I removed it...thought it would be simpler for a windows developer because there are other options...but easy to add back if desired.  Will try to answer more for you tomorrow...thanks!&lt;/p&gt;</comment>
                                                            <comment id="190145" author="5af5ea1ed95cfc55bfb76c8d" created="Tue, 30 Jan 2018 21:59:40 +0000"  >&lt;p&gt;Thank you &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;/p&gt;</comment>
                                                            <comment id="190146" author="61cd0ca0bce5e00069e98be7" created="Wed, 31 Jan 2018 01:11:08 +0000"  >&lt;p&gt;FOLIO developers would generally need &apos;curl&apos; anyway. So will add a note to this README.&lt;/p&gt;</comment>
                                                            <comment id="190147" author="5af5ea1ed95cfc55bfb76c8d" created="Fri, 2 Feb 2018 21:14:05 +0000"  >&lt;p&gt;Just wanted to address the rest of your concerns.  Color and table formatting can be changed to whatever preferred.  Bootstrap is used for styling.  I put the Glossary and API docs together in one page because they are both reference, demonstrate capability and you guys were desiring longer pages.  They can easily be separated into separate pages like the guide section.  For the tutorial section, I adjusted it so that you can have each tutorial title as the 1st level heading and each tutorial can have multiple pages (lessons) underneath (might be overkill for the other sections).  I have attached an image that makes that easier to see (
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-984&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-984&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Merge curriculum into dev.folio.org site&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-984
        &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;
 refers to this).  I have not pushed this to the fork yet because I was not sure that we needed that functionality at this time.  The one tutorial already in there seems fine on one page, but I can push up what I have in the attached picture if it is desired &lt;span class=&quot;image-wrap&quot; style=&quot;&quot;&gt;&lt;a id=&quot;63991_thumb&quot; href=&quot;/rest/api/3/attachment/content/63991&quot; title=&quot;tutorials.png&quot; file-preview-type=&quot;image&quot; file-preview-id=&quot;63991&quot; file-preview-title=&quot;tutorials.png&quot;&gt;&lt;jira-attachment-thumbnail url=&quot;https://folio-org.atlassian.net/rest/api/3/attachment/thumbnail/63991?default=false&quot; jira-url=&quot;https://folio-org.atlassian.net/rest/api/3/attachment/thumbnail/63991&quot; filename=&quot;tutorials.png&quot;&gt;&lt;img src=&quot;https://folio-org.atlassian.net/rest/api/3/attachment/thumbnail/63991&quot; data-attachment-name=&quot;tutorials.png&quot; data-attachment-type=&quot;thumbnail&quot; data-media-services-id=&quot;e60505cd-408e-44a5-aa02-715969c6b7d0&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;  Yes, if you have a page that is not in the left hand nav, you can still put it in the top nav category and the section will be highlighted.  Yes, you could put the search on a separate page...or just have the other searches on another page.  I just did it that way because most others do - &lt;a href=&quot;https://developers.google.com/style/tone&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://developers.google.com/style/tone&lt;/a&gt;, &lt;a href=&quot;https://developers.facebook.com/docs/apps&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://developers.facebook.com/docs/apps&lt;/a&gt;, etc  I think that is everything...have a good weekend!&lt;/p&gt;</comment>
                                                            <comment id="190148" author="61cd0ca0bce5e00069e98be7" created="Sat, 3 Feb 2018 02:33:22 +0000"  >&lt;p&gt;I realise that Bootstrap is used for styling. As part of my drive to ease maintenance, i was wondering if we need to carry a copy of its stuff (unless needing to deeply over-ride something). Could it be obtained via CDN.&lt;/p&gt;</comment>
                                                            <comment id="190149" author="61cd0ca0bce5e00069e98be7" created="Sat, 3 Feb 2018 02:34:02 +0000"  >&lt;p&gt;Regarding separate Tutorials each with potentially separate pages:&lt;br/&gt;
Great, thanks for verifying that this theme can handle that &amp;#8211; multi-page or single page as needed.&lt;/p&gt;

&lt;p&gt;We urgently need to move the old multi-page Curriculum (
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-984&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-984&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Merge curriculum into dev.folio.org site&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-984
        &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;
) as it is holding up the move to our new website building infrastructure (
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-832&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-832&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Build and deploy dev website via CI&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10307?size=medium&quot; /&gt;
            FOLIO-832
        &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 have almost finished doing that.&lt;/p&gt;</comment>
                                                            <comment id="190150" author="61cd0ca0bce5e00069e98be7" created="Sat, 3 Feb 2018 02:36:05 +0000"  >&lt;blockquote&gt;
&lt;p&gt;I put the Glossary and API docs together in one page because they are both reference, demonstrate capability and you guys were desiring longer pages. They can easily be separated into separate pages like the guide section. &lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;No, we were not actually &quot;desiring longer pages&quot;. The reason for the poll at 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-975&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-975&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Poll developers for style of breaking up content on pages&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-975
        &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;
 was in response to your proposal to split existing pages into small chunks, each as a separate page. That chunking is not wanted in general. We want separate pages per topic, with longer content when needed. Not to amalgamate separate pages into longer ones. Sure, the chunking can be relevant in certain situations.&lt;/p&gt;

&lt;p&gt;So for example, the &quot;Reference&quot; section should remain as separate pages.&lt;/p&gt;

&lt;p&gt;I raised this a number of times because i wondered if there was a misunderstanding.&lt;/p&gt;</comment>
                                                            <comment id="190151" author="5af5ea1ed95cfc55bfb76c8d" created="Wed, 14 Feb 2018 21:37:51 +0000"  >&lt;p&gt;Hello - I am going on vacation and will return to the office Feb 26th.  I probably will not be able to respond to JIRA comments until then.  This afternoon, I updated the content, incorporated faqs and separated the reference back into two pages - API Specifications and Glossary.  I put the FAQs under the Get Started section for now.  I have pushed the changes up to my POC branch below.&lt;/p&gt;

&lt;p&gt;Assuming that you have jekyll installed, you can follow the instructions below to 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-org.github.io.git&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/pdestefano/folio-org.github.io.git&lt;/a&gt;&lt;br/&gt;
switch to the POC branch once in the project - git checkout folio-817-hor-vert-navb&lt;br/&gt;
**&lt;b&gt;Note&lt;/b&gt;**- please make sure you have a b on the end of the branch name or you will get the wrong branch&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="190152" author="5af5ea1ed95cfc55bfb76c8d" created="Tue, 3 Apr 2018 20:25:44 +0000"  >&lt;p&gt;Hello - I received an updated top nav from the UX team here at EBSCO.   It is mainly added images, color and font.  Not sure if &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; has received the details as well, but wanted to update the top nav template on this issue to the latest.  So, attached is the latest top nav that they would like carried through all of the FOLIO sites for consistency and alignment.  The responsive behavior of the top nav is slightly different than I had anticipated.  I have aligned the POC branch to function according to the attached wireframes.  You can try it out by following the instructions below.  I have also included some screen shots of the POC included with the top nav ux wireframes.  While I was in there, I also synced the POC branch with the latest content in the folio master branch (events page, video, raml-cop guide in the guide section, latest tocbot, etc.).  &lt;/p&gt;

&lt;p&gt;clone the project - git clone&#160;&lt;a href=&quot;https://github.com/pdestefano/folio-org.github.io.git&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/pdestefano/folio-org.github.io.git&lt;/a&gt;&lt;br/&gt;
switch to the POC branch once in the project - git checkout folio-817-hor-vert-navb&lt;br/&gt;
*&lt;b&gt;Note&lt;/b&gt;*- please make sure you have a b on the end of the branch name or you will get the wrong branch&lt;br/&gt;
build it - bundle exec jekyll serve&lt;br/&gt;
try it - browse to&#160;&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;

&lt;p&gt;&lt;span class=&quot;image-wrap&quot; style=&quot;&quot;&gt;&lt;a id=&quot;63990_thumb&quot; href=&quot;/rest/api/3/attachment/content/63990&quot; title=&quot;topnavv2.png&quot; file-preview-type=&quot;image&quot; file-preview-id=&quot;63990&quot; file-preview-title=&quot;topnavv2.png&quot;&gt;&lt;jira-attachment-thumbnail url=&quot;https://folio-org.atlassian.net/rest/api/3/attachment/thumbnail/63990?default=false&quot; jira-url=&quot;https://folio-org.atlassian.net/rest/api/3/attachment/thumbnail/63990&quot; filename=&quot;topnavv2.png&quot;&gt;&lt;img src=&quot;https://folio-org.atlassian.net/rest/api/3/attachment/thumbnail/63990&quot; data-attachment-name=&quot;topnavv2.png&quot; data-attachment-type=&quot;thumbnail&quot; data-media-services-id=&quot;cab77a33-c3a5-4511-ba76-c06c3d18ab60&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;span class=&quot;image-wrap&quot; style=&quot;&quot;&gt;&lt;a id=&quot;63989_thumb&quot; href=&quot;/rest/api/3/attachment/content/63989&quot; title=&quot;topnavmobile.png&quot; file-preview-type=&quot;image&quot; file-preview-id=&quot;63989&quot; file-preview-title=&quot;topnavmobile.png&quot;&gt;&lt;jira-attachment-thumbnail url=&quot;https://folio-org.atlassian.net/rest/api/3/attachment/thumbnail/63989?default=false&quot; jira-url=&quot;https://folio-org.atlassian.net/rest/api/3/attachment/thumbnail/63989&quot; filename=&quot;topnavmobile.png&quot;&gt;&lt;img src=&quot;https://folio-org.atlassian.net/rest/api/3/attachment/thumbnail/63989&quot; data-attachment-name=&quot;topnavmobile.png&quot; data-attachment-type=&quot;thumbnail&quot; data-media-services-id=&quot;e2650dc2-eddd-471c-96ce-99dc5a12f4dd&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;</comment>
                                                            <comment id="190153" author="5ced27478b03050f27825a93" created="Wed, 4 Apr 2018 15:37:42 +0000"  >&lt;p&gt;Hi!  I&apos;ve seen the mockups, but I haven&apos;t seen the implementation-in-code yet.  I think I found it in your branch: &lt;a href=&quot;https://github.com/pdestefano/folio-org.github.io/blob/folio-817-hor-vert-navb/_includes/topnav.html&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/pdestefano/folio-org.github.io/blob/folio-817-hor-vert-navb/_includes/topnav.html&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I&apos;m hoping for something that is a standalone fragment of HTML5 that I can plug into the various web properties...use in-line CSS styles and base64-encode images and the like.  That way it can get added/updated as a unit without having to worry about external dependencies.  That might be unrealistic, but it seems like a good goal to strive towards.  Is there JavaScript required for the nav bar on your branch?  I can&apos;t quite determine that from the browser inspector.&lt;/p&gt;</comment>
                                                            <comment id="190154" author="5af5ea1ed95cfc55bfb76c8d" created="Thu, 5 Apr 2018 18:10:43 +0000"  >&lt;p&gt;Hi &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 understand what you are looking for.  I used a bootstrap navbar - it provides alignment for different pieces of the nav bar, styling and responsive behavior.  So, you need to include the bootstrap required js and css.  Yes, topnav.html.  It is separate from the markdown content.  So, it could be replaced with a different nav bar without affecting the structure or content, but it would take some work to get a new nav bar to match the style and responsive behavior of the bootstrap nav bar.  You could also try to use the bootstrap bar without the javascript&#8230;would require some work and more css.  I think that the EBSCO marketing group is starting to implement the same thing for the top of the general site now.  I am not sure how they are going to generate the site (wordpress or the like&#8230;or custom?).  They are aiming for the same bar as well, but they are not using a static site generator as far as I know&#8230;so, guessing they will do it differently.  Maybe what they come up with could be an option for you? &lt;/p&gt;</comment>
                                                            <comment id="190155" author="5ced27478b03050f27825a93" created="Thu, 5 Apr 2018 18:21:29 +0000"  >&lt;p&gt;The FOLIO marketing team is meeting right now, and I wanted to show what the navbar plan looks like at the moment, so I pushed your branch to the `folio-org` organization, which generated this: &lt;a href=&quot;http://folio-817-hor-vert-navb.dev.folio.org.s3-website-us-east-1.amazonaws.com/&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;http://folio-817-hor-vert-navb.dev.folio.org.s3-website-us-east-1.amazonaws.com/&lt;/a&gt;&lt;/p&gt;</comment>
                                                            <comment id="190156" author="5af5ea1ed95cfc55bfb76c8d" created="Thu, 5 Apr 2018 19:02:49 +0000"  >&lt;p&gt;Sounds good.  Thanks...let me know if I can be of help.&lt;/p&gt;</comment>
                                                            <comment id="190157" author="62a96ae7192edb006f9f1bf9" created="Tue, 21 Aug 2018 19:16:12 +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; and &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5ea1ed95cfc55bfb76c8d&quot; class=&quot;user-hover&quot; rel=&quot;5af5ea1ed95cfc55bfb76c8d&quot; data-account-id=&quot;5af5ea1ed95cfc55bfb76c8d&quot; accountid=&quot;5af5ea1ed95cfc55bfb76c8d&quot; rel=&quot;noreferrer&quot;&gt;Patricia DeStefano&lt;/a&gt;, should this user story remain open? &lt;/p&gt;</comment>
                                                            <comment id="190158" author="61cd0ca0bce5e00069e98be7" created="Wed, 22 Aug 2018 06:45:53 +0000"  >&lt;p&gt;Ah sorry &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=62a96ae7192edb006f9f1bf9&quot; class=&quot;user-hover&quot; rel=&quot;62a96ae7192edb006f9f1bf9&quot; data-account-id=&quot;62a96ae7192edb006f9f1bf9&quot; accountid=&quot;62a96ae7192edb006f9f1bf9&quot; rel=&quot;noreferrer&quot;&gt;Khalilah Gambrell&lt;/a&gt; there are a number of old related issues that i still need to tidy and close.&lt;/p&gt;

&lt;p&gt;Yes this investigation is finished. The current theme is satisfactory 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-829&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-829&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Implement classic-jekyll-theme for dev.f.o phase 2&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-829
        &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;
. The common top navigation bar 
    &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;
 is added to the various sites. The improved navigation is implemented 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-646&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-646&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Implement improved navigation dev.f.o phase 2&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-646
        &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>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                                                <inwardlinks description="is blocked by">
                                        <issuelink>
            <issuekey id="80437">FOLIO-975</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="80249">FOLIO-644</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="63988" name="topnav.png" size="32070" author="5af5ea1ed95cfc55bfb76c8d" created="Thu, 16 Nov 2017 14:15:53 +0000"/>
                            <attachment id="63989" name="topnavmobile.png" size="120947" author="5af5ea1ed95cfc55bfb76c8d" created="Tue, 3 Apr 2018 20:22:21 +0000"/>
                            <attachment id="63990" name="topnavv2.png" size="91685" author="5af5ea1ed95cfc55bfb76c8d" created="Tue, 3 Apr 2018 20:22:08 +0000"/>
                            <attachment id="63991" name="tutorials.png" size="54217" author="5af5ea1ed95cfc55bfb76c8d" created="Fri, 2 Feb 2018 20:35:53 +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|hzxyiv:</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>Tue, 12 Sep 2017 16:59:39 +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>