obsidian-enhancing-export VS pages-gem

There's also: https://github.com/mokeyish/obsidian-enhancing-export , which also gets good reports.

I just wanted to share my first successful addition to an Obsidian plugin. I've made two academic templates and added a the ability to select them through the Obsidian Enhancing Export plugin.

I've tried using Obsidian Enhancing Export, but it froze up Obsidian. I'm currently trying the Pandoc plugin, and while it works a bit better, still leaves so much to be desired.

To convert Markdown to HTML inside Obsidian, I've had the best luck with Obsidian Enhancing Export. That in turn requires you install pandoc, which isn't hard but is an extra step. I think you'd have to convert them one at a time if you use this UI.

For exporting, check out Enhancing Export plugin. You can export notes in .doc, .rtf, etc. formats. https://github.com/mokeyish/obsidian-enhancing-export

You could use pandoc and specify the twocolumn option (please see https://stackoverflow.com/a/34809186). You could use pandoc standalone or use it through some Obsidian plugins (obsidian-pandoc, obsidian-enhancing-export)

Also available: https://github.com/mokeyish/obsidian-enhancing-export

There's also obsidian-enhancing-export

It's super easy to publish a static site like the resume with GitHub Pages. Just check out the docs.

GitHub Pages: Host your static websites directly from your GitHub repository.

As per many other comments, it sounds like a static site generator like Hugo (https://gohugo.io/) or Jekyll (https://jekyllrb.com/), hosted on GitHub Pages (https://pages.github.com/) or GitLab Pages (https://about.gitlab.com/stages-devops-lifecycle/pages/), would be a good match. If you set up GitHub Actions or GitLab CI/CD to do the build and deploy (see e.g. https://gohugo.io/hosting-and-deployment/hosting-on-github/), your normal workflow will simply be to edit markdown and do a git push to make your changes live. There are a number of pre-built themes (e.g. https://themes.gohugo.io/) you can use, and these are realtively straightforward to tweak to your requirements.

Ideal for open source projects, docs sites, and portfolios. GitHub Pages

Github Pages: Link to Github Pages

Once you have all the documentation worked out a place to host it will be necessary. Some documentation generation may have ties in with specific hosting sites. Read The Docs' support for Sphinx and other documentation tools is one example. GitHub pages can be useful for GitHub hosted projects as it integrates well with GitHub Actions CI/CD deployments.

If you use GitHub and need to host a static website, consider GitHub Pages. Free for one site Stored on a GitHub public respository Deploy via web interface, or Git 100GB/month free bandwidth

https://pages.github.com/ https://docs.github.com/en/pages https://docs.github.com/en/pages/quickstart https://docs.github.com/en/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll

There are plenty of other hosting options you could use instead, such as GitHub Pages.

Functionally github.io just presents whatever you throw into the repository as the root directory of a site, github themselves host a very good, basic outline of how to set up a site on github.io.