pixeldroid / programming-pages Goto Github PK

The links listed under Template-Features#content-layouts are broken:
http://pixeldroid.com/programming-pages/guides/Template-Features/#content-layouts

clicking on a footnote forward link or backlink results in the following javascript error:

Uncaught Error: Syntax error, unrecognized expression: unsupported pseudo:

the parent layout section is incomplete:
https://github.com/pixeldroid/programming-pages/blob/master/lib/src/_layouts/layout.md#parent-layout

see

when ordering guides arbitrarily (non-alphabetically) using the order variable, children get assigned incorrectly to parents in the indices view.

expecting:

├─P1
├──P1C1
├──P1C2
├──P1C3
├─P2
└─P3

seeing:

├─P1
├──P1C1
├─P2
├──P1C2
├──P1C3
└─P3

in /guides/Theme-Features/, the id #collection-indices refers to both a div in the side nav and a section on the page.

currently all icons are included whether used or not; consider instead a liquid macro that pulls icons at build time, taking care of the html/svg/css.

also consider returning svg ids to the names found in the icon libraries themselves (maybe an alias to translate the programming-pages intentions back to library ids: interface → neuter)

e.g., instead of this:

<svg class="icon"><use xlink:href="#icon-folder-outline" /></svg>

something like this:

{% include icon.liquid icon=folder-o %}

the footnote backlink arrow (⮌) is rendering as a missing character on mobile, but not on desktop

⮌ U+2B8C: ANTICLOCKWISE TRIANGLE-HEADED RIGHT U-SHAPED ARROW

chrome browser in both cases.

code listings are given a width of fit-content, and provide horizontal scrolling for overflow. but if they are inside a table, the table will stretch and the parent container will overflow, preventing horizontal scoll access.

to repro, visit the url below and shrink the viewport width:
https://pixeldroid.github.io/programming-pages/layout_api/layout/#/layout_api/

examples (browse in mobile or tighten the browser window width to see):

• https://pixeldroid.com/programming-pages/examples/sampler/#links
• https://pixeldroid.com/programming-pages/layout_api/package/#/layout_api/

while a _sass folder was added to source control in 7d13135, the folder was not added to the gemspec and doesn't get packaged into the gem or zip release artifacts.

would be nice if the collection tabs could be arbitrarily ordered; currently they are always sorted alphabetically

for in-page links generated by kramdown auto_id like this:
http://pixeldroid.com/programming-pages/guides/Template-Features/#title-bar

the section is scrolled to the top of the page, beneath the title bar, where it is covered.

Dear pixeldroid,
thanks for this nice theme! I'm trying to set up a small github.io website but the rendering of the navigation pane is not nice when using Firefox (when more than 3 collections, the 1st sub element name is cut, see github.io.png). The rendering is fine (see local.png) using Firefox and local page done with jekyll serve. The github.io website is OK using Chromium or Falkon. So this is only using Github server and Firefox that I have the problem... Is there a way to avoid that? Maybe, to increase artificially the space between the collections and the sub elements? Thanks for you help!

According to the docs:

Positive numbers will be sorted first, in ascending order, with 0 the first possible value. Negative numbers will be sorted last, in descending order, with -1 the last possible integer value:

 🡯first      last🡮
0 1 2 3  .. -3 -2 -1

but as of v0.5.11, setting two pages to be ordered -1 and -2 makes -2 the last (should be -1).

perhaps when adding to the endered array, the negative values should be shifted, not pushed? (see indices.html#L110)

lib/src/_config.yml defines several '_root' shortcuts, but these are tightly coupled to folder names, which we want the user to be in control of. maybe these references can be removed, or at least auto-gen'd.

visual defect; see screenshot:

the Authoring Documentation page is missing info and warning icons:
http://pixeldroid.com/programming-pages/guides/Authoring-Documentation/#/guides/

This is known (jekyll/jemoji#89)), and addressed in jemoji v0.10.2.

Bumping githubpages dependency to 196 should address.

visual defect; see screenshot: