Localization

[Tychodewaard]

I did not find a comprehensive explanation about localizing content.
So, I created one on https://dnncommunity.org/blogs/Post/5144/DNN-and-content-localization

What is the best way to incorporate this in DNNDocs? Not just content but also the location. I did not find an obvious spot for this.

Is there by any chance a simple way to add this content? Or do I have to do the whole markup thing, clone the repo, create a PR etc etc?

[david-poindexter]

@Tychodewaard this is a great observation.

There are a few documents already in DNN Docs related to localization and they are as follows:

• https://docs.dnncommunity.org/content/tutorials/modules/beginning-module-development/considerations/index.html#localization
• https://docs.dnncommunity.org/content/tutorials/modules/mvc-modules/mvc-module-mvcviews/index.html#localization
• https://docs.dnncommunity.org/content/features/security-privacy/privacy/cookie-consent/index.html#localization
• https://docs.dnncommunity.org/content/tutorials/troubleshooting/ts-incomplete-content-localization/index.html#troubleshooting-incomplete-content-localization

That said, it seems content like you created in your blog post would be well suited under the current Features section (probably under Content Management). We are currently trying to figure out some ways to better organize content and/or generate new content and my goal is to try and finalize our IA direction over the coming weeks. Until then, I'd be happy to work with you to show you how to contribute to DNN Docs, or you can read up on the documentation for that. 😉

[Tychodewaard]

I have a lot more to contribute. Actually, there are two things that have been stopping me from contributing

1. is that I don't understand it.
   Whereever I click in the Getting started, it is empty
   
   Whereever I click in the Features section, the information is much less than expected.
   

Only the tutorials seem to have real content.
If I want to solve this by taking up the challenge and fill 'features' for instance, I get to the next point.

2. if there was a structure in place I would add content easily but creating a structure is more complicated that just adding text/images. That requires Github, pull requests etc.

If I am wrong about this, please add on https://docs.dnncommunity.org/content/getting-started/contribution/dnn-docs/how-to-submit-a-new-topic/index.html
(I really have been trying and not just some laze Dutch guy :-) )

[david-poindexter]

@Tychodewaard you have so many valid points here and I'd like to say I have all the answers, but let's just suffice it to say, it is all a "work in progress".

I will try to address a few key points though.

• We are working on solidifying the site information architecture as we move forward so it becomes much clearer where new/revised content should ultimately live. Many ideas have come and gone through the life of what we now know of as DNN Docs, but each attempt ran into bumps along the road to fruition. Thus, I along with a few others (happy to get your input as well) are trying to rethink what we NEED versus just trying to reorganize the mess of content we actually HAVE. This is no simple feat. Thanks for your patience and your input would be super much appreciated.
• Regardless of the future of the site information architecture, any contribution to the document will still require some level of GitHub knowledge. The basics are all covered in this current section of DNN Docs but this needs to be improved for sure. And as you have pointed out, there is one page in that section that is currently empty (there as a placeholder for someone to contribute).

Once we finalize the new site information architecture, I plan to vision-cast a bit better and to educate via other means/channels (including videos) as to how people can participate and contribute to the project.