DEV Community

loading...

Git-based CMS and privacy

patarapolw profile image Pacharapol Withayasakpunt ・1 min read

How do you usually manage it? Private git repo?

Also, what do you feel when people forked your GitHub Pages, for instance?

Discussion (4)

pic
Editor guide
Collapse
mattwaler profile image
Matt Waler

If the content is going to be generated into HTML and will be indexed for SEO, who cares if the repo is public?

Collapse
patarapolw profile image
Pacharapol Withayasakpunt Author

You made a point. Still, I don't want to think about being Fork'd. I don't want to make it too explicit.

Collapse
funivan profile image
Ivan

I made it private. Don't have any problems with this approach. The biggest disadvantage are typos, anyone who have GitHub account can fix the. But whit private repo you need to have 3d party apps to manage this. Just create a list of pros/cons for private repo and chose the most valuable for you ;)

Collapse
amorpheuz profile image
Yash Dave

Unless you don't want to allow the repository to be publicly available, forking is all right since a public repo can be cloned anyway and re-uploaded without proper consent. At least a fork will always point back to the original source!

Haven't had an occasion where someone forked my repo without a fix in mind. Licensing the repo appropriately should also help in clearly indicating that you are the author for the content and what's okay, what's not.

If your concern is keeping certain posts private such as drafts, I think keeping the repo private is the solution.