Skip to content

docs(developer): Add Developer walkthrough tutorial#15447

Merged
mcdurdin merged 16 commits intomasterfrom
walkthrough
Mar 16, 2026
Merged

docs(developer): Add Developer walkthrough tutorial#15447
mcdurdin merged 16 commits intomasterfrom
walkthrough

Conversation

@DavidLRowe
Copy link
Copy Markdown
Contributor

@DavidLRowe DavidLRowe commented Jan 16, 2026

TODO:

  • Links from existing content --> docs: remove old content that is deprecated by walkthrough #15710

  • Compare old tutorials for content match

  • Retire old tutorials --> docs: remove old content that is deprecated by walkthrough #15710

  • We want to eliminate the other tutorials over time, so we should avoid referencing them in 03-creating-desktop-layout

    "A summary of the elements of the Keyman header can be found in part of another tutorial and detailed information is in the official Keyman documentation:"

  • The walkthrough belongs at the same level as the 'Keyman Developer Guides' topic /guides/walkthrough, rather than guides/develop/walkthrough [MD] --> docs: move walkthrough up one level #15711

  • Avoid confusion in following paragraph in 03-creating-desktop-layout --> docs: tweak walkthrough content #15712

    Note that rules created when using the Design tab use virtual key codes rather than the corresponding characters. This does not matter unless you are writing a mnemonic layout keyboard. Keyman keyboards are positional by default, so unless you specify a mnemonic layout in your header, the following two lines of code will produce the same output:

  • Move 'interpreting errors' section from 04-using-debugger --> docs: tweak walkthrough content #15712

    Interpreting Errors

    This section feels like it would belong better elsewhere, under creating-desktop-layout, probably


Post-merge TODO:

  • Promote

Build-bot: skip
Test-bot: skip

@github-project-automation github-project-automation Bot moved this to Todo in Keyman Jan 16, 2026
@keymanapp-test-bot keymanapp-test-bot Bot added the user-test-missing User tests have not yet been defined for the PR label Jan 16, 2026
@keymanapp-test-bot
Copy link
Copy Markdown

keymanapp-test-bot Bot commented Jan 16, 2026

User Test Results

Test specification and instructions

User tests are not required

@keymanapp-test-bot keymanapp-test-bot Bot added this to the A19S20 milestone Jan 16, 2026
@DavidLRowe
Copy link
Copy Markdown
Contributor Author

Test-bot: skip.

Not sure if this is needed?!

@keymanapp-test-bot keymanapp-test-bot Bot removed the user-test-missing User tests have not yet been defined for the PR label Jan 16, 2026
@darcywong00
Copy link
Copy Markdown
Contributor

Not sure if this is needed?!

I think you edit the PR description and have at the bottom of the text area:

Test-bot: skip

@darcywong00 darcywong00 changed the title Walkthrough tutorial docs(developer): Add Developer walkthrough tutorial Jan 16, 2026
@keyman-server keyman-server modified the milestones: A19S20, A19S21 Jan 16, 2026
Copy link
Copy Markdown
Contributor

@darcywong00 darcywong00 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the extensive work in migrating this from Notion!

Just a few initial comments for now. Some may warrant more discussion before making changes throughout.

Comment thread developer/docs/help/guides/develop/walkthrough/index.md Outdated

Keyman Developer is a powerful tool you can use to create custom keyboards optimized to type in any language you choose. Keyboard authors can distribute their work for desktop, web, tablet and phone, enabling global communities to quickly benefit from keyboards made for their own language.

Keyboards created with Keyman Developer can be used on Windows, Mac, Linux, iOS, Android, and the web.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we generally try to be consistent in using "macOS" instead of "Mac" or "MacOS". (See l.20, 32, etc)


After installing Keyman Developer, you should be able to run it on your computer and begin creating projects immediately.

Note that Keyman Developer is a separate app from Keyman, which is the app that lets you use any keyboard created with Keyman Developer.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can style "notes" like

Suggested change
Note that Keyman Developer is a separate app from Keyman, which is the app that lets you use any keyboard created with Keyman Developer.
> [!Note]
> Keyman Developer is a separate app from Keyman, which is the app that lets you use any keyboard created with Keyman Developer.

