Server: Get own documentation up and running

Created on 11 Jun 2016  Β·  17Comments  Β·  Source: nextcloud/server

2. developing bug help wanted high

Most helpful comment

Like that: https://github.com/nextcloud/documentation πŸ˜‰ ...If yes, i will start with rebranding.
Screenshots repository is already up (but not forked!), and we only need to fill it with new screenshots :)

All 17 comments

Should we simply fork owncloud/documentation?

Yes. But also the screenshots needs to be updated as well as "ownCloud" replaced through "Nextcloud" in the user-facing text. Additionally remove all Enterprise Apps documentation parts.

Any help utmostly welcome on that one… Otherwise we likely won't have any documentation in our 9.0 release and only for 10.0 πŸ™ˆ

And if you fork please just pull the whole repository locally and then create a new repo on GitHub and push all branches. :-)

Like that: https://github.com/nextcloud/documentation πŸ˜‰ ...If yes, i will start with rebranding.
Screenshots repository is already up (but not forked!), and we only need to fill it with new screenshots :)

Like that: https://github.com/nextcloud/documentation πŸ˜‰ ...If yes, i will start with rebranding.
Screenshots repository is already up (but not forked!), and we only need to fill it with new screenshots :)

πŸš€ ⭐ ❀️ πŸŽ‰ - Awesome stuff! If you could go over the stable9 repo this would be super awesome. We might even have proper documentation then for the 9 release πŸŽ‰

How to handle the parts where ownCloud 8 is mentioned?

  • Remove
  • Call it ownCloud
  • Call it Nextcloud (which would be strange for 8.2 😜)#

Which version numbers should i use?

  • 9 instead of 9.0
  • 10 instead of 9.1

Old branches

Should we remove stable7, stable8, ... (because they are simply not existing πŸ˜‰)

Documentation of Enterprise-stuff

Should we completely remove it, or should we leave it in, because we rewrite these features?

Master or stable9

Should we not first rework the master-branch, and then backport everything into stable9

cc @LukasReschke

Let me know if help is needed, i have no problem helping, but two persons working on the same thing is a waste of time :)

On my mobile atm, so please excuse my short response :)

Parts where oC 8 is mentioned

Remove.

Version numbers

9 instead of 9.x and master will be 10

Old branches

Kill it with :fire:

Enterprise stuff

Remove. The rewrites have the same functionality but another (better, see for example files_drop) user interface. Not having them closed allows us to integrate the stuff way better.

Master or stable9

At the moment we are aiming for getting a Nc 9 out very soon, likely next week already. Master is still 2-3 months away, so in my opinion we should first work on Nc 9 docs as that is what users will see.

@karlitschek Seems like we might even get some decent documentation earlier than expected then πŸ˜„

Any chance you can configure docs.nextcloud.org or so to point to .138? :-)

done :-)

Should it not be "doc.nextcloud.com" ... already changed to that everywhere 😭 @karlitschek

...i've also changed URLs to 9 instead of 9.0:

https://doc.owncloud.org/server/9.0/user_manual/userpreferences.html to
https://doc.nextcloud.com/server/9/user_manual_userpreferences.html

UPDATE: The user manual is finished now πŸ’ͺ Please review, before I go on πŸ˜‰

cc @MorrisJobke @LukasReschke

Yes. it should. Because of a super stupid limitation of the current dns provider i can't do that. Let me think about an option

ok. i looked again for options and there is unfortunately nothing we can do for now. In about one month we move to a different provider which removed this limitation. Unfortunately we can't do before that.

Then ... We wait :wink: ... And we stay at the adresses i've mentioned above.
Please Review the user_manual :wink:

Documentation related stuff should be handled in https://github.com/nextcloud/documentation/ -> closing this here

Thanks a lot @mar1u5

Was this page helpful?
0 / 5 - 0 ratings