turn apertus.org logo into link to www.apertus.org ?

It'll do for the first month.

Point of note: Blackmagic Design's Duplicator 4K is an SD card duplicator with built in realtime H.264 and H.265 encoding, yet Blackmagic Design DaVinci Resolve doesn't support H.265

OpenEMM is an Open Source web-based enterprise application for e-mail and marketing automation.

for https://www.apertus.org/sites/default/files/styles/large/public/image/image.1495404558-phpcy4mSm.jpeg we need to find some way to give proper context as the activity is not directly camera related. Context could be: maker faire, soldering workshop, education, electronics building

Almost perfect!

https://www.apertus.org/axiom-beta from 4.5 MB to 2.3MB -> great!

Looks helpful indeed.
Anyone up for writing a small mediawiki extension?

And this one is more to the point maybe: https://www.mediawiki.org/wiki/Manual:Tag_extensions/Example

Maybe like examples from this page: https://www.mediawiki.org/wiki/Manual:Tag_extensions

I looked into that already and it doesn't seem trivial to do with mediawiki, but maybe I searched for the wrong thing. Please check.

Or we can add just a simple script/plugin which looks for some special marker and replaces the HTML code for the section. Like $ for bash commands.

good question, will need research.

can we make this behaviour default for the nowiki snippets?

This is indeed a problem we discovered when switching from the old wiki to the most current build.

Added the test code from sandbox, please check if it's better suited.

another example: https://wiki.apertus.org/index.php/Beta_Power_Board#Calibrating-Voltages
I think, that <nowiki></nowiki> should preserve newlines

I think that having a single point of information is quite valuable. I like the idea of having the code/the design files in the same file tree as the docs, but having the WIki as the only central point is fine for me, too.

Not sure, but just to update this for now and for anyone who's picking this progress up - The intention was to use LaTeX as a central point and update other platforms from there, however, this would be bad. Best bet is to use Wiki as a start point and do periodic updates of a LaTeX doc (or another solution) from that.

I'll leave that till you see Sebastian, in case you have something in mind, and I can't remember how it was, but it looks to me like this should be bulletted as opposed to a code block.

Maybe readthedocs would be a better tool choice, because it can create beautiful PDFs, but it can also be viewed and searched online. Moreover, it has a lower entry barrier for contributes. What do you think?

Yeah. Maybe a laptop to the right (If it's new). No stickers because we overdo that. Analyzer to the left maybe.

Great example of overhead. Cam would wanna be where the laptop is here.

Great example of overhead. Cam would wanna be where the laptop is here.

all errors fixed, two warnings remaining that can safely be ignored.

Some new requirements added.

done

Please remove the prototype page, as i'm at work right now and can't do it without my credentials.

well done everyone, looks very nice!

Added to main page.

Adjusted like requested.

beautiful work with the DIVs and CSS!!!

Just a small thing: Header 5 should possibly be a bit bigger or bolder than normal text. But all in all we can close this task, if current adjustments are sufficient.

One or two loose ends on Dimensions here - https://wiki.apertus.org/index.php/AXIOM_Beta/Camera_Structure#Dimensions

wiki restructuring mostly completed and a bit still in progress

In the other hand apert.us is also not delegated at the moment :)

If anyone is landing on this task it would be a good idea to speak with one of us as a lot of mocks have been done and structure, whilst nothing is necessarily final, has moved on a lot since the pictures in the OP were posted.

I have used YOURLS in the past. It works... and is easy to setup.

But they also do open hardware, it's another branch.

Unlikely that 'open source' would be dropped as it constitutes the entire basis of the project and its ethos.

I also like "cinema" is special. In the future, a marketing campaign can be linked to other products.

We may have found the solution there.

There is the option of just using 'open source' of course:

In T817#12239, @RexOr wrote:

Welcome Alex.

Welcome Alex.

open source systems, but, as Cinema refers to cinema. Source refers to software. Other alternatives...

Any more feedback on this issue please?

I prefer Open Source Design and Open Source Cinema out of the seven names.