Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The order of your navbar menu is determined by the HTML template in <code>_layout</code> (which may be pulling in HTML fragments from <code>_includes</code>.</p> <p>It sounds like your navbar is being programatically generated from the list of pages provided in site.pages using the liquid code</p> <pre><code>{% assign pages_list = site.pages %} </code></pre> <p>If you have only a small number of pages, you may prefer to just write the list out manually. <code>site.pages</code> is Jekyll's alphabetical list of all pages. Nothing stops you from just hardcoding this instead:</p> <pre><code> &lt;div class="navbar" id="page-top"&gt; &lt;div class="navbar-inner"&gt; &lt;div class="container"&gt; &lt;a class="brand" href="/"&gt;EverCoding.net&lt;/a&gt; &lt;ul class="nav"&gt; &lt;li&gt;&lt;a href="/pages.html"&gt;Pages&lt;/a&gt;&lt;/li&gt; &lt;li&gt;&lt;a href="/archive.html"&gt;Archive&lt;/a&gt;&lt;/li&gt; &lt;li&gt;&lt;a href="/about.html"&gt;About&lt;/a&gt;&lt;/li&gt; &lt;li&gt;&lt;a href="/messages.html"&gt;Messages&lt;/a&gt;&lt;/li&gt; </code></pre> <p>Whereas I'm guessing at the moment you have that list generated programmatically, perhaps by following the way Jekyll-bootstrap does with liquid code:</p> <pre><code>&lt;div class="navbar"&gt; &lt;div class="navbar-inner"&gt; &lt;div class="container"&gt; &lt;a class="brand" href="{{ HOME_PATH }}"&gt;{{ site.title }}&lt;/a&gt; &lt;ul class="nav"&gt; {% assign pages_list = site.pages %} {% assign group = 'navigation' %} {% include JB/pages_list %} &lt;/ul&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; </code></pre> <p>The liquid code in this second example is handy if you really want to determine the menu each time, but if you have a static menu in a static order you are probably best coding it by hand as in my first example, rather than modifying the liquid code to sort. </p> <p>If you could link to the Jekyll source, rather than the published blog, we could be more specific. </p>
    singulars
    1. This table or related slice is empty.
    1. POHow to change the default order pages in Jekyll?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. UScboettig
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to change the default order pages in Jekyll?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks. Ni have looked at the [Jekyll source](https://github.com/mojombo/jekyll/blob/master/lib/jekyll/site.rb) aboue about site.pages. Looks it cannot deal the site.pages array
      singulars
      1. PO
      1. USEver
    2. COI am afraid I don't follow your comment. Are you using the jekyll-bootstrap template? It accesses site.pages just fine. As per my suggestion above, I don't see why you need access to site.pages if you intend to work with the four static page choices you specify.
      singulars
      1. PO
      1. UScboettig
    3. COthanks. I have chanage my blog with your first method. I give the comment above for learning. I just wonder why i cannot deal with an array in the jekyll..
      singulars
      1. PO
      1. USEver
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload