I often use my side projects for experimenting with concepts and one area of interest is onboarding. Too often there are major hurdles and complexities in getting started contributing or developing web projects.
With Cuttlefish the goal is to be as approachable as possible and be productive after running a single command.
So I’m happy to say today I landed a few PRs in the main branch that add zero configuration project tooling in the guest when using vagrant🎉
Dependency management, linting, pre commit hooks etc are all ready to go after a vagrant up. I’m pretty chuffed.
It’s optional so you can still bring your own tooling and use the built in PHP webserver.
Hopefully that should make it easy to get up and running and contribute.
Cuttlefish is my hackable web/blog framework. I’m doing most of the hacking and eventually you might blog.
Rubber ducking a bit. Working on the coupling of the controller name being linked to the content structure. For example /posts/x loads the post controller with the post model and content from content/post/x.md.
It felt intuitive but I’m not happy deriving a path literally from a class name. In Particular the post archive is an archive controller with a post model. Also feeds/post vs feeds/auctions or something.
Originally I went with contentpath being based on a controller name property. But because the model already specifies the fields available in the content that didn’t seem right
So doing some work around each model having a content path property but not 100% if that’s the right relation.
Feels like It’s doing two things. Routing and content types.
For instance if I want a /blog I’d probably create a blog controller with a post model with records loaded from content/blog.
Looks like the controller is registered to a path via the router and it dictates the content path after all.
As a web professional and a person who isn’t a native speaker but values privacy, it’s disheartening to see catering websites offering the choice between a phone call and a facebook message.
Also, it’s a business risk if your income is dependent on using a third-party community for essential business operations.
This used to be common knowledge in “web design” but it’s still true. Every time a site interrupts the visitor from achieving something on your site, (modal, sso login, login prompt, newsletter signup) the visitor loses focus and is less likely to meet the goal (or “lowers conversion tracking” if you’re using analytics). That’s why these things should be displayed after the main content when the visitor is naturally open for a new pathway.
So shell login can be slow if you installed node versions using nvm and used nvm to set a default interpreter. The solution that helped me was to unset the default node but that means that there’s no node executable unless you manually first run
nvm use node or setup .nvmrc in projects… If limited to the former solution, that means PHPStorm might complain node is missing.
I had success installing node from nodesource as the “system node” fallback. weird flex but ok. Some node is better than the right node.
Where do I go to figure out if a pc component is compatible with a version of Ubuntu?
So PHPStorm couldn’t find my node and vagrant executables… until I changed the
source command in my
.zshrc to point to a file instead of a symlink to the file. Which is weird, as it worked correctly for login and interactive shells before the change. Puzzled.
Was going to work on repoman (https://github.com/svandragt/repoman) for a bit today but it’s working well as it is.
It’s interesting to hear the arguments against digital vaccine passports and discrimination and then map them to proving settled status for EU nationals.