The idea of publishing content from one org file is very
impressed. But whatever one.el is designed to create small
and simple sites.
For examples, your sites on subdomains are small. By the
way, Google counts sites on the subdomains as separate and
sees them each as a separate small site with the corresponding rating.
"One" is trying to process the markup of the org with its
limited parser. There are tools in Org for processing itself.
There is no project structure. There are no exceptions to
publication for some files. A lot of things are not exist
what org-publish able to offer.
People who want to publish from 1 org file will find this "One".
But having examined it, they will ask why it has little functions.
How about taking part from One.el, which is responsible for
publication from 1 org file and send the withdrawal of
separate files to the Org-publish project folder.
That is code that converts the single org into separate
posts, standart separated org files.
Next standart workflow can be launched by the org-publish.
Org-pubslish can only publish from the original form 1 org file in 1 HTML page. It will work with these separate org files in their order as established.
The organizer mechanism can be used and by running
separation into a separate files from headings with the
status of Done, taking from heading their creation time that
is automatically recorded into :LOGBOOK: when changing the status of the org-heading.
It will be possible to send people who want 1 org file and
More functions to this "converter" code. This code can gain more popularity than One.el.
The idea of publishing content from one org file is very impressed. But whatever one.el is designed to create small and simple sites. For examples, your sites on subdomains are small. By the way, Google counts sites on the subdomains as separate and sees them each as a separate small site with the corresponding rating.
"One" is trying to process the markup of the org with its limited parser. There are tools in Org for processing itself.
There is no project structure. There are no exceptions to publication for some files. A lot of things are not exist what org-publish able to offer.
People who want to publish from 1 org file will find this "One". But having examined it, they will ask why it has little functions.
How about taking part from One.el, which is responsible for publication from 1 org file and send the withdrawal of separate files to the Org-publish project folder.
That is code that converts the single org into separate posts, standart separated org files.
Next standart workflow can be launched by the org-publish. Org-pubslish can only publish from the original form 1 org file in 1 HTML page. It will work with these separate org files in their order as established.
The organizer mechanism can be used and by running separation into a separate files from headings with the status of Done, taking from heading their creation time that is automatically recorded into :LOGBOOK: when changing the status of the org-heading.
It will be possible to send people who want 1 org file and More functions to this "converter" code. This code can gain more popularity than One.el.