Once you have a domain^1, and connect it to an #IndieWeb service like https://micro.blog, or a https://indieweb.org/CMS on https://indieweb.org/web_hosting, you can focus^2 on your writing. Or if you enjoy #webDevelopment and want to build (option three^3), use developer services to more rapidly add IndieWeb building blocks^4 to your site so you too can focus on creating & owning your content^5. Here are some of the most common and popular developer services: 1. Webmention sending: https://webmention.app/ by https://remysharp.com/ (@rem@front-end.social), or https://mention.tech/ by https://kevinmarks.com/ (@kevinmarks@xoxo.zone) 2. Webmention receiving: https://webmention.io/ (I use this) by https://aaronparecki.com/ or https://webmention.herokuapp.com/ by https://voxpelli.com/ (@voxpelli@mastodon.social) 3. POSSE & backfeed: https://brid.gy/ by Ryan of https://snarfed.org/ (@schnarfed) 4. ActivityPub federating: https://fed.brid.gy/ also by Ryan. More on Bridgy & Bridgy Fed^6. Using a developer service to support IndieWeb protocols saves you time. You can also contribute to the community by filing suggestions for improvements, or participating on their GitHub repositories. If you prefer that your site not depend on any external services, you can do that too. Most of the above services are also open source that you can install and fully manage yourself. For example: * Webmention installable services: https://indieweb.org/Webmention#Publisher_Services Another option is to use one of many open source libraries to more rapidly implement support for IndieWeb standards^7. The wiki pages for each standard list libraries in a variety of programming languages, e.g.: * https://indieweb.org/Webmention-developer#Libraries If you choose the path of installing or building something new with libraries or by directly implementing an IndieWeb standard, be sure to test your implementation with its test suite, e.g.: * https://webmention.rocks/ As a web developer, you can choose how much of your #IndieWeb support you want to implement yourself (and time to invest) vs build on the services, libraries, and other open source that the community has produced and is actively supporting. This is day 10 of #100DaysOfIndieWeb #100Days. ← Day 9: https://tantek.com/2023/009/t2/edit-reply-comment-update → Day 11: https://tantek.com/2023/011/t1/indieweb-evolving-at-mention ^1 https://tantek.com/2023/004/t1/choosing-domain-name-indieweb ^2 https://tantek.com/2023/005/t3/indieweb-simpler-approach ^3 https://tantek.com/2023/003/t1/indieweb-path-chosen-why ^4 https://indieweb.org/building_blocks ^5 https://tantek.com/2023/001/t1/own-your-notes ^6 https://tantek.com/2023/008/t7/bridgy-indieweb-posse-backfeed ^7 https://spec.indieweb.org/

Once you have a domain¹, and connect it to an #IndieWeb service like https://micro.blog, or a https://indieweb.org/CMS on https://indieweb.org/web_hosting, you can focus² on your writing.

Or if you enjoy #webDevelopment and want to build (option three³), use developer services to more rapidly add IndieWeb building blocks⁴ to your site so you too can focus on creating & owning your content⁵.

Here are some of the most common and popular developer services:
1. Webmention sending: https://webmention.app/ by https://remysharp.com/ (@rem@front-end.social), or https://mention.tech/ by https://kevinmarks.com/ (@kevinmarks@xoxo.zone)
2. Webmention receiving: https://webmention.io/ (I use this) by https://aaronparecki.com/ or https://webmention.herokuapp.com/ by https://voxpelli.com/ (@voxpelli@mastodon.social)
3. POSSE & backfeed: https://brid.gy/ by Ryan of https://snarfed.org/ (@schnarfed)
4. ActivityPub federating: https://fed.brid.gy/ also by Ryan. More on Bridgy & Bridgy Fed⁶.

Using a developer service to support IndieWeb protocols saves you time. You can also contribute to the community by filing suggestions for improvements, or participating on their GitHub repositories.

If you prefer that your site not depend on any external services, you can do that too.

Most of the above services are also open source that you can install and fully manage yourself. For example:
* Webmention installable services: https://indieweb.org/Webmention#Publisher_Services

Another option is to use one of many open source libraries to more rapidly implement support for IndieWeb standards⁷. The wiki pages for each standard list libraries in a variety of programming languages, e.g.:
* https://indieweb.org/Webmention-developer#Libraries

If you choose the path of installing or building something new with libraries or by directly implementing an IndieWeb standard, be sure to test your implementation with its test suite, e.g.:
* https://webmention.rocks/

As a web developer, you can choose how much of your #IndieWeb support you want to implement yourself (and time to invest) vs build on the services, libraries, and other open source that the community has produced and is actively supporting.

This is day 10 of #100DaysOfIndieWeb #100Days.

← Day 9: https://tantek.com/2023/009/t2/edit-reply-comment-update
→ Day 11: https://tantek.com/2023/011/t1/indieweb-evolving-at-mention

¹ https://tantek.com/2023/004/t1/choosing-domain-name-indieweb
² https://tantek.com/2023/005/t3/indieweb-simpler-approach
³ https://tantek.com/2023/003/t1/indieweb-path-chosen-why
⁴ https://indieweb.org/building_blocks
⁵ https://tantek.com/2023/001/t1/own-your-notes
⁶ https://tantek.com/2023/008/t7/bridgy-indieweb-posse-backfeed
⁷ https://spec.indieweb.org/