<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Thanks, I will check them.</p>
<p>Ideally it is an app that can run on or behind a http
server/proxy and serve html pages generated from the .md files
directly from the folder with the clone of the github repo. But
maybe I ask too much and adapting the wiki structure for a static
site generator from .md files is enough or even better.</p>
<p>Cheers,<br>
Daniel<br>
</p>
<div class="moz-cite-prefix">On 10.05.22 00:28, Seven Du wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAJs+-5rpP+RPJyUEzaG34=0n03Mz0Fhy8yVZvLOrundYaUxRgw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr">
<div>We'd like to help.</div>
<div><br>
</div>
<div>Select one from Jekyll, Hugo and TailwindBlog</div>
<div><br>
</div>
Jekyll: Ruby based <a href="https://jekyllrb.com/"
moz-do-not-send="true" class="moz-txt-link-freetext">https://jekyllrb.com/</a>,
can directly convert to html by github
<div>Hugo: Go based, can also auto covert to html <a
href="https://gohugo.io/hosting-and-deployment/hosting-on-github/"
moz-do-not-send="true" class="moz-txt-link-freetext">https://gohugo.io/hosting-and-deployment/hosting-on-github/</a> <br>
<div>TailwindBlog: Next.js based <a
href="https://github.com/timlrx/tailwind-nextjs-starter-blog"
moz-do-not-send="true" class="moz-txt-link-freetext">https://github.com/timlrx/tailwind-nextjs-starter-blog</a></div>
<div><br>
</div>
<div>We built a few websites with the TailwindBlog recently
and it looks very good. But as all JS projects, you have
to download a giant deps of node_modules and build locally
manually to generate static html pages, we haven't found
how to do it automatically, since our updates are not
frequent, we are ok to do it by hand.</div>
<div><br>
</div>
<div>There may be other options. Anyway, look and discuss,
as long as it's determined we can help to build.</div>
<div><br>
</div>
<div>As a reference, these are sites we just built recently:</div>
<div><br>
</div>
<div>- <a href="https://xswitch.cn/" moz-do-not-send="true"
class="moz-txt-link-freetext">https://xswitch.cn/</a></div>
<div>- <a href="http://rts.cn/" moz-do-not-send="true"
class="moz-txt-link-freetext">http://rts.cn/</a></div>
<div><br>
</div>
<div>
<div><br>
</div>
</div>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Mon, May 9, 2022 at 8:11
PM Daniel-Constantin Mierla <<a
href="mailto:miconda@gmail.com" moz-do-not-send="true"
class="moz-txt-link-freetext">miconda@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">Hello,<br>
<br>
it was discussed a couple of times during the past Kamailio
development<br>
meetings and several days ago the works started to convert
the Kamailio<br>
Wiki content to markdown format and host the files on
Kamailio<br>
<a href="http://github.com" rel="noreferrer" target="_blank"
moz-do-not-send="true">github.com</a> organisation.<br>
<br>
The Dokuwiki engine has served us very well during more than
a decade<br>
and a half, but open editing had to be disabled many years
ago due to<br>
bad actors pushing inappropriate content. The contributors
had to make a<br>
dedicated account on our portal only for Wiki editing. More
recently we<br>
had add another layer of protection requiring to grant
manually edit<br>
permissions to newly created wiki accounts because bots
started to work<br>
around CAPTCHA and other security extensions, posting again<br>
inappropriate content.<br>
<br>
All these added to operational overhead, but also made it
difficult for<br>
new people to contribute, specially for small editing to fix
typos or<br>
add usage examples.<br>
<br>
Thanks to Kenneth Stowe, who undertook the first big effort
of<br>
converting the Dowkuwiki files to markdown format, we are
now in the<br>
position of moving further with the plans of using github
for hosting<br>
the content of the wiki and enable easier contributions via
pull<br>
requests. The history of changes done via Dokuwiki show up
now as git<br>
commits.<br>
<br>
The github repository for the wiki content is available at:<br>
<br>
* <a href="https://github.com/kamailio/kamailio-wiki"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://github.com/kamailio/kamailio-wiki</a><br>
<br>
It is still work in progress, therefore we ask for the help
of community<br>
to speed up the conversion, among the tasks that need to be
done:<br>
<br>
* convert relative links between wiki pages – the
conversion tools<br>
used relative paths without file extensions, like:<br>
<br>
[Install Kamailio v4.4.x From GIT](/install/4.4.x/git)<br>
<br>
They have to be converted to relative path with .md
extension in order<br>
to be able to browse directly :n the <a
href="http://github.com" rel="noreferrer" target="_blank"
moz-do-not-send="true">github.com</a> portal — practically
the<br>
leading / has to be removed and .md added at the end, like:<br>
<br>
[Install Kamailio v4.4.x From GIT](install/4.4.x/git.md)<br>
<br>
* some section heading markers were not
detected/converted, onee may<br>
notice many equal signs (=) around a section name, it has to
be replaced<br>
with the appropriate markdown format based on hash signs
(#). For example:<br>
<br>
======= Install And Maintain Kamailio v4.4.x From GIT
=======<br>
<br>
Should be converted to:<br>
<br>
# Install And Maintain Kamailio v4.4.x From GIT<br>
<br>
* some Dokuwiki paragraphs used special formatting based
on plugins,<br>
for example the notes, warnings, … had special colors. The
common<br>
markdown format does not specify a syntax to color the text,
the propose<br>
solution is to use emoji at the start of the paragraph to
signal its<br>
special purpose. For example, the Dokuwiki content:<br>
<br>
<color blue>//IMPORTANT: Content for older releases
than 3.2.0 is<br>
available at the **Old Wiki Site**://</color><br>
<br>
Has to be transformed to:<br>
<br>
:fire:*IMPORTANT: Content for older releases than 3.2.0 is
available at<br>
the **Old Wiki Site**:*<br>
<br>
You are welcome to propose a better syntax for this kind of
transformation.<br>
<br>
* review config examples and evaluate what improvements
can be done<br>
(e.g., in terms of formatting and syntax highlighting)<br>
<br>
Any of these changes do not require any C programming
knowledge, nor<br>
much Kamailio config knowledge. Can be your first
contribution to the<br>
project and it will be very appreciated. It can also help
you learn more<br>
about Kamailio, because you may discover documentation that
you were not<br>
aware of.<br>
<br>
A very important decision is how to present the wiki
markdown content on<br>
<a href="http://kamailio.org" rel="noreferrer"
target="_blank" moz-do-not-send="true">kamailio.org</a>
website. Besides being able to see it on github repository,<br>
we want to process the markdown pages somehow and make them
available in<br>
html format on <a href="http://kamailio.org"
rel="noreferrer" target="_blank" moz-do-not-send="true">kamailio.org</a>
website for easier navigation and better<br>
indexing (e.g., with tables of content for large pages). If
you are<br>
aware of a suitable cli or web app that can convert markdown
to html and<br>
generate table of content, let us know.<br>
<br>
Any questions and suggestions should be addressed to<br>
<a href="mailto:sr-users@lists.kamailio.org" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">sr-users@lists.kamailio.org</a>
mailing list. Looking forward to your<br>
contributions on this community effort!<br>
<br>
Cheers,<br>
Daniel<br>
<br>
-- <br>
Daniel-Constantin Mierla -- <a href="http://www.asipto.com"
rel="noreferrer" target="_blank" moz-do-not-send="true">www.asipto.com</a><br>
<a href="http://www.twitter.com/miconda" rel="noreferrer"
target="_blank" moz-do-not-send="true">www.twitter.com/miconda</a>
-- <a href="http://www.linkedin.com/in/miconda"
rel="noreferrer" target="_blank" moz-do-not-send="true">www.linkedin.com/in/miconda</a><br>
Kamailio Advanced Training - Online<br>
* <a
href="https://www.asipto.com/sw/kamailio-advanced-training-online/"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://www.asipto.com/sw/kamailio-advanced-training-online/</a><br>
<br>
<br>
__________________________________________________________<br>
Kamailio - Users Mailing List - Non Commercial Discussions<br>
* <a href="mailto:sr-users@lists.kamailio.org"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">sr-users@lists.kamailio.org</a><br>
Important: keep the mailing list in the recipients, do not
reply only to the sender!<br>
Edit mailing list options or unsubscribe:<br>
* <a
href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br>
</blockquote>
</div>
<br clear="all">
<div><br>
<br>
</div>
</div>
</blockquote>
<pre class="moz-signature" cols="72">--
Daniel-Constantin Mierla -- <a class="moz-txt-link-abbreviated" href="http://www.asipto.com">www.asipto.com</a>
<a class="moz-txt-link-abbreviated" href="http://www.twitter.com/miconda">www.twitter.com/miconda</a> -- <a class="moz-txt-link-abbreviated" href="http://www.linkedin.com/in/miconda">www.linkedin.com/in/miconda</a>
Kamailio Advanced Training - Online: June 20-23, 2022
* <a class="moz-txt-link-freetext" href="https://www.asipto.com/sw/kamailio-advanced-training-online/">https://www.asipto.com/sw/kamailio-advanced-training-online/</a></pre>
</body>
</html>