Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

new content structure #26

Closed
Tracked by #48
nweldev opened this issue Jul 19, 2022 · 3 comments
Closed
Tracked by #48

new content structure #26

nweldev opened this issue Jul 19, 2022 · 3 comments
Assignees
Labels
effort2: medium (days) priority: 0 (critical) Critical priority issue that must be resolved immediately type: doc Improvements or additions to documentation type: request Informal request for help or information
Milestone

Comments

@nweldev
Copy link

nweldev commented Jul 19, 2022

Request by @Vuk-BN for 2022-07-22: Deliver a thorough plan describing the new structure of the website while progressively moving toward the DevKit.

Define the new structure and create the associated sections.

@nweldev nweldev added type: doc Improvements or additions to documentation effort2: medium (days) type: request Informal request for help or information priority: 0 (critical) Critical priority issue that must be resolved immediately labels Jul 19, 2022
@nweldev nweldev added this to the Q3 2022 milestone Jul 19, 2022
@nweldev nweldev self-assigned this Jul 19, 2022
@nweldev nweldev moved this from Todo to In Progress in Technical Communications Jul 19, 2022
@nweldev
Copy link
Author

nweldev commented Jul 21, 2022

Working Draft

Warning

This working draft will be constantly updated while creating new content.

ℹ️ LEGEND

🔽 pre-existing content transfered as is
↗️ external link
♻️ simple translation / extension / update of pre-existing documents
🗜️ simple summary of pre-existing documents
🚧 should be first marked as "coming soon" as the associated part should be available around the end of Q3

Home Page (calls to action)

  • quick overview of the DevKit
    • with more incentives to start using/testing the DevKit
  • quick introduction to blindnet
  • Community / Contribute
  • Openness

Docs

Note

The first "overview" tutorial should be extended/replaced by a "modular" quick start tutorial as follow ASAP:

Deep Dive

Note

As a first step, some of these documents have been moved to the /docs section.

APIs

automatically generated dev/API docs

  • OpenApi ↗️ (stoplight)
  • Privacy Computation Engine
  • ♻️ Data Capture — (1) migration of the existing SDK docs (2) replace with new dev docs from repos
    • Java
    • Dotnet
    • Node.js
    • Frontend JS
  • Storage
  • WebKit (storybook) ↗️

Community

see #14

Openness ↗️

@nweldev
Copy link
Author

nweldev commented Sep 14, 2022

see #31 (comment) for update on week 36

The following follows a meeting between @Vuk-BN, @milstan and me on September 14th, and outdated this previous comment.

The main focus of blindnet.dev now needs to be on acquisition and activation, not retention.
Completing the introductory tutorial and detailed docs for PCE configuration and PC4W is now my top priority.

@nweldev
Copy link
Author

nweldev commented Sep 21, 2022

The new structure for the /docs is now in production.

#14 and other sections will be addressed with dedicated issues.

@nweldev nweldev closed this as completed Sep 21, 2022
Repository owner moved this from 🏗 In progress to ✅ Done in Technical Communications Sep 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort2: medium (days) priority: 0 (critical) Critical priority issue that must be resolved immediately type: doc Improvements or additions to documentation type: request Informal request for help or information
Projects
Status: Done
Development

No branches or pull requests

1 participant