pharos_master

テクノロジー・科学

[pharos_master @PharosMaster]

どこにできるのか楽しみです
https://t.co/rE3QUJD0TZ

[ケータイ Watch @ktai_watch]

横浜にApple Store誕生へ https://t.co/sKSkrjOgeV

[pharos_master @PharosMaster]

BSの通販番組みたいなやり取り…

[Hide.Ishikawa@WordPress テーマ Lightning / X-T9 開発 @kurudrive]

@Koots2021 ありがとうございます！！

[瀬尾 @seoryco]

本体バージョンをダウングレードできる「WP Downgrade」は 7.0 でも動作しました。

（最終更新が 3 年前なので推奨とは言えないですけど…）

[pharos_master @PharosMaster]

WordPressがAIと親和性が高い理由の一つは、フィルターとフックによってコア本体を変更せずに外部と連携しやすいことがあるそうな…。

[The Repository @therepositorywp]

WordPress wasn't built for AI, or was it?

In this opinion piece, @miriamschwab makes the case that two decades of open infrastructure, hooks, and 60,000+ plugins have positioned #WordPress perfectly for the AI era.

https://t.co/z863RNAcRW

#sponsoredpost

[pharos_master @PharosMaster]

この投稿とまったく同意見。たとえ1ページのLPでも標準的なブロックで構成されたWordPressで作りたい。将来的なカスタマイズが容易でスケーラビリティが担保され、一定の知識がある人なら引き継ぎが可能な「Webサイト」を作りたいから。

[Nat Miletic @natmiletic]

"I built a site in 2 hours with AI" posts are missing the point entirely.

Nobody's arguing AI can't generate a website. It can. The question is what happens on day 31.

Your developer is busy. Your marketing manager wants to update the homepage hero. Your content team has three blog posts ready to go.

Who's touching the site?

If the answer is "we have to wait for a developer" that's not a website problem. That's a business problem that isn't solved by AI.

This is exactly why WordPress still powers 43% of the internet, not because it's trendy, but because it works for real teams over the long haul.

A few things AI-generated sites quietly can't do:

Look like you.
Vibe-coded sites and no-code tools recycle the same layouts. Your competitors are launching the same "site" with different colors. Custom WordPress builds don't have that problem.

Hand off cleanly.
Any developer on the planet can open a WordPress project and know exactly what they're looking at. Try that with someone else's AI-generated codebase.

Let non-devs take the wheel. WordPress was built around the idea that content people — not engineers — run websites. That's still true.

Scale without starting over.
E-commerce, memberships, multilingual, complex integrations — there's a plugin or a pattern for it. You're not rebuilding from scratch every time requirements change.

Keep you in control.
Your data, your hosting, your codebase. No platform deciding to change pricing or deprecate a feature you depend on.

Speed to launch is a metric. It's just not the most important one.

The sites that win long-term are the ones people can actually maintain, update, and grow — without the whole thing becoming someone's full-time job.

[pharos_master @PharosMaster]

ブロックテーマのチートシート。コアのブロック、パターンとテンプレート、theme.jsonリファレンス、作者が使っているアクションやフィルター、「トラブルシューティング」タブ。

[WPNEWS.io @wpnewsio]

Enhance your WordPress skills with the Block Theme Cheat Sheet. Find everything you need for[…][...]

#WordPress #Uncategorized
https://t.co/KlluIorDge

[Brandon K. Hill | CEO of btrax 🇺🇸x🇯🇵/2 @BrandonKHill]

中国が運営する偽の日本ローカル新聞のフリをした中国が運営するサイトが15件も見つかった。

「富士山タイムズ」「仙台新聞」「福岡エクスプレス」などなど、全部中国から。現在2年以上稼働中。本当に怖いのは目的。今の読者を騙すことではなく、Google検索とAIの学習データを汚染すること。数年後にAIに「日本」について聞いたら、北京が書いた偽記事から回答が生成される。

カナダのCitizen Labが2024年に暴露。日本政府は知ってた。でも何も対応をしていない模様。AI時代の情報戦は始まってるのに、防衛手段があんまない。

情報元: https://t.co/YoVVh1bEOE

[内閣官房 @Naikakukanbo]

4月24日、総務省・デジタル庁と共同で「Japan Dashboard｜地方財政（市町村ごと）」を公開しました。市町村ごとの財政状況が手軽に把握できるだけでなく、時系列比較や自治体間での比較も簡単に行えます。また、地図を用いて視覚的に把握することも可能ですので、ぜひご利用ください。

[ハヤシシュンスケ｜合同会社みやび @The_AGI_WAY]

設立したばかりのうちの会社に、毎日のように営業電話がかかってくる。「ホームページ拝見しました」「AIO対策しませんか？」ある日、最後まで全部聞いてみた。そしたら出てきたのが、教科書に載せたいレベルの"刈り取り装置"だった。解体記録、置いておく。👇

