We need a section for visitors to search & find PostCSS Plugins, similar to http://postcss.parts/ - Is it possible to integrate PostCSS Parts into this?

Add continous integration so no PR gets merged that doesn't adhere to the common code style (will be defined in #32) and that breaks the build (and the website) in the process.

Currently, the entire code follows @MoOx' eslint-config-i-am-meticulous.

To be honest, I don't think it matters which exact style guide we adhere to, as long as we choose one and force eslint to complete successfully before we merge anything into master.

I'd be fine with simply enforcing eslint-config-i-am-meticulous since the whole codebase is written like that at the moment and it'll save us time because we don't have to rewrite everything in a new style. Any objections?

Note: I personally am a big fan of eslint-config-airbnb with three custom rules, for an example of React code with that eslint config take a look at this example file.

Refine and clarify your goals

Determine what you want to accomplish.

1. Communicate differentiation
2. Provide overview of quote process
3. Show value through rich media
4. Outline next steps (testimonials, referrals, etc.)

Define who will be visiting your website and what you want them to do. Primary and secondary audiences should be considered on every page.

Demographics

Example of basic traits of people that fit into your audience.

• Age (25-34 & 45-54)
• Location
• Gender (Female & Male)
• Income
• Education
• Occupation
• Ethnicity
• Marital Status
• Number of Children

Psychographics

Based on the demographic, this helps you talk to your audience.

• Personality
• Attitudes
• Values
• Interests/hobbies
• Lifestyle
• Behavior

Resources

You can start your research with these tools:

• US Census Bureau >
• Google Analytics >
• Facebook Insights >

We have discussed creating a "Blog" section for the website including a Twitter feed of some kind having users to look up the latest news about PostCSS and it's community.

We already have the logo symbol but do not have a logotype to go with it. I would think this would be a requirement for a website. Would love to track this here and collectively look at type specimens and usage.

First comp from today, just basic Helvetica Neue

The main decision is to agree on what system is going to be used for this website. My first thought was to do this website in like Jekyll or an small CMS system but now after so many people already wanting to contributing and having suggestions I will leave this up for a very open discussion.

@MoOx has one suggestion of using Statinamic stated in ticket #391

Don't know what you plan to use for the engine, but I would be really happy to offer some support for my new engine Statinamic (react based static website generator, that also provide client side optimised navigation).

What do you guys think? Let us know you're thoughts.

Pull Requests are reviewed by members of the team specified in the MAINTAINERS file in your repository and cannot be merged until all approvals are received.

Approvers comment on the issue with LGTM, looks good to me, indicating their approval to merge the changeset.

This looks very useful for this project, this means without approval of the core maintainers no PR can be merged.

@ai @marcustisater do you want to be in the MAINTAINERS file? You'd have to comment each and every PR then with LGTM though.

We need some content and suggestions for the FAQ(Frequently Asked Questions) section.

Example:

Can I still use Sass?
Yes, you can still compile....etc

Where can I find the API documentation?
You can find it at .....

Please read through our contributing guidelines before you start.

https://github.com/postcss/postcss.org/blob/master/content/learn/introduction/faq.md

@ai how is the domain name looking? It's already bought, I hope you did that? 😜

This is a child page of #64

This page will contain useful resources such as

• PostCSS Articles
• PostCSS Video tutorials like https://www.youtube.com/watch?v=bJShpMC7xFM from @stolinski

Please read through our contributing guidelines before you start.

https://github.com/postcss/postcss.org/blob/master/content/learn/resources

I think in order to run a very successful project you need some developers that are willing to put in some extra work/time and take responsibility therefor we should state some key people that can be lead of development and also design.

@ai will of course have the final word of everything but the main focus it to get some people in charge

TBD on Gitter upcoming meeting.

There should be some very good documentation of PostCSS on the website. Here are some quick initial ideas;

• How to get started
• Developer API
• PostCSS in a nutshell

etc...

There are already some very good documentation on the PostCSS GitHub page that we can use.

@ai mentioned an idea to create a migration guide for PostCSS

Design to be made when #4 is completed.

