Wiki Help
How to edit
The ALB wiki is written by its readers — anyone can edit any page, no account needed. Click the Edit tab on any article, change the text, write a short summary, and hit Save page. Your change is live immediately and kept in the page's history forever.
Be bold. If you see something wrong or missing, fix it — you can't break anything, every old revision is kept.
Markup
The wiki uses Markdown plus wiki-style Links:
| What you want | What you type |
|---|---|
| Headings | # Title, ## Section, ### Part |
| Bold / italic | bold, italic |
| Inline code | \PRINT\`` |
| Code block | a fenced block starting and ending with \\\` |
| Bullet list | - item |
| Numbered list | 1. item |
| Quote | > words |
| Internal link | Page name or shown text |
| Category | Category:Name anywhere in the page |
| External link | label |
| Horizontal rule | --- on its own line |
Links
Internal links are the wiki's connective tissue. Type Getting Started and the wiki links it automatically:
- Blue links go to pages that exist.
- Red links go to pages that don't exist yet — click one to create it. Red links are invitations, not errors.
- Use
the languageto show different text than the page name.
Categories
Put Category:Reference anywhere in a page's text to file it. The category box appears at the bottom, and the page shows up automatically at Category:Reference's listing. Categories are created just by being used — no setup needed.
History, diffs, and reverting
- The History tab lists every revision ever made — who, when, and the summary.
- Click diff next to any revision to see exactly what changed.
- Click revert to restore an older revision. A revert is itself a new revision — history is never destroyed, and vandalism can be undone by anyone in seconds.
Good pages to write
This wiki's first subject is AdaLogic BASIC. Great contributions include:
- Language reference pages — one page per statement or function
- Tutorials and worked examples
- Patterns and idioms — how to structure an ALB program
- Gotchas, pitfalls, and frequently asked questions
- Glossary pages for terms beginners meet
Style notes
- Keep it family-friendly — this is a learning site.
- Write plainly and factually; teach, don't advertise.
- Prefer short sections with headings over one wall of text.
- Code examples should be real, working ALB.
- Always fill in the summary line — it makes Recent Changes and History readable.
House rules
- Edits are public immediately — don't post private information.
- Pages can be protected and edits logged; spam and vandalism get reverted quickly.
- Anonymous edits are attributed "Anonymous"; signed-in members get credited by username.