Provide Default Styleguide landing homepage

[andrewmallis]

When we add kalastatic to a web build, and point a client to the styleguide. The landing page is somewhat cryptic.

There's a big heading for KSS Boostrap, which is not relevant to their needs or current understanding. We are encouraging a download of the project here, but it is baked in.

This page is coming from https://github.com/kalamuna/kss-bootstrap/blob/master/styleguide/styleguide.md

GOALS

But should be customizable to the website it pertains to. The page should be rewritten so it is more welcoming and:

• orient users to the purpose of the styleguide
• describe how it should be used
• express that this is their styleguide
• reinforce workflows for keeping things up to date

  QA

http://test-kalastatic.at.kalamuna.com/styleguide/ should present more meaningful and welcome content Display the Kalamuna logo by default

[RobLoach]

https://github.com/kalamuna/kss-bootstrap/pull/38

Could/should clean it up in kstat too... Or improve it.

[andrewmallis]

Great! Cross posting here. We should seek to document how the page can be overridden in a build. Perhaps in here: https://github.com/kalamuna/kalastatic/wiki/Project-Configuration ? Happy to contribute if I can be educated.

[RobLoach]

The homepage property https://github.com/kss-node/kss-node possibly.

[RobLoach]

Thiago has some brain thoughts on this sort of stuff in #239 .

[thiagodemellobueno]

• [ ] Clear well-defined header.
• [ ] Work on a first pass of intro text
• [ ] Provide a basic 'in page flow' high-level menu.

[thiagodemellobueno]

https://github.com/kalamuna/kstat-kss-builder

Not saying it's done, buit I would say it's drastically improved.

[andrewmallis]

Let's integrate this into the build by default and add documentation as well!

[RobLoach]

Style Guide A web Styleguide offer a way of ensuring consistency between brand, design and code. Herein we are looking documenting every component and its code on the site in one place to ensure "same-pagey" communications between designers, front end developers and developers. The pattern portfolio expresses every component and layout structures throughout the site. It articulates the atomic design structure, and is used to illustrate the project’s shared vocabulary.

[RobLoach]

This could be "Done" by taking on https://github.com/kalamuna/kalastatic/issues/408 . Deprioritizing this story to put focus on 408.

[RobLoach]

https://github.com/kalamuna/kalastatic/blob/master/src/homepage.md