Something that we have mentioned before is building a "build you're own PostCSS package" section were you can get some kind of a postcss-package from just a few simpel clicks in a GUI similar as Yeoman.

@ai idea

You select basement: preprocessors or/and CSS4.
You select architecture: BEM, CSS Modules, etc.
You select a builder: Gulp, webpack, grunt, etc.
Pick some extra sugar.
We will get you a exactly code to copy-paste to your build process. For example, only gulp-cssnext with some sugar plugin additions if you select CSS4, BEM, Gulp and not so many additions.

We would need a favicon - http://realfavicongenerator.net/

@stephenway should we include this into the brand repo as well or is it irrelevant?

From the sitemap ( #48 ) - we have decide that there is going to be a page of PostCSS Plugins to pick from. I am thinking that the landing page would include the Plugin Search( #17 ) and then there would be a list similar as a sidebar navigation menu to group PostCSS plugins as a categories.

What do we need?

1. Landing page mockup of how the plugins page would look like including the search as well how the user can navigate to find more plugins to choose from.
2. Mockup for individual PostCSS categories pages
3. Mockup for individual PostCSS plugin pages when clicked or hyperlink for GitHub/NPM?

We need a introduction landing page for how you can contribute to the PostCSS community.

parent of
#72
#66

We need a nice short introduction of what the documentation page is all about.

parent of
#71
#70
#69
#68
#67

See http://moox.io/statinamic/docs/usage/gh-pages/

Boilerplate to be started when #8 is completed. What I mean by boilerplate is to add things like well documented and thought out structured CSS, JS before we get to building.

Should we consider to use structure like BEM or just plain up components with CSS Modules etc...

Assignee: TBA Lead Developer to help out?

I think a wise idea is to get together on Hangouts or gitter.im and talk over some ideas and inputs for this project meanwhile that there are being some tickets & milestones created.

There is no set date for a meeting yet but plans are after new years when everybody is back home and are ready for some action.

Date to be updated soon and hopefully time zone friendly 😅

@ai do you think it's possible to get up an staging server for tests when we start building the website? How is that part looking? Do you think that's necessary? It would be cool with some kind of a beta launch also

That would be nice to already have this setup :)
Btw, I think www. are should not be used, this provide a 90' feeling and PostCSS is the future, not the past :)

Might be helpful for PRs. Thoughts?

Invision - Emailed Support about OSS Plans
Zeplin - Offering free plan with 3 projects
Pixelapse - Unlimited public projects! Thanks @patrick91

@marcustisater - Need issue labels for design and design needed.

I think this should be discussed, following #4 (comment)

@ai can you hook me up with the .io and .org domain on gandi so I can set it up

AST explorer to be embedded/integrated in a section for plugin developers to get started. There is a issue that has to be resolved first. Feel free to help.

@fkling from issue #11

I started working on something that lets you specify the parser in the URL. That should be good enough for a start I guess.

Before we begin actually designing and building the website, we need a coarse overview of the modules/pages the website needs for v1. This is what I imagine currently:

postcss.com
├── Documentation
├── AST Explorer    <-- Is this v1?
├── Plugins         <-- (List, wizard is v1.1)
└── Get involved

We are going to try end up having all initial suggestions for the website collected here. Try reference tickets to this one.

@ai had some very good suggestions from ticket #391

Plugins list (even with search like in gulp) is a lame way. We need some wizard (of course list will exists too):
You select basement: preprocessors or/and CSS4.
You select architecture: BEM, CSS Modules, etc.
You select a builder: Gulp, webpack, grunt, etc.
Pick some extra sugar.
We will get you a exactly code to copy-paste to your build process. For example, only gulp-cssnext with some sugar plugin additions if you select CSS4, BEM, Gulp and not so many additions.
AST explorer for plugin developer. You put a CSS and get PostCSS AST with references.
Migration guide
Docs with good formation.
Playground based on postcss-use.

We have a Slack group. Slack only allows people with access to an email address at the domains specified by the team's Owner will be able to sign up therefor I have to do the invite only rule.

