lostgrid / lostgrid-site Goto Github PK

I was thinking it'd be quite a nice idea to (non-intrusively) collect user email addresses, just to build up a database that we can use in the future. A subscribe section at the bottom of the site would probably suffice, since I hate newsletter popups on websites!

Hey there!

Just wondered why the choosed font for the lostgrid-docs looks rather ordinary:

Montserrat is used in css (see compiled main.css, line 130), but not imported anywhere. Instead an unused Quicksand is imported via CSS-import (see compiled main.css, line 1)

Now that GitHub supports having docs in the main project I think it'd be super helpful to have it there so that features could update the docs within their own branch instead of coming here. (https://help.github.com/articles/configuring-a-publishing-source-for-github-pages/#publishing-your-github-pages-site-from-a-docs-folder-on-your-master-branch)

@japick, you did the heavy lifting on this project – would love to know your thoughts on this!

Hi guys, I've started learning Lostgrid recently by reading the docs and I realized I can't see the syntax code on the examples page which could be a good feature to improve the learning curve. What do you think?

Best 👍

Create the initial Jekyll setup laying out the structure, etc.

• Initial Jekyll creation/de-boilerplating
• Setup how docs are structured

This could be done with either separate repos or an additional new feature for the site.

peterramsing/lost#197 (comment)

It's in the wiki but it should be in one place: https://github.com/peterramsing/lost/wiki/Installation

I created a collection for all the docs to be created in. They are then looped through. I'm creating an example within #11 for the Lost Column but we'll need to transfer all of them over in time.

From @nirfse in library's repo:

Please consider adding screenshots or visual representation of grid layouts in documentation. There are horizontal, vertical, waffles, and masonry grid layouts available to day.

While "horizontal' and "vertical" grids meet the expectations of an accidentally passing by beginner or non front-end developer, it's absolutely not obvious what "waffles" or "masonry" grids look like. I had to double-check in google, what exactly is meant by these. But even googling wasn't straightforward with clarification.

There are a fair amount of similar questions that get asked.

I know this will likely be an iterative process, but we could do with defining an initial sitemap (w/ content for each section) that we can tweak and add to in future.

I believe this is something I might be able to fix.

• buy lostgrid.org

I was thinking WordPress would be most suitable for the site's back-end - unless you had a preference already? I work with WP on a daily basis, so I'm more than comfortable using it.

What were your thoughts on this?

PostCSS would like documentation that includes the outputted version of the plugin: https://github.com/postcss/postcss/blob/master/docs/guidelines/plugin.md#42-include-input-and-output-examples

peterramsing/lost#365

What are your thoughts on a one-pager? I quite like sites like http://kenwheeler.github.io/slick/ that keep everything on the one page with scroll-to sections.

My idea behind the initial design was to have a fixed sidebar with the main content on the right scrollable. Each heading and sub index would then scroll to the relevant section on click. Could be quite nice!

• Update CNAME

I'd love to gather a list of sites/projects using Lost. I'll post on Twitter and see if we can get users commenting in this issue and we can compile a list. 👍

I just been reading your docs and found it quite difficult to read some things.

You have some colour contrast issues which make your example code difficult to read (you can check them here http://webaim.org/resources/contrastchecker/).

I have listed the worst offenders below, there are some others but these three examples are very difficult to read.

.row, .quarter, .half
foreground: #bb0066
background: #434243
contrast: 1.57:1

:first-child
foreground: #555555
background: #434243
contrast: 1.34:1

width, height
foreground: #336699
background: #434243
contrast: 1.67:1