Epub, PDF, MOBI, RTF, what else do you need?

As a self-titled “senior consultant” for Markdown programmers, I write a lot of code, write a lot of articles (I have 600+ on my blog phodal.com), and write a lot of ebooks.

The article summarized the problems I encountered in the work, recorded the pit I climbed, and some stories of growing up.

An e-book summarizes the knowledge I need in a certain field.

In the past, WITH these ebooks, I used to just upload HTML to GitHub. Recently when I was playing Serverless, I wanted to use the power of Serverless to provide offline version of e-books, supporting PDF, EPUB, MOBI, RTF formats.

GitHub’s Hitchhiker’s Guide

This ebook is a compilation of my experiences using GitHub, how I can improve myself, and some thoughts on open source software in the process.

Git basics and GitHub usage, Git submission information and several different specifications, how to improve the quality of GitHub project code, how to promote GitHub project, how to read open source software code in the “right posture”, and two years of experience on GitHub.

Target audience: Readers interested in exploring GitHub.

Ideabook: A hands-on project set for full-stack growth engineers

As a programmer which can not have Idea, have Idea to do.

Are you struggling to improve your programming skills?

Are you having trouble finding the right training program?

Are you frustrated that you have the right program, but no guide?

With the Ideabook, you have a series of hands-on projects.

My Idea is constantly growing, some ideas have Cool, but these ideas do not have a good actual combat guide. The goal of this ebook is to provide practical guidance for these ideas and build them step by step.

Target audience: programmers with programming experience, but suffering from no good Idea

Growth: Guide for full-stack Growth engineers

An ebook based on the seven steps of Web development described in Introduction to Repractise: Seven Days of Web Development.

This is a how-to book – don’t expect to learn everything from this book, but it will help you build your knowledge.

This is what other technical books lack. It can tell you what you can learn and then what to read.

For some people, it becomes the full stack because: small and medium-sized companies from different parts of the society, it is difficult to survive only on the knowledge of one field. For others, it becomes the full stack because: there is too much fun in the world, it is too pity to hang on a tree. For some people, it’s full stack because they want to start a business.

There are a lot of misconceptions about the full stack — that it should be able to do everything and master everything. Full stack just because we know the system as a whole, not because we know the system as a whole. Because experts are only skilled in one area, an architect is needed to understand the system.

Target audience: Experienced programmers interested in becoming and beyond full stack engineers.

Full stack Growth Engineer’s Guide

This book is the Python(Django) hands-on version of the Full-stack Growth Engineer’s Guide.

You will learn: how to develop a Web application (blog), how to write unit tests, how to write functional tests, automate UI tests, build continuous integration, add SEO support, support APP usage, develop apps, add a front end to a single page application, automate deployment, and how to make small submissions.

Target audience: Novice programmers interested in becoming and surpassing full-stack engineers.

I’m a front-end engineer by profession

This book summarizes some of the things that front-end engineers need to know.

For example: how to choose the right front-end language, six debugging skills you must know, eight things you should know about front-end separation, SEO optimization techniques, the art of client-side storage and modeling, the core knowledge of single-page applications, how to develop a front-end application from scratch, and more.

Target audience: Engineers who want to become better front-end engineers.

RePractise

The ebook was originally intended to come before Growth, but the book was a bit too difficult to write, so it was shelved.

No matter what kind of Coding, it is continuous Practise. To be successful, you need to RePractise — summarize and diff change and Practise.

As far as engineering is concerned, a skill is constantly practiced.

Different people have different approaches to practice. Some exercises are unnecessary and do not increase our skill points. Some exercises cut 10,000 hours in half or less.

Target audience: developers who have some Web development experience and don’t have a good direction.

Just follow the public account (phodal-weixin) and reply “book” or “ebook” to get the download address.