or Fork this repo to get started.
#+export_file_name: index
to get started I have added some cool themes in the repo. they help you make your pages look better than the plain text which is also completely fine tbh
#+setupfile: <theme file path>
the option used in this file actually is as follows
setupfile: ./theme-readtheorg.setup
As we are going to use static HTML all our org files will be dispatched to html using the following setting. just add the source and destination of the .org file and .html file that will be created from them respectively..
(setq org-publish-project-alist
'(("my-org-files"
;; Path to the directory containing your Org files
:base-directory "~/path/to/where/this/repo/is/cloned"
;; Path to the directory where HTML files will be exported
:publishing-directory "~/destination/for/html/files/to/be/exported"
:recursive t
:publishing-function org-html-publish-to-html
:headline-levels 4 ;; Just the default for this project
:auto-sitemap t ;; Generate sitemap.org automatically
:sitemap-filename "sitemap.org" ;; Name of the sitemap file
:sitemap-title "My Sitemap" ;; Title for the sitemap
:sitemap-style list))) ;; Style of the sitemap with list, tree, and folder options can be used instead as well.
these will be the files that will be basically the pages in your github page. it can be anything, literally.
this will populate the publishing-directory with final html files created from the .org files.
notice html files, sitemap.org, being created for the repo.
- wait for some time.
- refresh
make README just a landing page for all steps list.
check if denote can be used for ORG Blog Forge.
this is not possible as github looks for html files in the root and in order to make it look in a seperate folder we need to change the default which would be somehting that i would keep in the scope of the user.
Thanks to