For some reason, all the c-grid-nav links aren't working.

I checked in Chrome, Firefox, and Safari, and none of these links take you through to the appropriate page. The links look like they're all pointing to the right place, so I'm wondering if maybe there's a formatting issue or something?

The SCSS structure should look like this

/css
  /scss
    /abstracts
    /base
    /utilities
    /layout
    /components
    /scope

• Abstracts include variables, mixins, and other Sass-specific stuff.
• Base are base styles like headings, paragraphs, etc
• Utilities will be utility/helper classes like clearfix and stuff
• Layout are layout styles
• Components are all the module-specific styles
• Scope is this.

We probably won't need scope or utilities for this site, but this is how I'm envisioning structuring Sass partials now.

In the url http://bradfrost.github.io/style-guide-guide the Get Started button points to a nonexistent or wrong path, returns error 404

Tried the tool and was having some issues understanding how to make updates. Is there a plan to add more "how-to" documentation in the near future?

If I'm understanding things correctly looking at the blocks-hero module, I have to update the rendered version as well as the markup-only files. This seems a bit difficult to maintain 2 versions. Another similar tool called Astrum has some very nice features and runs through the terminal. Check it out here:

https://github.com/NoDivide/astrum

Thanks and much appreciated!

I am editing button.md and component-detail.html. In the button.md file I am creating a new variable called yammer.

fine-print:
- version: 0.3
  update: April 27, 2017
  owner: Jane Doe
  yammer:  http://github.com

In the component-detail.html file I am trying to use the yammer variable in an anchor tag like this:

<ul>
  <li>Yammer: {{ print.yammer }}</li>
</ul>
<a href="{{ print.yammer }}" class="c-btn">Discuss this on Yammer</a>

When the page renders, Yammer's value does appear in the unordered list, but does not appear within the anchor tag. Any ideas how to get this to work?

It currently has the html extension but is using markdown content.

https://github.com/bradfrost/style-guide-guide/blob/master/getting-started.html

We'll want to set up the basic pages of the

• / - homepage
• /brand/ - brand homepage
• /brand/logo - logo page
• /brand/colors - colors
• /brand/typography - typography
• /brand/tagline -
• /principles/ - principles landing
• /voice-and-tone/ - voice and tone landing
• /voice-and-tone/detail - voice and tone detail page (see http://voiceandtone.com/ for example)
• /patterns/ - landing page for patterns. Note that this page will be a placeholder for other tools
• /code/ - landing for code guidelines. This will house the answers to the questions here: https://github.com/bradfrost/frontend-guidelines-questionnaire/blob/master/README.md
• /code/detail - detail for specific code language/section
• /about/ - about the style guide, who to contact, etc

Getting started page (http://bradfrost.github.io/style-guide-guide/getting-started.html) code conventions link broken

... to learn more about <a href="/style-guide-guide/guidelines/code-conventions.html">code conventions</a>
should be
... to learn more about <a href="/style-guide-guide/guidelines/code.html">code conventions</a>

The <title> tag should read "Voice and Tone | { site.name }" on interior pages

<use href="..&#x2F;..&#x2F;icons.svg#chevron-right"></use> in _includes\patterns\01-molecules-02-blocks-card\01-molecules-02-blocks-card.markup-only.html ends up resolving to http://bradfrost.github.io/icons.svg which obviously doesn't exist/404s

Hello, I found the wiki link of this project (https://github.com/bradfrost/style-guide-guide/wiki) is redrict to the project home (https://github.com/bradfrost/style-guide-guide).
😮 It's interesting. 😸 I couldn't find this feather on the github guides.
How is it achieved?

I just came around reading #26, especially that part with spaces vs. tabs.

I was wondering, whether you would want to add a .editorconfig to make editors pick the chosen convention up :)

Hi, I know that this things take a lot of time and effort, if you can complete the "Importing components and assets from Pattern Lab" section it'd help me a lot 😄

Thanks a lot and if let me know if I can help in anyway

In the primary nav, we'll want the primary nav item to stay open if the user is on a child page for that section. For instance, if the user is on the browser support guideline page, the guidelines section in the primary nav should be open. If the user is on the data table page, components and data tables should be open.

I'd like to display custom tabs (similar to the HTML, Angular, React examples) within the downloads.md file. Is this possible using just markdown?

For example, one common overview-page for all components, with search-form in top that auto-update the component list based on what you type.

Is possible to add a i18n to this? How? I could help, but need details of implementation, like which "plugin" we will use, how text is rendered today, etc

Right now, it says "import HTML code" but we should be able to display the HTML code properly.

I created a landing template that works well for guidelines and styles, but it doesn't really work the same way for the components landing page. I think this should be a simple if/else fix in the landing template. Something like if page.group == "components" then loop through the component subpage categories.

Hi!

I'm trying to get syntax highlighting to work with rouge, but for some reason the rendering is a bit off. The rendered classes for highlight seem really different than what rouge is documenting on their page (in this case, class="token tag instead of class="ng for example). I tried adding highlighter: rouge in config but that doesn't change anything.
Is there a config somewhere that i'm missing?

feature request for a sidebar toggle option to show/hide the SG component list

The primary navigation should be in the open state if you're on a detail page. For example, if you're on Code > HTML, the Code nav dropdown should be open and the HTML link should be highlighted.

While the default focus ring isn't ideal (and can get lost on some backgrounds) the subtly of the current focus style can be difficult for keyboard users to spot when tabbing through.

Judging by the comments on this article [ https://www.paciellogroup.com/blog/2012/04/how-to-remove-css-outlines-in-an-accessible-manner/ ] it seems to be a complicated business getting it right for keyboard and mouse users.