Replies: 1 comment
-
Thanks. Force-pushing is not a big problem, most of the time. I see myself doing that fairly often now that I work more intensely on these projects, primarily alanif/alan, of course. Moving original sources to assets is a good move. I agree on the folder name, and if you want my vote it would go to |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
@thoni56,
I've ported the ALAN Conversion Guide to AsciiDoc — sorry but I had to do some force pushing during the last updates, to clean up the history here and there, but the alpha man branch was rebased without conflicts.
I've taken liberty to fix some typos and polish a few sentences as I was porting and applying styles according to our guidelines, I hope you don't mind.
I've also left some
@TODO
,@FIXME
,@NOTE
, etc. comments with possible pending tasks and problematic text.I'd now like to move the original ODT and PDF files of the Conversion Guide in the
_assets-src/original-docs/
with all the other original upstream docs that were ported to ADoc.I have a question about the Conversion Guide folder and file names, which currently are:
conversion/
conversion/conversion.asciidoc
conversion/conversion.html
I think that having a
conversion/
folder can be misleading and confusing, newbies might thing it's part of the conversion toolchain. The file names of the documents are not quite revealing about the nature of the document either.What about changing
conversion
to something like:conv-guide
conversion-guide
alan2conversion
alan2conv
etc., i.e. something which is more indicative of what the document is all about? Any proposals are welcome, but let's not keep
conversion
.Beta Was this translation helpful? Give feedback.
All reactions