Sitemap

Question

Before we begin actually designing and building the website, we need a coarse overview

marcustisater · Answer

This goes along with <a aria-label="Issue #26" class="issue-link js-issue-link" data-e

marcustisater · Answer

I will have one ready for Thursday - caught up with a lot of work <g-emoji class="g-em

marcustisater · Answer

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

marcustisater · Answer

If we really can get together an completed sitemap it can be easier to split up issues

mxstbr · Answer

Is this launch only?

marcustisater · Answer

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

mxstbr · Answer

I meant, should we only add pages that have to be ready for launch? Otherwise the Wiza

marcustisater · Answer

I gotcha, sorry.

Yes, launch only otherwise it will get to confusing

marcustisater · Answer

cc <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="

ai · Answer

I think Writing a Plugin should be docs. Because we h

ai · Answer

We need a API in Documentation or Learn. Because this API is useful not only for plugi

stephenway · Answer

I could see adding a page to formalize the process of submitting plugins, or for that

marcustisater · Answer

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

marcustisater · Answer

quick update

ai · Answer

<a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/us

marcustisater · Answer

Thanks, I guess this would be a quick start to create issues from what content we need

marcustisater · Answer

updated again

marcustisater · Answer

I broke this issue into <a aria-label="Issue #83" class="issue-link js-issue-link" dat

Sitemap about postcss.org HOT 18 CLOSED