The rollout schedule for the new Aptivi documentation is up!
#GitBook #Docs #TechNews #TechUpdates #Aptivi #dotnet #csharp #programming
The rollout schedule for the new Aptivi documentation is up!
#GitBook #Docs #TechNews #TechUpdates #Aptivi #dotnet #csharp #programming
Apple: Our philosophy is to provide software for our machines free (1976)
http://apple1.chez.com/Apple1project/Gallery/Gallery.htm
#ycombinator #Apple #Apple1 #Apple_1 #6502 #NMOS6502 #Microprocessor #Pom #Pom1 #Opcode_Matrix #Wozniak #monitor #bios #rom #computer #Ordinateur #Opcode #Instruction #Java #Applets #6502_Assembly #Emulation #Archive #Emulator #Histoire #History #Documentation #Doc #Docs
Here’s your sneak peek of the improved docs design!
As we’ve stated earlier in one of the last articles about the improved docs design plan, our plan was to make the documentation visually appealing to make the docs more gorgeous and more understandable to a wider audience.
Today, we have finally made the updated, improved documentation design available in the main Aptivi docs page! We have changed the design from simplistic to appealing design, and we’ve made the text less wordy to make the docs more understandable.
This is the current state now, versus the previous design:
We have used cards instead of bullet points with links to give you a comprehensive list of projects and other elements without introducing walls of text. Cover photos are also used to make those cards stand out, ensuring visual appearance. Links will also appear in the titles, if desired, along with a slightly bigger text due to space.
For step-by-step instructions and other listings, we have replaced the traditional bullet points and walls of text with elements like “steppers” and “expandables.” This is to ensure easier comprehension when following the steps while hiding secondary content under expandables. Restructuring the pages is also done to make sure that all key points are in one place instead of different points that point to the same section but scattered to multiple places.
The above image also shows a role of expandables when it comes to addressing different points when sections aren’t enough, such as code of conduct and contribution guidelines.
We are very excited to announce that we’ll start working on evaluating all documentations beginning today to redesign them according to the above principles!
However, all stable and rolling documentations that were branched before February 15th won’t be updated to preserve the history and to show users how we evolved from traditional but wordy docs to minimalistic and modern docs.
The rollout will start gradually on February 15th across projects, starting from the Nitrocid manual, until all documentation has been updated. This ensures that we maintain consistency while being able to update docs for new features and other changes at the same time.
Until then, check out our brand new main docs design!
Take a look!#docs #documentation #gitbook #news #Tech #Technology #update
You can now see how will our GitBook documentation look like!
#GitBook #Website #TechNews #TechUpdates #Documentation #Docs #Aptivi #Branding #WebDesign
https://officialaptivi.wordpress.com/2026/02/01/heres-your-sneak-peek-of-the-improved-docs-design/
Vivement la nouvelle version de @lasuite #Docs, en 4.5.0 qui permet d'importer des .docx très facilement si j'en crois la vidéo : https://github.com/suitenumerique/docs/releases/tag/v4.5.0
Next.js 평가에서 AGENTS.md에 압축된 8KB 문서 인덱스를 넣은 방식이 스킬 기반 접근보다 우수했습니다. AGENTS.md는 빌드/린트/테스트에서 100% 통과, 스킬은 명시 지시 시 79%, 기본은 53%였습니다. 이유: 조회 결정 지점 제거·항상 사용 가능·순서 문제 없음. .next-docs 다운로드·인덱스 주입은 npx @next/codemod@canary agents-md로 자동화됩니다. 권장: 문서 인덱스는 압축해 AGENTS.md에 포함하고 스킬은 특정 작업용으로 보완 사용하세요.
https://vercel.com/blog/agents-md-outperforms-skills-in-our-agent-evals
Our docs look a bit boring, but we'll work on it to make them more gorgeous!
#GitBook #Docs #csharp #dotnet #programming #TechNews #TechUpdates
https://officialaptivi.wordpress.com/2026/01/29/improvements-planned-for-project-and-other-docs/
Improvements planned for project and other docs
Documentation is always the most important part of any project and other technology-related topics. This tells users what the project is, how it functions, and how can users use it, and every good project includes documentation.
However, we think that there is room for improvements across the entire Aptivi project documentation workspace, such as Nitrocid, Terminaux, and so on, so we have decided to make a plan for refinements to happen in all project documentations.
Those improvements will make users and developers be able to more comprehensively understand what they’re reading, while providing improved design at the same time. We’ll use more items and elements that are related to layout to make the documentation look much more welcoming.
To save resources, those changes will only land to all rolling manuals. This means that there will be no design updates for both stable and deprecated project docs that were made before March 1st.
The incremental rollout of the new documentation design will start from February 15th. You’ll be able to have a sneak peek of the new design in the main Aptivi GitBook docs page starting February 1st.
#docs #documentation #gitbook #news #Tech #Technology #update
Scheinbar verwendet #docs niemand? 😴
I will add back in ones that aren't there right now that maybe had been used before. Let me know if you want something.
#Democracy #Docs
#BlueCrew
#Resister
#MissKitty DEMOCRACY Docs - Go...
Writing is often the smallest part of a tech writer's day. Consider our work as a kind of super QA team and alpha tester that goes beyond making sure the software works as the ticket describes, for example.
Read more:
🔧 Đánh giá tài liệu Markdown do AI viết? Công cụ mới mdschema (Go CLI, MIT) giúp ràng buộc cấu trúc: bắt buộc tiêu đề, khối code, bảng, liên kết, frontmatter… Tạo template, suy ra schema từ file có sẵn, hỗ trợ CI, đa nền tảng. Thử ngay! #AI #Markdown #OpenSource #Docs #CôngCụ #AIđánhgiá #OpenSourceVN
https://www.reddit.com/r/opensource/comments/1qpaefh/guardrails_for_aiwritten_markdown_docs_enforce/
Announcing godoc-static v1.0.0: Distribute Go documentation as static HTML.
https://codeberg.org/tslocum/godoc-static
godoc-static starts a local instance of godoc and scrapes it to generate static documentation for one or more Go packages. A demo of godoc-static's output is available at https://docs.rocket9labs.com
#foss #freesoftware #opensource #godoc #documentation #docs #html #software #tech #golang #technology #free #linux #freebsd #release #announcement
Kennt jemand eine Instanz von "Docs" mit der man das editieren von Text ausprobieren kann?
Does anyone know an instance of the “Docs” suite where I can try editing text?
「Docs」スイートでテキスト編集を試すことができる事例ページをご存知の方はいらっしゃいますでしょうか?
https://github.com/suitenumerique/docs
#docs #Collaborative #Text #Editing
Docs SaaS của bạn đang thất bại trong bài kiểm tra GPT? 6 bước AIO: 1️⃣ AI summary ở đầu; 2️⃣ Định nghĩa thuật ngữ; 3️⃣ “Tại sao quan trọng”; 4️⃣ Đồng nhất tên tính năng; 5️⃣ Tóm tắt mỗi chương; 6️⃣ Liệt kê lỗi thường gặp. Viết cho bot AI, không chỉ Google. #SaaS #AI #Docs #Marketing #AIOptimization #TốiƯuHóaAI
https://www.reddit.com/r/SaaS/comments/1ql1nge/why_your_saas_docs_are_failing_the_gpt_test_and/
Sometimes I just cook so hard I have to write #docs for my code so others can admire my genius too.
Reviving old Nitrocid Documentation
While we are gathering information about how we plan to finalize the documentation for the upcoming Nitrocid release, we’ve discovered an interesting way to revive the old Nitrocid documentation. Before we get into details into how we did it, here’s some background information about the original Nitrocid documentation.
When version 0.0.6 was still in development, we did it as part of the executable using embedded resources. You can see the resultant “manual page” files here, before the migration to GitHub Wiki started at around 2019 before the release of 0.0.8. The documentation then stayed on GitHub Wiki until 2022, when we had planned to move the docs to DocFX during the development of 0.0.23.x.
However, during development of 0.0.24.x, we’ve discovered that the documentation needed a rework, and that libraries at the time had no documentation. The only documentation that was provided at the time was the API docs, and that, in our opinion, wasn’t enough, because the API docs don’t usually provide detailed information about the functionality of the library.
So, when 2023 started, we’ve begun a project that focuses on a complete rewrite of the Nitrocid documentation, which was part of our plan of the Nitrocid 0.1.0 release. During the beta release, we’ve brought the GitBook documentation online. That was after careful choosing of the documentation frameworks: whether to continue using DocFX or to switch to another doc framework (GitBook, Read The Docs, etc.) was our question.
Modernity of our docs and simplification of our workflow was our requirements, and GitBook has been carefully chosen after considering its capabilities. The current GitBook documentation can be found here. This migration has caused us to shut down the Wiki section in our GitHub as we were telling people that the migration was done.
Fast forward to today, as we no longer have backups of the old wiki for versions 0.0.23.x and older, we’ve decided to run a Git clone on the Wiki repository of Nitrocid to check to see if we can fetch them. Here’s the command:
$ git clone https://github.com/Aptivi/Nitrocid.wiki.git Instead of getting an error or getting an empty repository, we got a full history of the wiki that was active from 2019 to 2022. This gave us a brand new project to do during the “Final Touches” stage of 0.2.0 as part of the documentation preservation project under the Archived Manuals GitHub organization, making February 12th the biggest milestone yet.
We will study the structure of the commits and release archived documentation under GitBook when each version is discovered. This release is going to be asynchronous to the 0.2.0 release plan.
We have learned that when you disable the Wiki on GitHub, the repository that contains the wiki itself won’t be deleted. For example, deactivating Nitrocid’s Wiki section on GitHub won’t remove the Nitrocid.wiki.git repository. Therefore, this is done on purpose to make restoration easier, in case you ever want to turn the Wiki section back on.
To clone the wiki repository when the Wiki section is disabled, just run this command:
$ git clone https://github.com/<owner>/<repo>.wiki.git You can interact with it just like any other Git repository.
#docs #documentation #gitbook #KernelSimulator #KS #NKS #news #nitrocid #NitrocidKS #Tech #Technology #update