Revision history for WikkaHowto
Revision [23123]
Last edited on 2016-05-20 07:38:46 by DarTar [Replaces old-style internal links with new pipe-split links.]Additions:
~-[[CodingGuidelinesHowto | Coding guidelines]]
~-[[DocumentingCodeHowto | Documenting Code (with templates)]]
~-[[DocumentingCodeHowto | Documenting Code (with templates)]]
Deletions:
~-[[DocumentingCodeHowto Documenting Code (with templates)]]
No Differences
Additions:
~-[[CodingGuidelinesHowto Coding guidelines]]
Deletions:
Additions:
===Tip for beginning developers===
While Wikka is pretty easy to hack, you do at least need some basic knowledge of PHP to do that. And you need a little more than that to be able to write your own (simple) extensions. If you're a PHP beginner, there is now a **free** downloadable book that might help:
~**Book Title**: A Programmer's Introduction to PHP 4.0
~**Description**:
~A Programmer's Introduction to PHP 4.0 shows you how to make the most of PHP's powerful capabilities, regardless of your current scope of PHP knowledge.
~To celebrate the runaway success of W. Jason Gilmore's second Apress title, Beginning PHP 5 and MySQL: From Novice to Professional, we're pleased to be able to offer this earlier PHP title to you absolutely free. This book begins with a rapid introduction to PHP's syntax and basic functionality, then steers you toward advanced issues, like PHP's role in database manipulation, sessions, and user interactivity. It examines how PHP can work with XML, JavaScript, and the Component Object Model (COM). You'll find it loaded with practical examples and several projects which can be immediately incorporated on any website.
~**Download**:
~http://apress.com/free/content/ProgrammersIntroductionToPHP4.pdf
~**Corresponding Code**:
~http://www.apress.com/ApressCorporate/supplement/1/3/1893115852-12.zip
~//augustwind16 on http://groups.yahoo.com/group/phpexperts/message/443//
While Wikka is pretty easy to hack, you do at least need some basic knowledge of PHP to do that. And you need a little more than that to be able to write your own (simple) extensions. If you're a PHP beginner, there is now a **free** downloadable book that might help:
~**Book Title**: A Programmer's Introduction to PHP 4.0
~**Description**:
~A Programmer's Introduction to PHP 4.0 shows you how to make the most of PHP's powerful capabilities, regardless of your current scope of PHP knowledge.
~To celebrate the runaway success of W. Jason Gilmore's second Apress title, Beginning PHP 5 and MySQL: From Novice to Professional, we're pleased to be able to offer this earlier PHP title to you absolutely free. This book begins with a rapid introduction to PHP's syntax and basic functionality, then steers you toward advanced issues, like PHP's role in database manipulation, sessions, and user interactivity. It examines how PHP can work with XML, JavaScript, and the Component Object Model (COM). You'll find it loaded with practical examples and several projects which can be immediately incorporated on any website.
~**Download**:
~http://apress.com/free/content/ProgrammersIntroductionToPHP4.pdf
~**Corresponding Code**:
~http://www.apress.com/ApressCorporate/supplement/1/3/1893115852-12.zip
~//augustwind16 on http://groups.yahoo.com/group/phpexperts/message/443//
Additions:
~-[[DocumentingCodeHowto Documenting Code (with templates)]]
Deletions:
Additions:
~-[[WikkaCodingGuidelinesHowto Coding guidelines]]
Deletions:
Additions:
=====The Wikka "Howto" Pages =====
//This page is still a stub - it will be expanded soon.//
This page is the "hub" for tips and guidelines for Wikka Developers - both those working on features intended to be included in an official Wikka release, and those writing "plugins" that extend the basic Wikka functionality for specific purposes but don't (won't) form part of the package.
There will be a variety of guidelines and tips, all intended to get good, maintainable code that generates standards-compliant output. Some of these will be based on established web standards (such as XHTML and CSS), while others are more proposed guidelines to enhance readability and maintainablity of our code base, support (future) internationalization, documentation guidelines, etc..
What to expect:
~-Coding guidelines
~-Coding tips
~-Code structure guidelines (what to place where and why)
~-Documenting Code (with templates)
~-Prepare code for internationalization
~-XHTML
~-Generating data tables
~-... more that I haven't thought of yet ;-)
----
//This page is still a stub - it will be expanded soon.//
This page is the "hub" for tips and guidelines for Wikka Developers - both those working on features intended to be included in an official Wikka release, and those writing "plugins" that extend the basic Wikka functionality for specific purposes but don't (won't) form part of the package.
There will be a variety of guidelines and tips, all intended to get good, maintainable code that generates standards-compliant output. Some of these will be based on established web standards (such as XHTML and CSS), while others are more proposed guidelines to enhance readability and maintainablity of our code base, support (future) internationalization, documentation guidelines, etc..
What to expect:
~-Coding guidelines
~-Coding tips
~-Code structure guidelines (what to place where and why)
~-Documenting Code (with templates)
~-Prepare code for internationalization
~-XHTML
~-Generating data tables
~-... more that I haven't thought of yet ;-)
----
Deletions:
//This page is still a stub - it will be expanded soon.//
This page is the "hub" for tips and guidelines for Wikka Developers - both those working on features intended to be included in an official Wikka release, and those writing "plugins" that extend the basic Wikka functionality for specific purposes but don't (won't) form part of the package.
There will be a variety of guidelines and tips, all intended to get good, maintainable code that generates standards-compliant output. Some of these will be based on established web standards (such as XHTML and CSS), while others are more proposed guidelines to enhance readability and maintainablity of our code base, support (future) internationalization, documentation guidelines, etc..
----
Additions:
CategoryHowto
Deletions:
Additions:
=====The Wikka "Howto" Pages =====
//This page is still a stub - it will be expanded soon.//
This page is the "hub" for tips and guidelines for Wikka Developers - both those working on features intended to be included in an official Wikka release, and those writing "plugins" that extend the basic Wikka functionality for specific purposes but don't (won't) form part of the package.
There will be a variety of guidelines and tips, all intended to get good, maintainable code that generates standards-compliant output. Some of these will be based on established web standards (such as XHTML and CSS), while others are more proposed guidelines to enhance readability and maintainablity of our code base, support (future) internationalization, documentation guidelines, etc..
CategoryDocumentation CategoryHowto
//This page is still a stub - it will be expanded soon.//
This page is the "hub" for tips and guidelines for Wikka Developers - both those working on features intended to be included in an official Wikka release, and those writing "plugins" that extend the basic Wikka functionality for specific purposes but don't (won't) form part of the package.
There will be a variety of guidelines and tips, all intended to get good, maintainable code that generates standards-compliant output. Some of these will be based on established web standards (such as XHTML and CSS), while others are more proposed guidelines to enhance readability and maintainablity of our code base, support (future) internationalization, documentation guidelines, etc..
CategoryDocumentation CategoryHowto
Deletions:
=====Title of the page =====
//This page is a **template** intended for documentation of **official Wikka features**. This page belongs to CategoryTemplate (which contains more handy templates). To create a Wikka documentation page, [[http://wikka.jsnx.com/DocumentationTemplate/clone clone this page]] (most documentation page names end in 'Info' so it's useful to stick to that convention), replace the title with a meaningful one and replace this paragraph with the actual page content.//
CategoryDocumentation
