docs
docs copied to clipboard
flarum
Flarum documentation.
We go over the components (input fields, streams, app.request), but we don't have an example that ties everything together. Could be really helpful.
To prevent any mixin collisions between extensions, we should recommend the use of Less namespaces, similar to how we handle initiali(s/z)ers in JS. https://lesscss.org/features/#mixins-feature-namespaces They're not _that_ tricky to understand,...
Advantages: - Visual online editor with real-time preview of translation results. - Integration with github to automatically update source documents and synchronize translation results. - Multiple branches (i.e. multiple versions)...
As proposed by @Kulga [here](https://github.com/flarum/flarum/commit/569e3a3b5ec862ecae93e0e438dd6a7a4c5012ed#commitcomment-21080215), we should probably change our included Apache configuration (and the one for Nginx in the docs) to only include the bare essentials - or at...
Vuepress supports automatically generating ToCs based on markdown headers. I see no reason not to add this at the top of every `extend` page: https://vuepressbook.com/tutorial/special.html#automatic-table-of-contents-generation
Some complex topics, like the API controller data flow or the policy system, could greatly benefit from diagrams/flowcharts.
We have this for apache and caddy; this would make it clear that the `include` statement should be positioned in a server block.
Even if it's as much as there previously was on the docs for beta 7, at least that'd be something which would include getting an API key and performing basic...
