Is it possible to re-use parts of documentation across different pages?
We have this feature to be implemented in the near future!
DeveloperHub.io: Create beautiful product documentation, hassle-free
61–70 of 70 posts
Re: DeveloperHub.io: Create beautiful product documentation, hassle-free
#62For the startup plan and using a custom domain, is it possible to enable https (let's encrypt)?
Hey again, this will be available this month! Keep an eye on us.
Re: DeveloperHub.io: Create beautiful product documentation, hassle-free
#63Earlier quoted context omitted.
I agree, this should have been HTML, not chasing the latest JavaScript fad. They managed to get links wrong. How on earth can you get something so easy and fundamental wrong!? I hold down command and click all the time to open in a new tab. They've got it opening in a new tab and following the link, so you can't stay in one place and open several tabs. This is something a beginner with an hour's experience of HTML ca…
Hey @JimDabell, We just launched the internal links feature yesterday in beta mode to test how the users use it! It is still not announced to the users. Your feedback is amazing and we will be looking to enhance it ;) Cheers, Z
And it's fixed now!
Re: DeveloperHub.io: Create beautiful product documentation, hassle-free
#64Seems cool. I'm browsing your own doc and found one thing i hate tho. Could you please please let user himself decide, if he wants to open next pages(your "Next to read") in new browser tab or in the same one? I hate how every second website doesn't respect this.
Hey @masa331, This is a feature that we just added yesterday as a beta, we will be iterating over according to your request ;) Look out for the changes in What's New ( https://docs.developerhub.io/v1.0/support-center/what-s-new ) Cheers, Z.
And it's now fixed!
Re: DeveloperHub.io: Create beautiful product documentation, hassle-free
#65I find that the best way to build docs is to use some sort of a static html generator and host the html yourself, which is not at all hard to do. There are free and open source themes available to host your own docs in various site generators. My personal favorite is hugo. Previously I have built a documentation for a large project [0] using hugo and it gave us 100% control over how we design or host it. Outsourcing…
@stockkid hey! This works great for small dev teams, but once you get technical writers around and the team gets bigger, static documentation just doesn't cut it and is unable to scale with the demand. Hugo is amazing, but this is the same thing with buying your own hardware and racks, or hosting with Amazon. It's all about the managed service and peace of mind! Thanks, Z
> once you get technical writers around and the team gets bigger, static documentation just doesn't cut it and is unable to scale
I feel that this is not convincing because docs for large software projects are also built using static site generators and git (e.g. docker).
In my case, we had many devs including a full-time technical writer contributing to the doc using Hugo and GitHub pull request and had no problems. I am curious what you think the bottlenecks of static documentation are.
Re: DeveloperHub.io: Create beautiful product documentation, hassle-free
#66Earlier quoted context omitted.
Hey @JimDabell, We just launched the internal links feature yesterday in beta mode to test how the users use it! It is still not announced to the users. Your feedback is amazing and we will be looking to enhance it ;) Cheers, Z
And it's fixed now!
Thanks, I can verify that's fixed. The larger point still stands though – testing this, it took 29.74s to load. DOMContentLoaded 19.79s / Load 21.13s. Your main.….js alone took 16.31s. A static HTML page would have taken a fraction of the time and it would be easier to get the basics right. Using an SPA for documentation seems completely wrong.
Re: DeveloperHub.io: Create beautiful product documentation, hassle-free
#67Earlier quoted context omitted.
And it's fixed now!
Thanks, I can verify that's fixed. The larger point still stands though – testing this, it took 29.74s to load. DOMContentLoaded 19.79s / Load 21.13s. Your main.….js alone took 16.31s. A static HTML page would have taken a fraction of the time and it would be easier to get the basics right. Using an SPA for documentation seems completely wrong.
Hey @JimDabell, can you tell me where are you based?
Re: DeveloperHub.io: Create beautiful product documentation, hassle-free
#68Earlier quoted context omitted.
Thanks, I can verify that's fixed. The larger point still stands though – testing this, it took 29.74s to load. DOMContentLoaded 19.79s / Load 21.13s. Your main.….js alone took 16.31s. A static HTML page would have taken a fraction of the time and it would be easier to get the basics right. Using an SPA for documentation seems completely wrong.
Hey @JimDabell, can you tell me where are you based?
From their profile: Based in Brighton & Hove, U.K.
Re: DeveloperHub.io: Create beautiful product documentation, hassle-free
#69SaaS-ifying your docs seems risky to me. Writing documentation is a big investment and startups tend to come and go ("it's been an incredible journey"). $39/mo is much more than what it costs to self-host Confluence, which for all its flaws at least leaves you in control of your data and is super extensible. Improve the data portability story and it'd be a lot more attractive. Additionally the actual docs and demo si…
Hey again,
A CDN and compression is now activated. We achieved 2.3x faster application and only 300ms difference between first meaningful paint in London and in Hong Kong. Can you please give it another try now ;)
Re: DeveloperHub.io: Create beautiful product documentation, hassle-free
#70Earlier quoted context omitted.
And it's fixed now!
Thanks, I can verify that's fixed. The larger point still stands though – testing this, it took 29.74s to load. DOMContentLoaded 19.79s / Load 21.13s. Your main.….js alone took 16.31s. A static HTML page would have taken a fraction of the time and it would be easier to get the basics right. Using an SPA for documentation seems completely wrong.
Hey again,
A CDN and compression is now activated. We achieved 2.3x faster application and only 300ms difference between first meaningful paint in London and in Hong Kong. Can you please give it another try now ;)