I have asked for feedback and I got little. I do not think that many open points were left that could have easily been implemented. This is why I wasn’t too happy to read this email now, because I would have preferred some constructive ideas and help over this now.
You are a tough person to send feedback to. You have a tendency to react in off-putting ways. Re-read your response.
You did receive my constructive ideas in the Documentation list.
First of all: There is no time to work on this. I have been doing nothing else but infrastructure and admin work around the project for the last four weeks. I am barely able to respond to my email. One emergency after the other is happening and I am doing “quick and dirty” on more things than I would like to. Bare this in mind. This is also the reason why I am a bit on the edge.
How can I help?
Since I’m not a firewall expert, I help with documentation (I started working on the old wiki near April 2018)
False information is worse than none.
Sorry to say but you’ll have to point those out (I know you are busy!). I’m not an expert but I have been going through and correcting what I can. I don’t have the skills to identify false info.
Did the https://github.com/benweet/stackedit.js not work?
This project hasn’t been updated in years. I am not going to integrate legacy software into something new.
Sorry for dwelling on this (and I’m not trying to make you mad): To my unskilled eyes it looks like it was updated in Aug 2018. I saw your concern about PageDown but there is not a Pagedown reference in the JS code. On the webpage it states "stackedit.js is lightweight and has no dependency.” (I wrote a note to the developer to confirm). I am missing something obvious...
I am also quite frustrated about seeing loads of HTML .... This is not how this was intended and we have talked about why this is a bad idea.
What should I correct? The HTML I remember is:
<color blue> Example </color> to <span style=“color:blue”> Example </span>
I believe I wrote to you asking for guidance and did not receive a response.
Keep in mind, pages that look like this —> https://wiki.ipfire.org/hardware/arm?revision=2019-08-06T13:57:34.868460
Will now look like this —> https://wiki.ipfire.org/hardware/arm?revision=2019-01-09T19:34:43
—
I’m sure you realize this is an uphill battle. Especially since users are allowed/encouraged to update wiki pages. Without the code to limit or exclude HTML you’ll become the wiki cop and continue to be frustrated by non-compliance. This doesn’t seem worth your time.
I am also quite frustrated about ... only the word “update” in the change log.
Look at the revisions for a single page. You see many proper remarks. The “Update” is normally a quick change where I got frustrated fighting the interface to get a page completed. My bad. I will do better.
Again, none of this is meant to be mean. It just my feedback.