Our great sponsors
-
-
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
-
-
evidence
Business intelligence as code: build fast, interactive data visualizations in pure SQL and markdown
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
not sure why they insist on hiding this, but here is the source:
https://github.com/nota-lang/nota
Hi, Nota creator here. A high-level comment:
After developing the initial prototype you see in the webpage, I've since gone back to the drawing board. I'm working on developing a firmer foundation for issues like:
- How do you interleave content and computation? See: https://arxiv.org/abs/2310.04368
- How do different syntaxes make different document tasks easy, hard, or impossible? See: https://github.com/cognitive-engineering-lab/doclang-benchma...
I still very much believe in the high-level philosophy, but Nota will look very different within ~6 months.
Hi, Nota creator here. A high-level comment:
After developing the initial prototype you see in the webpage, I've since gone back to the drawing board. I'm working on developing a firmer foundation for issues like:
- How do you interleave content and computation? See: https://arxiv.org/abs/2310.04368
- How do different syntaxes make different document tasks easy, hard, or impossible? See: https://github.com/cognitive-engineering-lab/doclang-benchma...
I still very much believe in the high-level philosophy, but Nota will look very different within ~6 months.
I would very highly recommend Astro [0]. Astro lets you write React-style components that compile to plain HTML/CSS (unless you _actually_ need JavaScript). My personal site and blog [1] is built with Astro
Here's their tutorial on building a blog with Astro: https://docs.astro.build/en/tutorial/0-introduction/
[0]: https://astro.build/
[1]: https://sjer.red/ source at https://github.com/shepherdjerred/shepherdjerred.com
I would very highly recommend Astro [0]. Astro lets you write React-style components that compile to plain HTML/CSS (unless you _actually_ need JavaScript). My personal site and blog [1] is built with Astro
Here's their tutorial on building a blog with Astro: https://docs.astro.build/en/tutorial/0-introduction/
[0]: https://astro.build/
[1]: https://sjer.red/ source at https://github.com/shepherdjerred/shepherdjerred.com
[1] https://github.com/pypa/readme_renderer/issues/205
Also https://docusaurus.io/ is very nice and flexible.
I suggest to look at these two to extend nota in similar way
Of course, it is now much less flexible, as you cannot define a custom label or different placement instructions. But that is the price you pay for short and memorable syntax.
By the way, developing a LaTeX class is not hard. It is more or less a file whose name ends in `.cls` with all the commands that you typically put in your preamble. It just needs a header of three lines that define some meta data and also supports options. See here for an example: https://github.com/latex-ninja/colour-theme-changing-class-t...
You put it in the same directory as your main tex file or in the system wide TEXMFHOME or user-specific TEXMHFHOME.
Of course, it is now much less flexible, as you cannot define a custom label or different placement instructions. But that is the price you pay for short and memorable syntax.
By the way, developing a LaTeX class is not hard. It is more or less a file whose name ends in `.cls` with all the commands that you typically put in your preamble. It just needs a header of three lines that define some meta data and also supports options. See here for an example: https://github.com/latex-ninja/colour-theme-changing-class-t...
You put it in the same directory as your main tex file or in the system wide TEXMFHOME or user-specific TEXMHFHOME.
> Not sure the language you choose matters as much as making the API usable by a wide audience.
Fully agree with this, and having typeset my masters thesis and later my resume using LaTeX, I think that the “authoring experience” is 100% the place to focus on improving.
If you’re interested in the “markup to document publishing” space, you might also be interested in the open-source report publishing tool I’m now working on, Evidence (https://github.com/evidence-dev/evidence)
It’s similarly based on markdown, though uses code fences to execute code, HTML style tags for charts and components, and {…} for JavaScript, i.e.
---