and would look like

Image

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When the text came out of Notion, some of the notes were marked with HTML, others with the >, but then the links that were in those paragraphs didn't work, so I ended up removing the markup for notes and tips. My preference would be to wait on adding markup to style the notes.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, let's worry about integration before minor styling details

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fair enough. I was just looking to have consistency in the styling across the site. But yeah can focus on content now

title: Introduction
---

[Next: Part 1 - Creating a Keyboard Project →](01-creating-keyboard-project)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The knowledge-base folder uses < and > for navigation arrows.
We probably don't want to implement a separate .php file

https://github.com/keymanapp/help.keyman.com/blob/29cf16f40ab32e3e37446de1ca0ef63a739fe116/knowledge-base/index.php#L51-L53

Image

but for now maybe we just replace the arrows ?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the arrows here are nicer than the ones in the KB and I am not sure why we would be worrying about this anyway @darcywong00?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Original author used the arrows. I've changed them to wedges.


### Installing Keyman Developer

Keyman Developer is completely free to download and use. You can download it from [https://keyman.com/developer/download](https://keyman.com/developer/download).
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we make all the help.keyman.com links relative?

like
/developer/download

and all the
/developer/17.0/
/developer/18.0/ links become

/developer/current-version/

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not a relative link. But relative links on help.keyman.com are a good idea with /developer/current-version in order to avoid linking people into old content (and it also means if content shifts around, we will be prompted to update the tutorial accordingly).

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tried to follow @mcdurdin 's advice on links, but could easily have goofed it up!

@keyman-server keyman-server modified the milestones: A19S21, A19S22 Jan 31, 2026
@github-actions github-actions Bot added the docs label Feb 2, 2026
in response to Darcy's suggestion

Co-authored-by: Darcy Wong <darcy_wong@sil.org>
@github-actions github-actions Bot added docs and removed docs labels Feb 2, 2026
@github-actions github-actions Bot added docs and removed docs labels Feb 2, 2026
@github-actions github-actions Bot added docs and removed docs labels Feb 2, 2026
Co-authored-by: Darcy Wong <darcy_wong@sil.org>
Copy link
Copy Markdown
Member

@mcdurdin mcdurdin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Moved TODO to top comment for visibility

@DavidLRowe
Copy link
Copy Markdown
Contributor Author

@mcdurdin What's the status on this PR? Do I need to make some changes?

@mcdurdin
Copy link
Copy Markdown
Member

@mcdurdin What's the status on this PR? Do I need to make some changes?

#15595 has some changes that would be good for you to look at.

Then I think I need to work through the first 3 TODO items in #15447 (review) before we can merge this.

@keyman-server keyman-server modified the milestones: A19S23, A19S24 Feb 27, 2026
@github-actions github-actions Bot added docs and removed docs labels Mar 5, 2026
@mcdurdin
Copy link
Copy Markdown
Member

mcdurdin commented Mar 5, 2026

I have consolidated the TODO list in the PR description

mcdurdin and others added 6 commits March 9, 2026 15:04
Remove old content and place redirects where the content is adequately
replaced by the new walkthrough. Leaves some content which does not
overlap the walkthrough. Moved reference information about package
contents.

Test-bot: skip
Test-bot: skip
Build-bot: skip
Co-authored-by: Eberhard Beilharz <ermshiperete@users.noreply.github.com>
docs: remove old content that is deprecated by walkthrough
@github-actions github-actions Bot added docs and removed docs labels Mar 13, 2026
@github-actions github-actions Bot added the docs label Mar 13, 2026
@github-actions github-actions Bot added docs and removed docs labels Mar 13, 2026
@keyman-server keyman-server modified the milestones: A19S24, A19S25 Mar 14, 2026
@mcdurdin mcdurdin merged commit a6225bf into master Mar 16, 2026
6 checks passed
@mcdurdin mcdurdin deleted the walkthrough branch March 16, 2026 03:54
@github-project-automation github-project-automation Bot moved this from Todo to Done in Keyman Mar 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

4 participants