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

Theme Resources #27

Open
psahalot opened this issue Jul 26, 2014 · 5 comments
Open

Theme Resources #27

psahalot opened this issue Jul 26, 2014 · 5 comments

Comments

@psahalot
Copy link

Hi @tarendai
I don't see any section for Themes. I will be happy to build one.
There could be various chapters under themes:

  1. Template Hierarchy
  2. Code Standards
  3. Functions, Hooks, Filters (Themes specific)
  4. Theme Customizer
  5. Data validation and sanitization
  6. Theme Translation / Internalization
  7. Copyright / License Attribution

This is all I could think as of now. But, I am sure there's lot more.
I will be happy to start the section and contribute on various topics.
Looking forward to your reply and confirmation.

Thanks!

@tomjn
Copy link
Owner

tomjn commented Jul 26, 2014

Perhaps but most of those already have sections

  • Template Hierarchy is covered under templates
  • Code standards have their own chapter ( 2 )
  • Data validation and sanitization should go under security
  • Translation and internationalisation is chapter 11 ( I18n )

@obstschale
Copy link
Contributor

I think a chapter about Themes is not bad, but like @tarendai mentioned there are already chapter for different topics. If we add a Theme chapter it should only contain information which are only valid for Themes. For example Copyright / License Attribution is not only a topic for themes but for plugins, too. However, Theme Customizer is a typical theme topic :)

@franz-josef-kaiser
Copy link
Contributor

A Themes chapter could have information about displaying images and strategies for that. It could also show how to register image sizes, change how to display images or alter their output in themes, etc. Another interesting topic would be menus and walkers. Those alone could fill a whole book.

@tomjn
Copy link
Owner

tomjn commented Jan 22, 2015

My thinking is that we already have a templates chapter, perhaps it can be broken up to include the relevant parts and renamed to Themes & Templates?

@franz-josef-kaiser
Copy link
Contributor

Yes, I'd rename that. And make Templates a sub chapter of Themes. There's much more to themes that needs covering than just templates.

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