Document export classess in hacking/customization page

[ssddanbrown]

https://github.com/BookStackApp/BookStack/blob/06b5a83d8f5105fceb5f44458df16a1643d7c890/resources/views/layouts/export.blade.php#L14

[dassudip2001]

@ssddanbrown how to fix this issue give me an idea

[ssddanbrown]

@dassudip2001 In my original link above I point to standardised class names we have for exports. This issue is to document these classes on our hacking/customization page.

If you're not sure about this, it may not be an issue to take on since it requires some understanding of how BookStack is applying these, which requires understanding of the BookStack source code.

[dassudip2001]

@ssddanbrown hacking/customization which section then i can cheange the documentation

and can I start BookStack?

[ssddanbrown]

@dassudip2001 It would be a new section to add.

[dassudip2001]

what I should change Some suggestions. and how to add a new section .and what is the new section name?

[ssddanbrown]

A new section can be added just but adding a new header in the markdown code content of that page.

I don't want to sound mean, and I know your intentions here are kind to contribute to the project, and I am happy to provide general pointers and guidance where needed, but if you don't understand what's being documented, and don't know what to write to make the changes, then it's probably not worth picking up these issues. At this point It's probably going to be quicker just to make the changes myself, rather than telling you what to write and where to write it.