π‘ When an idea strikes, the very next thing to do is buy a domain π
I do this a lot and started to slow down recently.
You take a shower and th...
For further actions, you may consider blocking this person and/or reporting abuse
Found this post by @madza about using sub domains. That's probably the best way to do it.
ie, start working subdomain in your main domain and then move to a separate if/when it demands
dev.to/madza/do-you-use-subdomains...
I bought a general purpose domain for this reason recently.
Smaller projects can just use a free subdomain on that one now.
nice trick! may I know the domain name?
Sure. It's bytebox.dev
Went for something generic and techy
You are not alone at buying domain names prematurely.
The answer to that trap is that we need to develop planning skills.
I found this article from @siddharthshyniben very helpful
A guide to planning a programming project.
Siddharth γ» May 22 γ» 6 min read
Just notied @siddharthshyniben is from same town as I am!
Really?
Yup, Kannur!
Good read, saved π
I put everything on subdomains.
People find my content via search, then bookmark it.
Which domain it's on doesn't matter.
I do have 4 top level domains, to provide a level of separation.
This is right way to go I think. Is it always on the subdomain or later moved to a separate one?
I should also write more to get results from SEO π I don't get much traffic from there like you do.
I keep websites on subdomains, so that I never pay for increasing number of domain renewals.
Unfortunately, for me, I build the project but I still can't buy a domain name as I can't afford it (as I am a high school student) I rely on free hosting subdomains like netlify, heroku, vercel, etc.. As I recently published my open source project software environment concepts project on free vercel subdomain =>
softwareconcepts.vercel.app
Static Site Generated Progressive Web App Glossary eBook for software concepts.
Software Environment Concepts
Understand Software ConceptsAbout
If you are new to software engineering or you are working in a software company (Manager, HR, Product Manager, etc..) and you want to understand what the engineers are talking about and lead them or you are Busines man/woman and you want to build a software product but you don't have experience in the field of software engineering then you should read this book. This eBook is like a glossary for software expressions or concepts where you can carry everywhere offline and online.
Software Environment Concepts App was built using:
Contributions
Software Environment Concepts is open to contributions, but first go to the discusions and let me know what you are working on first that way we don't overwrite each other.
What can you do to help:
Reporting an issue or a misleading concept
Fix an issue or a misleadingβ¦
That's a great way to start and build projects
Side projects means creating project in Heroku or AWS free tier. And creating a repo in Github of course. Domain name can come later.