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

BOOK DISC #50

Open
7 of 21 tasks
HanslettTheDev opened this issue Aug 8, 2024 · 3 comments
Open
7 of 21 tasks

BOOK DISC #50

HanslettTheDev opened this issue Aug 8, 2024 · 3 comments

Comments

@HanslettTheDev
Copy link

Introduction

An Electronic book format that allows you to make content using a github repo

Description

Generally, most electronic formats that exist work offline. Example, pdfs, pub files, epub etc. All of this digital formats have something in common. Whenever there is a revised edition of the content, they will need to update everything again and republish. My theory is that there can exist an electronic format with a reader that allows you to ship content from the comfort of your code editor(yes particularly for devs) and just git push, and have your readers sync automatically with the recent changes. You might be asking to yourself this questions

Why make a program that auto updates meanwhile you can have a website that does that for you?

Well, with this approach, you have zero server cost, push ready content and the user just needs internet connection to view updated material. It works on demand. You could read chapter 1 today and have the chance to see chapter two when it's immediately released

Who is the target audience?

Developers particularly. But when you think about the idea for a moment, it can extend to almost every discipline in life.

How will it work?

There are two approaches I am leaning on

  1. write an electronic format that is compatible with most mobile devices and their readers. let's say we have a file named "learn django.dc". When the user opens this file on thier device, it can be opened in any pdf reader and can dynamically be updated whenever there is a change from the source.
  2. Create a whole mobile/desktop/command line app that is designed to read the electronic format and provide support for viewing things like realtime changes done in the *book/material/book disc, create bookmarks etc. It's just a regular reader but with a specific approach to how content is been delivered

Is this some revolutionary breakthrough?

Yes and No. The concept of specific electronic formats that can receive live updates exist. And it's quite used in many apps today. But this is really targeted for developers who might want to write their own books but don't want to follow a specific pattern, and just want to share their personal experience at the same time not having the idea of writing a book seem like a difficult process. Let's just say it's a way to change how we see delivering content

What about SEO?

The format should automatically be rendered easily in a browser and compatible with those who want to blog. If it needs to be posted on the internet, parsers should exist to make deployment to a blog.
Build your content on your website while building a book about your journey

How practical is this solution?

Make revisions to your blog post, book all from one git push
Take advantage of git version control system to store your content
Make use of other file type formats within the same electronic format
See realtime updates been done on a book and have others contribute to your content with little overhead

Are there Monetization opportunities from this?

Maybe

After reading the above message, I guess your thinking "Well, we are just using git and github to do shit". Well true, and that's why I feel the idea is unique because it already integrates with a tool developers are familiar with. Why do you need to use a book creating app or MS word to write your thoughts when we can leverage git and github to create an Electronic format/Reader that can take your thoughts and make it easier to distribute quality content.

I'm open for more questioning

Relevant Technology

Currently, this project will use GoLang
As for other details, still on the drawing board

Complexity

  • Beginner - This project requires no or little prior knowledge of the technolog(y|ies) specified to contribute to the project
  • Intermediate - The user should have some prior knowledge of the technolog(y|ies) to the point where they know how to use it, but not necessarily all the nooks and crannies of the technology
  • Advanced - The project requires the user to have a good understanding of all components of the project to contribute

Required time

  • Little work - A couple of days
  • Medium work - A week or two
  • Much work - The project will take more than a couple of weeks and serious planning is required

Categories

  • Mobile app
  • IoT
  • Web app
  • Frontend/UI
  • AI/ML
  • APIs/Backend
  • Voice Assistant
  • Developer Tooling
  • Extension/Plugin/Add-On
  • Design/UX
  • AR/VR
  • Bots
  • Security
  • Blockchain
  • Futuristic Tech/Something Unique
Copy link

github-actions bot commented Aug 8, 2024

It's great having you contribute to this project

Welcome to the community 🤓, we will carefully review your project idea and get back to you.

If you would like to follow our community's work you should join us on our Telegram chat group and Channel, we help and encourage each other to contribute to open source.
You can also support us financially here to help us build Cameroon one open source at a time.

@Sanix-Darker
Copy link
Member

So, let me resume, if am not wrong here, you want to create a specific offline format that can be sync whenever the content got updated.

Why not using html 🤷🏾‍♂️ that is actually supported by many readers on mobile/desktop/... Offline and Online, then in this case, mix that with GitHub pages ?

You have something always synced from master branch, so always updated and you don't need to create a new format that existing readers should handle ??? 🤔

And you have only two thing to do, ping a GitHub page and add cache 🤷🏾‍♂️ ?

@HanslettTheDev
Copy link
Author

That's a good idea
I guess the reason I was going in for a special format was to make everything customized and controlled. So there is more flexibiliy

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants