DEV.to Reviews

1. jorge

   · CEO at Escuela de Formación Técnica Chile SPA · over 6 years ago
   It is a nice mini-blog, it's for free and such but

   As a mini-blog, it is a nice alternative for Medium to publish and share information about programming.

   However, the community and the organization are biased toward social justice (and they are open to it). You can read its Code of Conduct, it is so vague and politically leads (I prefer a term of service because it defines fair rules for everybody). So it alienates developers that we don't care about politics in pro of people that want to talk about any other topic such as sexuality, how women are unprivileged, and such. It even mandates to use inclusive language. Good grief.

   My main complaint is the quality of the community. It is not StackOverflow (so we don't want to ask for an answer here), and most of the top topics are clickbait, such as "how to become a rockstar developer in ... days", "100 tips to become a better programmer" (and it doesn't even talk about programming).

   Technically this "mini blog" site allows us to use markdown, and it is okay. However, the whole experience is really basic. Even the template is ugly.

   🏁 Competitors: Medium

   👍 Pros:    Free

   👎 Cons:    Social justice|Basic features|Quality of content

Docusaurus Reviews

DEV.to mentions (664)

• Stop Arguing About Which Model Is Best. Build a Two-Tier Habit Instead.

  Verifiable only with effort. Anything touching the filesystem, package installs, CI config, database changes. Wrongness here is quiet and expensive. These get the strongest model I have and a sandboxed dry run before anything executes. I wrote a separate piece on dry-running assistant-written shell commands because this category keeps hurting people. - Source: dev.to / about 24 hours ago

• My Comment-Reply Pipeline Picks One Winner Per Thread. Two Commenters Broke That.

  Def _pending_leaves(comment): if not comment["children"]: if comment["user"]["username"] != ME: yield comment return for child in comment["children"]: yield from _pending_leaves(child) Def _pending_entries(comment, drafted_codes): for leaf in _pending_leaves(comment): if leaf["id_code"] in drafted_codes: continue yield { ... - Source: dev.to / 1 day ago

• Your first Fitz LiveViews component, twice: SSR and WASM from one source

  In part 1 I made the pitch: real-time UI in one language, no JavaScript build. Now let's build something and ship it two ways from the same source. - Source: dev.to / 8 days ago

• My Comment-Reply Queue Draft One Reply to a Thread and It Went Deaf to Every Follow-Up After That

  Def pending(): try: drafted_text = open(DRAFTS, encoding="utf-8").read() except FileNotFoundError: drafted_text = "" drafted_codes = set(re.findall(r"^## (\S+)", drafted_text, re.M)) out = [] for a in api(f"/articles?username={ME}&per_page=100"): if not a["comments_count"]: continue for c in api(f"/comments?a_id={a['id']}"): if not... - Source: dev.to / 12 days ago

• Domain Search to Render: How the web works behind the scenes

  To think that all of this happens under the hood when I’m just trying to access YouTube to listen to my favorite music playlists to go through the day is insane! It all happens so quickly… to think that all eleven of these steps occur instantly when I was first entering a website like https://dev.to, for instance, is mind-blowing. - Source: dev.to / 12 days ago

Docusaurus mentions (225)

• I built a GUI-powered Userscript manager for faster userscript creation!

  I used Docusaurus to host my documentation website. Although it used mdx (based on React) while the rest of my website was using Svelte, there just wasn't a solution that worked nearly as well out of the box. There I made some basic tutorials and wrote documentation for the API. - Source: dev.to / 4 months ago

• 🦊 GitLab CI: Automated Testing of Job Rules

  If you use a doc-as-code tool like VitePress, Asciidoctor, or Docusaurus, you can render CSV files as HTML tables at build time — either natively or through a custom plugin. Most tools support CSV includes out of the box or with minimal effort, and any AI assistant can generate the glue code for your specific stack in seconds. - Source: dev.to / 8 months ago

• Choosing Your Documentation Tooling: A Practical Guide

  There's no shortage of documentation tools out there, and honestly, that can make the decision harder rather than easier. After working with various clients and our own projects here at Digital Speed, we've found ourselves reaching for a handful of tools repeatedly: Docusaurus, VuePress, Redocly, and Fumadocs. - Source: dev.to / 7 months ago

• Technical Writers Are Not Junior Developers

  Docusaurus is a popular choice for developer-first documentation, especially for teams that prefer Git-based workflows and static site generation. - Source: dev.to / 7 months ago

• # Why I Chose Mintlify (And What I Wish I Knew Earlier)

  Docusaurus gives you complete control. It's open-source, React-based, and incredibly flexible. The trade-off? You're essentially maintaining a website. For a solo technical writer at a startup, that overhead wasn't something I could justify. - Source: dev.to / 7 months ago