If you would like to join the Slack Channel please comment down below you're e-mail adress and the invite will be sent to you. You can also send me you're e-mail adress privately

Thank you,

Page for introducing PostCSS and what you can learn from this section.
#81
#82

It would be awesome to create a styleguide from the visual design #12

@MoOx suggested https://github.com/sapegin/react-styleguidist

This is a quick follow-on to @MoOx's comment in the boilerplate issue and the stylelint PR.

Are you be willing to accept a PR that replaces the current individual postcss plugins, of postcss-custom-media and postcss-custom-properties, with the postcss-cssnext plugin pack? I'll then be able to use its nesting feature as a replacement for @MoOx's use of indentation that I had to nuke in https://github.com/jeddy3/postcss.com/commit/592fe836fd6fa04f042b5fa064f6a07d5daa7787#diff-8a4b7dda92b463014bdba201b85229b6R24.

I figured it would be better to include postcss-cssnext, rather than request the addition of just postcss-nesting, as postcss-cssnext seems to be—like stylelint—featured in the early design mock-ups.

There are a few rules—function-calc-no-unspaced-operator, media-feature-range-operator-space-after, selector-pseudo-element-colon-notation etc—within stylelint-config-standard that are geared towards the features of postcss-cssnext, and so I think they will be an excellent fit for each other.

What do you think?

Landing page for new visitors to learn about what PostCSS is and what it has to offer.

The boilerplate issue mentions adding structured CSS.

Do you want me to submit a PR that adds linting to each component's CSS, using stylelint and the stylelint-config-standard? Although the config won't help enforce the use of CSS Modules, it will catch little coding mistakes like accidental shorthand overrides and invalid hex colours.

As an aside, it's awesome to see stylelint get a mention in the early mock-up designs! :)

There seems to be a problem with npm start with static not working. If this is a Statinamic issue, please recreate the issue on it's repository or refer this one.

throw new Error("webpack build failed with errors");

Page including how you can create you're own PostCSS Plugin. I would like this page to get sort of like a timeline from start to finish.

Timeline

• Tutorial (How to start?)
• Boilerplate
• API
• Tools(you might need)
• Submit plugin(tell the world!)

https://github.com/postcss/postcss/blob/master/docs/writing-a-plugin.md

Mindmap

Please read through our contributing guidelines before you start.

https://github.com/postcss/postcss.org/tree/master/content/docs/create-postcss-plugin

We need a good strategy of how to plan out all the documentation labeld for this project.
#26 #19

We need to create milestone being set for this project

I thought that we all decided to use postcss.org, because it is not _com_mertial project (unfortunately) and we are not members of British Indian Ocean Territory. So, maybe we need to rename repo?

Andrey mentioned in ticket 391 that he is looking for some really nice artwork for this website, something that PostCSS seems to have quite frequently on Twitter, posts etc...

Also I want a good art work for site. Something like pixelart or/and watercolor. Funny but about black magic. Can you recommend a good artists to place a order?

We are going to be designing the website from scratch and I think a good idea is to get up a mockup up for review as soon as possible.

These are some initial thoughts from ticket 391

omgovic

How about a section where some people will say ideas of plugins?

admdh

[THE LOOK] Maybe it would be good idea to introduce PostCSS like something more luxury, more ambitious? Something that make trends and not follows them. For example just look at bootstrap and foundation websites i think they look like 90th now. PostCSS website definitely shouldn't be like that. i think PostCSS website can, or even should be more conceptual.

[THE FEATURES] i think the most important feature of the website should be well organised documentation, easy to use, easy to find. Maybe search page like gulpjs.com has (as it was mentioned before). I think it would be good if there were rules which plugins will be recommended first (for example those which have good documentation) and which last (with bad documentation). maybe plugins statistics.

I think we need to include the npm for the statinamic build to the package.json or am I wrong?

Page for how contributors can help out in the community.

Key points

• PostCSS Repository
• PostCSS.org Repository
• How to report bugs?
• Contributing Guidelines

We need a REAMDE file with documentation of how to contribute.

There is going to be a landing page for visitors to "Getting Started" with PostCSS.