Tutorial and API documentation
To learn the ECK faster by myself, I'm now trying to write a programmer's tutorial and an API reference in the style of the django documentation
https://docs.djangoproject.com/en/1.4/intro/tutorial01/
Are there good examples of modules using the ECK?
You can also help me with a hint about how to add and modify bundles using code. I didn't see anything about that in the existing documentation (but with mouseclicks, it's very simple).
Philipp
Read moreD7 Documentation
Q: What could be better than free open-source software?
A: Free open-source documentation and tutorials.
I'm reposting this message here, because it looks really useful.
-dave
Itangalo has posted a Discussion at
http://groups.drupal.org/node/230358
Book "Drupal 7 – the Essentials" being added to the community wiki
I am very happy to announce that I (finally!) am publishing my book Drupal 7 – the Essentials in the documentation section on drupal.org!
Read moreDrupal 日本語ドキュメンテーション
日本語のドキュメンテーション作成に関しては、以前から何度か話題に出たり(例:http://groups.drupal.org/node/215518#comment-716204 )、翻訳の試みなどもあった中で必要なものが見えてきた気がします。ニーズがあることは明らかですし、協力することに前向きな方も増えているようなので、ここで一度意見をまとめた上で、可能であれば実行に移していければと思います。ホスティングに関しては、abechiyo2000 さんがオファーしてくださっていますし、弊社(Acquia)で行うことも可能です。
以下、僕が考えられる必要最低限の機能と人材です。
必要な機能(概要 - 詳細は追ってデザインしましょう):
- Wiki、または共同作業に適したコンテンツタイプ
- 作業に関連するディスカッションフォーラム
必要な人材:
- 翻訳者
- サイトビルダー(モジュールのインストールや設定。カスタムモジュール開発は極力避ける)
- サイト管理者(コンテンツおよびユーザーの管理)
- サイト管理者(コードの管理:コアやモジュールのアップデートなど含む)
[GSoC Proposal] Help Topic module for the Drupal Documentation Team and for the help system
Perl script to automatically format docblock text
One of the things that I find really fiddly with writing documentation is making sure lines wrap to 80 characters. I find it really breaks my flow of concentration to be always watching for when to hit return or even go back when a word turns out to be too long and then type a space-star-space (how on earth people did it in the days of manual typewriters... I guess we're just spoilt with technology nowadays!).
Read moreIs there a central place for Documentation of the BOA project?
I hope this isn't a silly question but is there a central place for Documentation of the BOA project? Or there plans for it going forward.
I realise that we have:
http://drupal.org/project/barracuda
http://drupal.org/project/issues/barracuda
http://drupal.org/project/octopus
http://drupal.org/project/issues/octopus
http://community.aegirproject.org/
http://groups.drupal.org/boa
http://omega8.cc/ (library section)
Then there are the text files.
http://drupalcode.org/project/barracuda.git/blob_plain/HEAD:/docs/INSTAL...
Read moreNeed info on "Standard Issue Tags for Drupal core"
I've been asked to edit the Standard Issue Tags for Drupal core page to correct its characterization of accessibility issues, and, as usual, the editorial eye found more needing to be fixed than it was asked to review.
Specifically in this case, there are cases in which two issue tags are difficult to distinguish from each other. "Accessibility" and "needs accessibility review" is one such instance. Another is "usability" and "needs usability review." The definitions given for these terms don't help clear things up, either.
Before I make sweeping changes, I would like to get feedback from folks who are familiar with the issue queue about a role- and intent-based approach for telling who should — or, sometimes, who may — use any particular tag.
Read moreLink to Omega 3.x docs wiki
I'm adding this link here because the wiki doesn't show up on the Omega Framework group's main page & it's not mentioned on the d.o Omega project page. Though the docs that exist in this wiki are temporary until the microsite is complete, there is a lot of info here that I think many who are new to 3.x will find useful.
Read moreRules Documentation
Judging from historical questions and comments regarding "Rules", that never are answered, it appears that documentation for this module is pretty thin. Unless the trigger and action falls into a pretty narrow spectrum, Rules is pretty limited.
Read more[GSoC proposal] Conditional text for the Drupal help system and the documentation team
Conditional text for the Drupal help system and the documentation team
“The basic idea of conditional text is to evaluate an expression, and display text if it's true. “
In short, this is what my proposed module will do.
However, sometimes the conditions will be topic level, sometimes it will be within the topic. The expressions must be user readable (eg.: module is views with version greater than 3.0). There can be 3 kind of displays of a conditional text: visible, hidden, collapsed fieldset, which can be chosen by the site builder.
Read more