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

Sitemap #48

Closed
mxstbr opened this issue Jan 10, 2016 · 18 comments
Closed

Sitemap #48

mxstbr opened this issue Jan 10, 2016 · 18 comments

Comments

@mxstbr
Copy link
Member

mxstbr commented Jan 10, 2016

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
@marcustisater marcustisater added this to the 1.0 milestone Jan 10, 2016
@marcustisater
Copy link
Member

This goes along with #26 - to create more issues, great point bringing this up. I've been meaning to do so myself.

I can sketch up the sitemap with my thoughts up for feedback.

@marcustisater marcustisater changed the title Content Sitemap Jan 10, 2016
@marcustisater marcustisater self-assigned this Jan 10, 2016
@marcustisater
Copy link
Member

I will have one ready for Thursday - caught up with a lot of work 😢

@marcustisater
Copy link
Member

These are my very first thoughts about the sitemap structure, need some help and feedback.

skarmavbild 2016-01-14 kl 21 09 21

I have this setup on mindmeister. Here is a public url to help contribute to it. https://mm.tt/632990172?t=C2Qo6uvzTk

@marcustisater marcustisater removed their assignment Jan 14, 2016
@marcustisater
Copy link
Member

If we really can get together an completed sitemap it can be easier to split up issues for content that we need.

@mxstbr
Copy link
Member Author

mxstbr commented Jan 14, 2016

Is this launch only?

@marcustisater
Copy link
Member

Sorry? This sitemap needs improvement, it should be ready before launch.

@mxstbr
Copy link
Member Author

mxstbr commented Jan 14, 2016

I meant, should we only add pages that have to be ready for launch? Otherwise the Wizard thing is missing under Plugins.

@marcustisater
Copy link
Member

I gotcha, sorry.

Yes, launch only otherwise it will get to confusing.

@marcustisater
Copy link
Member

cc @ai, @stephenway, @MoOx would love you're guys feedback and help on this one too - others are welcome to edit this sitemap as well of course 😄

@ai
Copy link
Member

ai commented Jan 14, 2016

I think Writing a Plugin should be docs. Because we have also custom plugins, which will not be part of Plugin catalog.

@ai
Copy link
Member

ai commented Jan 14, 2016

We need a API in Documentation or Learn. Because this API is useful not only for plugin developers, but also for runner developers (like gulp-postcss) or non-plugin tools like CSS concat.

@stephenway
Copy link
Collaborator

I could see adding a page to formalize the process of submitting plugins, or for that matter every page has a link to the equivalent content file on github so they can edit it there and create a pull request.

@marcustisater
Copy link
Member

Thanks for quick feedback, will update into a more full version to discuss over.

@marcustisater
Copy link
Member

quick update

sitemap-2

@ai
Copy link
Member

ai commented Jan 15, 2016

@marcustisater looks good

@marcustisater
Copy link
Member

Thanks, I guess this would be a quick start to create issues from what content we need on the website. I will leave this issue open. We will figure it out on the go too.

Feel free to add more pages or modifications if wanted.

@marcustisater
Copy link
Member

updated again

sitemap-3

@marcustisater
Copy link
Member

I broke this issue into #83

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

4 participants