Hey I love this generator. It's my favorite so far due to its simplicity and versatility. One thing that would be great is to generate a static site from the PHP that could more easily be handed off to customers. Is something like that possible?

Hi, thanks for the tool. IMO, this is more flexible than other tools which bake in the documentation inside of the CSS, which I personally dislike. However, is there anyway we can include a markdown processor for the docs? As the docs require code blocks? I'd be happy to send a PR but I haven't worked in PHP before

I've been trying to build a styleguide using this brilliant work.

But at some point selection of the code stopped working.

Firefox with Web Developer addon wont show an error when clicking Copy Source button.

Would you advise where to move on?

The live page/patient - https://englishextra.github.io/pages/styleguide.html The Repo here https://github.com/englishextra/englishextra.github.io/blob/master/pages/styleguide.html

After a couple of hours debugging I found that your original template html markup gets selected visually.

Mine doesn't - the w3c validator only warns about new functionality but the rest is ok.

I don't know enough about php to answer this myself, so might not even be an issue, but thought I'd check. I noticed that A List Apart seems to be using your boilerplate for the basis of their style guide and they have posted about URL sanitation and potential security risk when the files are public. http://alistapart.com/blog/post/pattern-library-security-vulnerability

I have used the boilerplate publicly so just checking. Regardless, thanks for the great resource.

css/sg-styles.css only defines .sg-nav-group a and .sg-nav-group a:hover. If a user replaces css/styles.css with a project stylesheet that defines a:visited and a:focus, this might look strange.

Probably the easiest solution would be to amend css/sg-style.css like this:

.sg-nav-group a,
.sg-nav-group a:visited { … }

.sg-nav-group a:hover,
.sg-nav-group a:focus { … }

Most Unix-/Linux-type operating systems (including OS X) produce hidden system files usually starting with a dot in the file's name (e.g. the infamous .DS_Store on OS X). PHP's scandir picks these up as well, but they are not excluded by if ($file != '.' && $file != '..') in functions.php.

Ideally, the *FilesInFolder functions should probably exclude any file name that starts with a ..

This feature allows quickly add new sections into project, no more index.php manual edit required. Just create a new folders/subfolders into the markup/ directory, and they will be added into project automatically.

If the source is too long, the view source window does not show it all and makes it impossible to view/select/copy. Scrollbar on this window? Possibly a button to copy source?

I don't know if you have a reason for this, but it seems unusual to include custom scrollbars in a boilerplate. I suggest you consider removing those styles.

Adding a stylesheet that uses box-sizing: border-box makes the color swatches smaller and breaks the hover effect.

Is it better to assume the use of box-sizing: border-box, or not?

In style guides you typically see different layout pages, so I think it would be a good idea to include a link to another page with a super simple demo layout

https://github.com/salesforce-ux/theo https://github.com/salesforce-ux/theo-example https://medium.com/@didoo/how-to-manage-your-design-tokens-with-style-dictionary-98c795b938aa https://uxdesign.cc/design-tokens-for-dummies-8acebf010d71 https://24ways.org/2019/design-tokens-and-component-based-design/ https://www.smashingmagazine.com/2019/11/smashing-podcast-episode-3/ https://noti.st/sturobson/QIaw2X

Goals of v4 Rewrite

• Write in language I use day to day so it is easier to maintain
  • I don't use PHP, haven't used it for years. However, I do use NodeJS so the rewrite will be built with that.
  • This will make it much easier for me to add new features
    • Im thinking about adding browser reload on save functionality
    • See if I can incorporate a simple search feature
    • Add support to design tokens for color and fonts
• Keep it as passive as possible for existing users.
  • Migration should be easy, there will be minimal lift and shift of files required
• Keep it as simple as possible
  • One of the main goals of the project has been to keep SGB simple, un-opinionated, and easy to use.
  • No jQuery, no Webpack, no Babel. All those tools are useful and have a place, but for this project I want to keep things really easy for people who primarily work in HTML and CSS to get a styleguide up and running.

What will happen to the PHP version?

The PHP version will be migrated over to https://github.com/bjankord/Style-Guide-Boilerplate-php