postcss / postcss.org Goto Github PK
View Code? Open in Web Editor NEWOfficial website for PostCSS
Home Page: https://postcss.org
License: MIT License
Official website for PostCSS
Home Page: https://postcss.org
License: MIT License
I think this should be discussed, following #4 (comment)
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! :)
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
https://github.com/postcss/postcss/blob/master/docs/writing-a-plugin.md
Please read through our contributing guidelines before you start.
https://github.com/postcss/postcss.org/tree/master/content/docs/create-postcss-plugin
Determine what you want to accomplish.
Define who will be visiting your website and what you want them to do. Primary and secondary audiences should be considered on every page.
Example of basic traits of people that fit into your audience.
Based on the demographic, this helps you talk to your audience.
You can start your research with these tools:
We need to create milestone being set for this project
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.
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?
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 :)
@ai mentioned an idea to create a migration guide for PostCSS
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.
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.
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 π
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?
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.
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
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.
There is going to be a landing page for visitors to "Getting Started" with PostCSS.
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.
I think we need to include the npm for the statinamic build to the package.json or am I wrong?
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?
This is a child page of #64
This page will contain useful resources such as
Please read through our contributing guidelines before you start.
https://github.com/postcss/postcss.org/blob/master/content/learn/resources
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?
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
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,
@ai how is the domain name looking? It's already bought, I hope you did that? π
@ai can you hook me up with the .io and .org domain on gandi so I can set it up
We need a REAMDE file with documentation of how to contribute.
There should be some very good documentation of PostCSS on the website. Here are some quick initial ideas;
etc...
There are already some very good documentation on the PostCSS GitHub page that we can use.
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
.
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");
We would need a favicon - http://realfavicongenerator.net/
@stephenway should we include this into the brand repo as well or is it irrelevant?
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?
It would be awesome to create a styleguide from the visual design #12
@MoOx suggested https://github.com/sapegin/react-styleguidist
@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
Landing page for new visitors to learn about what PostCSS is and what it has to offer.
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.
I started working on something that lets you specify the parser in the URL. That should be good enough for a start I guess.
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.
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.
Page for how contributors can help out in the community.
Key points
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?
Design to be made when #4 is completed.
Might be helpful for PRs. Thoughts?
A declarative, efficient, and flexible JavaScript library for building user interfaces.
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. πππ
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google β€οΈ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.