[pharos_master @PharosMaster]

@ddryo_loos 自分にとって使いやすくて気に入ったものを使えば良さそうだけど、「正解」にこだわる人ほどみんなが他のものを使うのが我慢できなくなるみたいですね。

[pharos_master @PharosMaster]

CMSユーザーが保守的だから？それとも世間はCMSにそれほどこだわっていないから？

[了@LOOS, Inc. @ddryo_loos]

あんなに盛り上がっていたEmDashですらタイムラインにはもう出てこない…

[pharos_master @PharosMaster]

メールで届いたQRコードをA4の紙に印刷していかないと20分待っても半分しか進まない行列に並ばされるテック系イベントの入場システム。従順で鈍感な日本人は自分たちがどれほど時代遅れか認識できない。

[Peter Deans @deans_risk]

I have now missed the first session at 11am I wanted to see at @SusHiTech_SUJP 2026, stuck in this queue. 20 mins in and I'm only halfway.

Despite receiving a QR code on the ticket via email - everyone needs to queue up if they havent PRINTED IT OUT ON A4 paper.

What the ... ????

I can't believe a tech event needs a paper ticket in 2026. A terrible, terrible advertisement for Japanese tech.

Happy to be a digital transformation consultant for Sushi Tech next year to improve the customer experience.

@SusHiTech_SUJP
@japantimes

#STT2026

[警視庁サイバー @MPD_cybersec]

【サイバー攻撃対策センター】
GW休暇中・後の隙をついた #サイバー攻撃 の可能性を踏まえ、休暇前対策（監視・対処・連絡要領の確認、データのバックアップ等）、休暇後対策（最新の脆弱性情報の確認、定義ファイルの更新、ログの確認等）の確実な実施をお願いします。
↓関係省庁・機関による資料

[pharos_master @PharosMaster]

「せっかくビギナーの方が参加しているのだから…」と非力を顧みず頑張って説明した結果、実力以上の「達人感」を打ち出してしまい、場の「ゆるさ」を損なってしまう時があります…(;_;)

[むつきんぐ @mutsuking]

勉強会って、いざ参加してみると
「何だ、こんなにゆるやかなんだ〜怖がって損した」
って分かるけど
参加すること自体がハードルな方々が割といらっしゃる。
この「ゆるさ」は、どうやったら伝わるんだろう

[pharos_master @PharosMaster]

AIが部下ならこちらの管理職としての資質が問われそうだけど、上司になってくれたら進捗管理とか閑散期の営業方針とか疲弊時の励ましとか新技術の習得計画とかいろいろ面倒見てくれそうで、生産性高まるかも…

[オレイン（Koji Kuno） @Olein_jp]

やはり AI ってツールだから使いようなんだと思うな。上司がポンコツだとそのチームも成果上がらないって感じになるのと似ている気がする。

ちゃんと指示を出して統率できていれば成果を出せるけど、それができないと結局頭打ちになりそうな気がしている。

知らんけど。

[ミロク💋 @369code_]

WordPressのテーマ表示テスト、ダミーデータどうしてる？🤔

公式テストデータがあるの知ってた？
👉 https://t.co/2pNIf5IHrO

DLしてxmlが管理画面のツール→インポートで使えるよ。
テストが楽になるから試してみてね✌

[pharos_master @PharosMaster]

パターンやテンプレートの検索しやすいアーカイブが欲しいです。プラグインみたいな「おすすめ」コーナーも…

[Katsushi Kawamori @dodesyo312]

WordPressは、TT4以降、テーマはデフォルトテーマ一択で良いと思う。FSEによって「デザインの枠組み」から「ブロックパターンの集合体」へと変わったからかな？
迷路のようなテーマディレクトリなど廃して、プラグインディレクトリをプラグインストアにする様な事を考えても良いんじゃないかと思う。

[pharos_master @PharosMaster]

@japonlove 使わないのは「間違っている」とか「邪悪だ」とかは思わないけど、「使わないともったいないですよ」とは思います

[pharos_master @PharosMaster]

最近のWordPress界隈でのいろんな論争を見ると、こちらの投稿の「WordPress people stopped being "WordPress people", WordPress could regain the community hype that it used to have.」が重みを増す…

[Jeff Matson 👾 @TheJeffMatson]

The WordPress community had has a lot of thoughts about Emdash. Here's mine:

The most important thing to know: it's a CMS layer on top of Astro.

What does that matter? 2 reasons:

1. At it's core, it's not something super new and unstable. Astro is incredibly mature and well maintained.
2. Emdash takes something that was built for modern developers, with a ton of great conveniences, and builds something accessible to WYSIWYG folks on top of it.

