Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add demo content for various modules #3

Open
18 of 34 tasks
csshugs opened this issue Jul 29, 2016 · 2 comments
Open
18 of 34 tasks

Add demo content for various modules #3

csshugs opened this issue Jul 29, 2016 · 2 comments

Comments

@csshugs
Copy link
Member

csshugs commented Jul 29, 2016

Provide extra files for demo content of respective modules and include it via <iframe> into the respective docs page.

Getting started

  • Introduction
  • Getting Started
  • Reading These Docs

Settings

  • Core

Tools

  • Clearfix
  • Font-size
  • Hidden

Generic

  • Box-sizing
  • Normalize.css
  • Reset
  • Shared

Elements

  • Headings
  • Images
  • Page
  • Tables

Objects

  • Block
  • Box
  • Crop
  • Flag
  • Layout
  • List-bare
  • List-inline
  • Media
  • Pack
  • Ratio
  • Tables
  • Wrapper

Components

  • Example

Utilities

  • Clearfix
  • Headings
  • Hide
  • Print
  • Spacing
  • Widths
@csshugs
Copy link
Member Author

csshugs commented Sep 2, 2016

I thought it might be a good idea to provide a list of available classes (base class + modifier classes) per module on the respective docs page. You can check that out by having a look at the current sate of the tkt-0003 branch.

csshugs pushed a commit that referenced this issue Oct 20, 2016
csshugs pushed a commit that referenced this issue Oct 20, 2016
csshugs pushed a commit that referenced this issue Oct 20, 2016
csshugs pushed a commit that referenced this issue Oct 20, 2016
@csshugs
Copy link
Member Author

csshugs commented Oct 20, 2016

@inuitcss/core
I now created a file for every module available. All that's missing is the documentation for each module itself. I thought a checklist might be useful to track our progress in providing content for the docs.

If you want to contribute, just check out tkt-0003 branch and put your awesome content in the files in the ./_docs/ directory.


EDIT: I put the checklist to the first comment at the top of the issue, so that the progress is visible in the issue overview page.

csshugs pushed a commit that referenced this issue Dec 29, 2016
csshugs pushed a commit that referenced this issue Dec 14, 2017
csshugs pushed a commit that referenced this issue Jan 4, 2018
csshugs pushed a commit that referenced this issue Jan 4, 2018
csshugs pushed a commit that referenced this issue Jan 4, 2018
csshugs pushed a commit that referenced this issue Jan 4, 2018
csshugs pushed a commit that referenced this issue Jan 4, 2018
csshugs pushed a commit that referenced this issue Jan 4, 2018
csshugs pushed a commit that referenced this issue Feb 22, 2018
csshugs pushed a commit that referenced this issue Feb 22, 2018
csshugs pushed a commit that referenced this issue Feb 22, 2018
Showing the user what partial is required, what is recommended
and what is ‘just’ optional in the docs would be useful when
deciding of which partial to include and which not.
csshugs pushed a commit that referenced this issue Feb 22, 2018
csshugs pushed a commit that referenced this issue Feb 22, 2018
csshugs pushed a commit that referenced this issue Feb 23, 2018
csshugs pushed a commit that referenced this issue Feb 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant