Danh mục

thiết kế giao diện wordpress phần 7

Số trang: 23      Loại file: pdf      Dung lượng: 932.33 KB      Lượt xem: 11      Lượt tải: 0    
Jamona

Hỗ trợ phí lưu trữ khi tải xuống: 9,000 VND Tải xuống file đầy đủ (23 trang) 0
Xem trước 3 trang đầu tiên của tài liệu này:

Thông tin tài liệu:

Tham khảo tài liệu thiết kế giao diện wordpress phần 7, công nghệ thông tin, đồ họa - thiết kế - flash phục vụ nhu cầu học tập, nghiên cứu và làm việc hiệu quả
Nội dung trích xuất từ tài liệu:
thiết kế giao diện wordpress phần 7 Chapter 5Ill use the CC Labs DHTML License Chooser to assist me in selecting an appropriatelicense (http://labs.creativecommons.org/dhtmllicense/):Ill of course allow sharing of the theme, and let others Remix, which means,derive new themes from this theme with proper credit. I will, however, prevent itfrom being sold commercially by another entity (commercial sites are welcome todownload it and use it), and require the Share-Alike option. This means that noone can legally take the theme package and offer it for sale or use it in such a waythat it generates income for them without my permission. If they reuse or redesignthe package in any other non-commercial way, theyre free to do so; theyre simplyrequired to give me and Packt Publishing credit where credit is due.My licensing agreement looks like the following:OpenSource Magazine WordPress Theme by Tessa Blakeley Silver is licensed undera Creative Commons Attribution-NonCommercial-ShareAlike 3.0 License. [ 117 ]Your Theme in ActionThe end result is a license that keeps to the spirit of the GNU/GPL license, but ismuch less vague. It tells the user upfront that it allows sharing, which is importantto us for educational purposes and prevents commercial distribution withoutpermission, and by requiring Share-Alike, encourages a continued friendlyWordPress-esque atmosphere of open-source collaboration. It also expressly statesthe version number of the license, making it very easy for anyone to look up andread in detail.Create a ReadMe.txt FileYoure now ready to create a ReadMe.txt file. ReadMe files have a long history withcomputers, often accompanying software installation. This has carried over to theweb where anything that gets added or installed into a web service usually has aReadMe file included. Many theme authors chose to make the ReadMe file a .rtf or.html file so that they can include formatting. You may deliver it in any format youwish. I prefer .txt files because it ensures that everyone can simply click to open thefile, and the lack of formatting options ensures I keep my text as clear and conciseas possible.ReadMe files are not required for your theme to work, but if you want to have happytheme users theyre highly recommended. Your ReadMe file is generally your firstdefense against theme users with installation and usage questions.These are the basics of what you should cover in your WordPress theme ReadMe file: Inform theme users what your theme and template files will do (what kind of • site it works best with, if any plug-ins work with it, if its Widit-ized, and so on). Inform theme users of any deficiencies in your theme (any plug-ins it does • not play well with or types of content it doesnt handle well, that is, Ive seen good themes that dont do well with YouTube content due to column width, etc.). Discuss any specific modifications youve made to the theme (especially if • its a newer version of a theme youve previously released) and what files contain the modifications (its always good to have comments in those files that explain the modification as well). Reiterate the basic steps for installing a WordPress theme (not everyone is • keen on reading through WordPresss codex site and will know to unzip the theme or where to upload the file). Also, mention any special requirements your theme has. For instance, if you included some custom PHP code that requires special CHMOD (a.k.a. RewriteRules) or anything like that, specifically list the steps of action a user should take to get your theme running. [ 118 ] Chapter 5 As mentioned in Chapter 4, try and test your theme across platforms and • browsers and mention any rendering issues that certain browsers may have on specific platforms. Reiterate the copyright information that you placed into your style.css • sheet and provide your contact information (web page or email) so that people can reach you for support and questions. ReadThisToo.txt: As long as your ReadMe file includes the points just discussed, youre generally good to go! However, if youre gearing up to release themes for commercial sale, Tonya Engsts article on writing a ReadMe file is great. Its geared toward software developers, but can provide invaluable insight to your themes ReadMe file (if the following URL is too long, you can also just go to mac ...

Tài liệu được xem nhiều: