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

Requirements for Layout Contribution #97

Closed
stephenway opened this issue Jan 20, 2016 · 5 comments
Closed

Requirements for Layout Contribution #97

stephenway opened this issue Jan 20, 2016 · 5 comments

Comments

@stephenway
Copy link
Collaborator

Now that we have a solid direction on design and contribution path, it seems that we need to flesh out the requirements.

  • First off, we need @okonet to upload his design to Zeplin and invite members to the project. Zeplin #98
  • After that we need to get the front-end coded into this project.
  • At this point we will need to identify which pages need custom layouts vs basic articles.
  • Assign each custom layout as 'help needed'.
@stephenway stephenway mentioned this issue Jan 20, 2016
@marcustisater
Copy link
Member

Great breakdown. Here are some of my notes.

  • Everything from Zeplin should try to be reference in issues, tasks such as "Create the main-navigation" etc.. I will help with that once the design is up.
  • We should investigate how we are going to break down individual page layout as mentioned. The way I see it from the content point of view is that we have an "landing page", and single "page" with sidebar navigation for subpages.

Yes, we definitely have to break down all the custom layouts.

@marcustisater
Copy link
Member

Remember that every page is already in a issue form to remind everyone. This is a good reminder to look at things that are "custom layouts" such as the plugin page.

#83

@marcustisater marcustisater mentioned this issue Jan 21, 2016
@marcustisater
Copy link
Member

@stephenway - Would you mind If I create some issues for the custom layouts that needs design or do you want to organize that?

@stephenway
Copy link
Collaborator Author

If you think you know what layouts we need, by all means, but otherwise we should identify which pages need custom.

@marcustisater
Copy link
Member

Good point, I know a few pages that would defently need to be custom but you are correct. I will sit down this weekend to really go through it all. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants