CommunityWriterPrograms VS documentation

View on GitHub

You could try writing blog posts for a company[1]. I haven't done this but I know people who have. It's crazy what some companies pay for such low-quality content sometimes.

[1] https://github.com/malgamves/CommunityWriterPrograms

Community Writer Programs

Applying for jobs has to be the biggest headache for technical writers. There are lots of writing and guest author programs here for technical writers to apply to. There are also Paid Community Programs and Community Writer Programs carefully curated for writers.

Check this page https://github.com/malgamves/CommunityWriterPrograms

There are so many great resources to learn about technical writing. Such as Emy’s article about “Starting Out With Technical Writing”, Yuri’s curated list of technical writing resources and Bonnie’s own book and resources to technical writing and Daniel’s GitHub repo which contains lists of paid technical resources.

I run Draft.dev, so of course, I think we're the best, but I also help maintain this big list: https://github.com/malgamves/CommunityWriterPrograms

Several platforms exist that pay developers for composing articles and or tutorials. A list of such writer programs can be found at here.

Suitability for content-first sites (marketing/personal/portfolio sites) Components and Dynamic Zones will be very helpful to allow content editors to build pages on the fly by reusing components you, as a developer, will configure (based on your Astro components) for them. Was the free plan adequate or did you find yourself nearing limits or having to go for paid plans? Free if you self-host but paid if you use Strapi Cloud. I understand you want to use a free plan but do make sure you anticipate the limits of free plans (which you might quickly reach) as the gap from free to paid can be high for some solutions. General developer experience and time/simplicity to set up Strapi has been created by developers for developers. You should easily get started https://docs.strapi.io/ :) User experience as a content manager using the CMS to make changes to the sit As mentioned above, Components and Dynamic Zones will help a lot. Content managers will enjoy other features such as role-based access control, content internationalization, custom fields, media library, etc.

With practice comes perfection. The only way to be a great technical writer is to write more. The more you write, the more you learn and get better. Once you are comfortable writing for the Write For the Community program at Strapi, you may also venture into contributing to making our documentation better.

Strapi’s core issues and documentation issues.

Fortunately this managed to get solved here https://github.com/strapi/documentation/issues/849

Strapi Documentation Next.js documentation 10 Reasons you should use a Headless CMS

How is this different than something like Strapi?