I've been using Astro to build sites since the pre-1.0 days. Back then, it was primarily for static content. As it's evolved, it's gone from being a really great SSG to my go-to framework.

IIRC, one of the first ones I put into production was the Pagely Quickstart docs site. Yup, I decided against using WordPress for an enterprise WordPress hosting company's docs site.

Why? Astro was the better tool for the job.

I won't go into all of those details right now, but building and maintaining it in WordPress would have been a PITA. I needed fast, reliable DX with near-zero maintenance.

But here's the problem with Astro: if ya can't write up some code, Astro is gonna be a bad time. It's a framework, not a CMS.

WordPress shines because of the WYSIWYG nature of it. Even your mom can write a blog post in WordPress (she told me in bed last night). If she needs something extra, there's a rich ecosystem of plugins and themes to go wild with. Worst case, she hires a dev to build something custom - WordPress devs far outweigh the demand.

Emdash is to Astro was the WordPress admin dash + post editor is to WordPress core.

But here's the big elephant in the room: is Emdash the "WordPress killer" that it's claimed to be?

Short answer: Ehhhhh... Right now? Not really.
Long answer: Over time, quite possibly. But that's going to depend on a lot of variables.

1. WordPress isn't going anywhere, even if market shifts. We still have demand for COBOL devs, we'll still have demand for WordPress devs for years to come. Companies take an eternity to switch over things that already work fine.

2. The WordPress ecosystem is so huge that it's going to be a while before anyone has 1:1 solutions for all the weird niche stuff. Especially if we're talking about non-devs who need a site builder experience.

3. WordPress could start progressing. If the repo got cleaned up, dev workflows improved, hosting became reliable, and WordPress people stopped being "WordPress people", WordPress could regain the community hype that it used to have.

Anyways, there's my brain dump. If you have thoughts, hit me with 'em.

TLDR: No, Emdash isn't going to murder WordPress. At least not right now. But it has a ton of potential. Only time will tell.

[pharos_master @PharosMaster]

@TheJeffMatson 返信ありがとう。WordPressは柔軟でまだまだ進化の余地が豊富にあるツールなのだから、使う側も既成概念にあまり囚われない方が楽しいですよね。

[pharos_master @PharosMaster]

わかりやすくて腑に落ちる意見です。コードを覚えたりプラットフォームに依存したりせずにWeb上に自分の意見や作品を公開できるツールはあまり無いと思います。

でも「"WordPress people"」のニュアンスはよくわからなかった…。悪口なんだろうなぁ

[Jeff Matson 👾 @TheJeffMatson]

The WordPress community had has a lot of thoughts about Emdash. Here's mine:

The most important thing to know: it's a CMS layer on top of Astro.

What does that matter? 2 reasons:

1. At it's core, it's not something super new and unstable. Astro is incredibly mature and well maintained.
2. Emdash takes something that was built for modern developers, with a ton of great conveniences, and builds something accessible to WYSIWYG folks on top of it.

I've been using Astro to build sites since the pre-1.0 days. Back then, it was primarily for static content. As it's evolved, it's gone from being a really great SSG to my go-to framework.

IIRC, one of the first ones I put into production was the Pagely Quickstart docs site. Yup, I decided against using WordPress for an enterprise WordPress hosting company's docs site.

Why? Astro was the better tool for the job.

I won't go into all of those details right now, but building and maintaining it in WordPress would have been a PITA. I needed fast, reliable DX with near-zero maintenance.

But here's the problem with Astro: if ya can't write up some code, Astro is gonna be a bad time. It's a framework, not a CMS.

WordPress shines because of the WYSIWYG nature of it. Even your mom can write a blog post in WordPress (she told me in bed last night). If she needs something extra, there's a rich ecosystem of plugins and themes to go wild with. Worst case, she hires a dev to build something custom - WordPress devs far outweigh the demand.

Emdash is to Astro was the WordPress admin dash + post editor is to WordPress core.

But here's the big elephant in the room: is Emdash the "WordPress killer" that it's claimed to be?

Short answer: Ehhhhh... Right now? Not really.
Long answer: Over time, quite possibly. But that's going to depend on a lot of variables.

1. WordPress isn't going anywhere, even if market shifts. We still have demand for COBOL devs, we'll still have demand for WordPress devs for years to come. Companies take an eternity to switch over things that already work fine.

2. The WordPress ecosystem is so huge that it's going to be a while before anyone has 1:1 solutions for all the weird niche stuff. Especially if we're talking about non-devs who need a site builder experience.

3. WordPress could start progressing. If the repo got cleaned up, dev workflows improved, hosting became reliable, and WordPress people stopped being "WordPress people", WordPress could regain the community hype that it used to have.

Anyways, there's my brain dump. If you have thoughts, hit me with 'em.

TLDR: No, Emdash isn't going to murder WordPress. At least not right now. But it has a ton of potential. Only time will tell.