Skip to content

Getting Started Guide for extension development#896

Draft
freisenhauer wants to merge 32 commits intomasterfrom
feature/extension-getting-started-guide
Draft

Getting Started Guide for extension development#896
freisenhauer wants to merge 32 commits intomasterfrom
feature/extension-getting-started-guide

Conversation

@freisenhauer
Copy link
Contributor

No description provided.

title: Contributor werden
---

TODO: Inhalt folgt
Copy link
Member

Choose a reason for hiding this comment

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

Doesn't look like this is ready for review yet, does it? Mind switching this PR back to "Draft" state for the time being?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

true, forgot to set draft, sorry.

@freisenhauer freisenhauer force-pushed the feature/extension-getting-started-guide branch from 08e51eb to 9b87800 Compare January 21, 2026 16:39
@freisenhauer freisenhauer marked this pull request as draft January 24, 2026 09:36
@freisenhauer freisenhauer force-pushed the feature/extension-getting-started-guide branch from e5dfc4e to aeb4f61 Compare January 30, 2026 11:23
@gandie gandie self-assigned this Jan 30, 2026
@gandie
Copy link
Contributor

gandie commented Feb 2, 2026

Diving into this one for onboarding, training and testing 👀

@gandie gandie force-pushed the feature/extension-getting-started-guide branch from aeb4f61 to f9c90f6 Compare February 4, 2026 14:24
projectName: "developer-portal", // Usually your repo name.

onBrokenLinks: "throw",
onBrokenLinks: "warn",
Copy link
Contributor Author

Choose a reason for hiding this comment

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

oh should we really make this less strict?

Copy link
Contributor

Choose a reason for hiding this comment

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

No no, this is just to get through build at all, fixing links and anchors is something i prefer doing as final steps, when guide structure is clear.


:::warning Keine nativen HTML-Elemente
Für die Entwicklung von Frontend Fragments können, bis auf wenige Ausnahmen, keine nativen HTML-Elemente wie `<div>`, `<span>` oder `<button>` verwendet werden.
Für die Entwicklung von Frontend Fragments können, bis auf wenige [Ausnahmen](../../40-how-to/10-develop-frontend-fragment.mdx), keine nativen HTML-Elemente wie `<div>`, `<span>` oder `<button>` verwendet werden.
Copy link
Contributor Author

Choose a reason for hiding this comment

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

We should maybe add a fragment to the URL to get to the corresponding section (if it exists, lol).


Wir empfehlen [zrok](https://zrok.io/) als Open Source und kostenlose Variante.

[//]: # TODO: Rly? What about: https://github.com/mittwald/extension-accessibility-checker?tab=readme-ov-file#load-the-frontend-fragments
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'm not quite following, to be honest. Could you briefly describe what you mean?

Copy link
Contributor

Choose a reason for hiding this comment

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

Found this hint in the accessiblity checker extension, which seemed to me like i could just set some variable in the browser local storage in order to connect my extension to mStudio for development. Not sure if this fully replaces a tunnel, though.

@freisenhauer freisenhauer force-pushed the feature/extension-getting-started-guide branch from dc1051d to 847b7a8 Compare February 12, 2026 16:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants