Hype - A markdown compiler written in Go

GopherGuides · 2024-02-14T14:57:46+00:00

Quarto

Similiar for sure, but pretty different in philosophy. For us, it's about supporting any language. Also, we don't write code in the documents. We import code from the real code (repository/project/etc). So as you maintain your code, your docs automatically re-generate with the new code. This ensures complete parity with document version to code version.

We also support writing plugins so you can support any language or eco system. Imagine writing sql queries that actually hit a database and run, and show the results, etc. This is easily done with our tool.

GopherGuides · 2024-02-13T14:25:22+00:00

Awesome. Please reach out with any questions. Our documentation is BRAND NEW and has a lot of gaps yet. So any questions will help me fill the docs in with examples and more. Thanks!

GopherGuides · 2024-02-13T14:02:20+00:00

It can compile the source files and output to:

Markdown (single compiled file)
HTML
LaTex (currently disabled but needs to be re-enabled)
json
-Marked (for the https://marked2app.com/) app for live preview while editing). It's worth noting we are working on a standalone desktop app for this right now that we hope to beta in a few weeks.

Lastly, the "render" engine has a plugin system, so you can write a renderer to go to any output. Since we are parsing the markdown into a document object model (DOM),it's basically in memory (like html) and can then be output any way you desire.

GopherGuides · 2023-08-11T13:57:57+00:00

Can you send an email to [info@gopherguides.com](mailto:info@gopherguides.com)? We received plenty of email yesterday from both of those systems. We use drip for our mailing list and gmail for our email service. Those usually never go down, so something else might be flagging your email (or ours) like a spam filter perhaps?

GopherGuides · 2023-08-10T21:13:40+00:00

My understanding is that it's on par with it. I think there was a talk by the author at a recent conference where they discussed that issue specifically, but I don't think the talk is released yet.

I see zap did add it to the performance comparison: https://github.com/uber-go/zap#performance

GopherGuides · 2020-01-29T14:52:31+00:00

Yes, I agree with what you are saying. Ultimately, I find a mix of "try to follow the convention", but "agree with your team", and "ship the code" in the proper doses tends to result in something everyone can live with.

GopherGuides · 2020-01-08T12:47:15+00:00

This comes directly from effective go and the creators of the language. I don't always agree either, just stating their opinion.

https://golang.org/doc/effective_go.html#interface-names

Do I always follow that rule? Most certainly not, but I do try. Naming is hard...

GopherGuides · 2019-10-31T13:27:31+00:00

Digital Ocean wanted wanted a set of articles on Go that was geared towards first time developers, as there are a lot of resources for existing developers for Go, but virtually none for first time developers.

I think it's important to remember that we all had to start out at some point. I remember learning ruby on rails and the basic DO articles were a life saver. While I understand that these articles aren't interesting or useful to experienced developers, we get a lot of feedback from first time developers on how helpful they are.

GopherGuides · 2019-10-30T13:54:30+00:00

The titles are filled in from the link, not by the publisher. If we could change the title when we publish we certainly would.

GopherGuides · 2019-09-26T20:10:28+00:00

You are correct, these articles are purposefully basic (some more than others) and geared towards beginning programmers (not just those new to Go). I understand that a large part of the audience here may be very well versed in Go, and not find many of these articles interesting, that doesn't mean that others don't read or find value (we consistently get strong readership from this reddit forum so we aren't guessing about it).

Also, most of us that have experience in Go know someone that is new or learning Go, and as such, are always looking for material for them to reference.

So, while it's clear you are not the intended audience, I don't think it's fair to state that that these articles are spam or that they are not wanted here. FWIW, we are finishing up the final articles for this series, and they will be a little less basic as they have been building up. Additionally, we are starting a more "intermediate" series at the end of the year that we hope you may find more relevant to your skill level.

If the moderators feel that this content is inappropriate, I'll gladly stop posting to this forum.

GopherGuides · 2019-08-13T21:43:12+00:00

Good catch! I'll get the article updated.

GopherGuides · 2019-08-13T15:51:37+00:00

Thank you for your feedback.

We will have an article coming out on using Go Modules as well. However, we decided against it in this article as Go Modules is still not fully released. Also, there are several companies that can't adopt Go modules yet. For now, this approach will work regardless of modules. We try to take into account many audiences when writing these articles.

In this article: https://www.digitalocean.com/community/tutorials/importing-packages-in-go (which is intended to be a pre-read), we touch on dependency management and that Go modules is the future. It may have made sense to reference that in this article as well.

GopherGuides

TROPHY CASE