-
-
Notifications
You must be signed in to change notification settings - Fork 50
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
Comments
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. |
I will have one ready for Thursday - caught up with a lot of work 😢 |
These are my very first thoughts about the sitemap structure, need some help and feedback. I have this setup on mindmeister. Here is a public url to help contribute to it. https://mm.tt/632990172?t=C2Qo6uvzTk |
If we really can get together an completed sitemap it can be easier to split up issues for content that we need. |
Is this launch only? |
Sorry? This sitemap needs improvement, it should be ready before launch. |
I meant, should we only add pages that have to be ready for launch? Otherwise the Wizard thing is missing under Plugins. |
I gotcha, sorry. Yes, launch only otherwise it will get to confusing. |
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 😄 |
I think |
We need a API in Documentation or Learn. Because this API is useful not only for plugin developers, but also for runner developers (like |
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. |
Thanks for quick feedback, will update into a more full version to discuss over. |
@marcustisater looks good |
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. |
I broke this issue into #83 |
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:The text was updated successfully, but these errors were encountered: