Update license to GPL v3

LICENSE

@@ -1,21 +1,674 @@
-MIT License
+                    GNU GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
 
-Copyright (c) 2024 Juan Manzanero
+ Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
 
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
+                            Preamble
 
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
+  The GNU General Public License is a free, copyleft license for
+software and other kinds of works.
 
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+  The licenses for most software and other practical works are designed
+to take away your freedom to share and change the works.  By contrast,
+the GNU General Public License is intended to guarantee your freedom to
+share and change all versions of a program--to make sure it remains free
+software for all its users.  We, the Free Software Foundation, use the
+GNU General Public License for most of our software; it applies also to
+any other work released this way by its authors.  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+them if you wish), that you receive source code or can get it if you
+want it, that you can change the software or use pieces of it in new
+free programs, and that you know you can do these things.
+
+  To protect your rights, we need to prevent others from denying you
+these rights or asking you to surrender the rights.  Therefore, you have
+certain responsibilities if you distribute copies of the software, or if
+you modify it: responsibilities to respect the freedom of others.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must pass on to the recipients the same
+freedoms that you received.  You must make sure that they, too, receive
+or can get the source code.  And you must show them these terms so they
+know their rights.
+
+  Developers that use the GNU GPL protect your rights with two steps:
+(1) assert copyright on the software, and (2) offer you this License
+giving you legal permission to copy, distribute and/or modify it.
+
+  For the developers' and authors' protection, the GPL clearly explains
+that there is no warranty for this free software.  For both users' and
+authors' sake, the GPL requires that modified versions be marked as
+changed, so that their problems will not be attributed erroneously to
+authors of previous versions.
+
+  Some devices are designed to deny users access to install or run
+modified versions of the software inside them, although the manufacturer
+can do so.  This is fundamentally incompatible with the aim of
+protecting users' freedom to change the software.  The systematic
+pattern of such abuse occurs in the area of products for individuals to
+use, which is precisely where it is most unacceptable.  Therefore, we
+have designed this version of the GPL to prohibit the practice for those
+products.  If such problems arise substantially in other domains, we
+stand ready to extend this provision to those domains in future versions
+of the GPL, as needed to protect the freedom of users.
+
+  Finally, every program is threatened constantly by software patents.
+States should not allow patents to restrict development and use of
+software on general-purpose computers, but in those that do, we wish to
+avoid the special danger that patents applied to a free program could
+make it effectively proprietary.  To prevent this, the GPL assures that
+patents cannot be used to render the program non-free.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+                       TERMS AND CONDITIONS
+
+  0. Definitions.
+
+  "This License" refers to version 3 of the GNU General Public License.
+
+  "Copyright" also means copyright-like laws that apply to other kinds of
+works, such as semiconductor masks.
+
+  "The Program" refers to any copyrightable work licensed under this
+License.  Each licensee is addressed as "you".  "Licensees" and
+"recipients" may be individuals or organizations.
+
+  To "modify" a work means to copy from or adapt all or part of the work
+in a fashion requiring copyright permission, other than the making of an
+exact copy.  The resulting work is called a "modified version" of the
+earlier work or a work "based on" the earlier work.
+
+  A "covered work" means either the unmodified Program or a work based
+on the Program.
+
+  To "propagate" a work means to do anything with it that, without
+permission, would make you directly or secondarily liable for
+infringement under applicable copyright law, except executing it on a
+computer or modifying a private copy.  Propagation includes copying,
+distribution (with or without modification), making available to the
+public, and in some countries other activities as well.
+
+  To "convey" a work means any kind of propagation that enables other
+parties to make or receive copies.  Mere interaction with a user through
+a computer network, with no transfer of a copy, is not conveying.
+
+  An interactive user interface displays "Appropriate Legal Notices"
+to the extent that it includes a convenient and prominently visible
+feature that (1) displays an appropriate copyright notice, and (2)
+tells the user that there is no warranty for the work (except to the
+extent that warranties are provided), that licensees may convey the
+work under this License, and how to view a copy of this License.  If
+the interface presents a list of user commands or options, such as a
+menu, a prominent item in the list meets this criterion.
+
+  1. Source Code.
+
+  The "source code" for a work means the preferred form of the work
+for making modifications to it.  "Object code" means any non-source
+form of a work.
+
+  A "Standard Interface" means an interface that either is an official
+standard defined by a recognized standards body, or, in the case of
+interfaces specified for a particular programming language, one that
+is widely used among developers working in that language.
+
+  The "System Libraries" of an executable work include anything, other
+than the work as a whole, that (a) is included in the normal form of
+packaging a Major Component, but which is not part of that Major
+Component, and (b) serves only to enable use of the work with that
+Major Component, or to implement a Standard Interface for which an
+implementation is available to the public in source code form.  A
+"Major Component", in this context, means a major essential component
+(kernel, window system, and so on) of the specific operating system
+(if any) on which the executable work runs, or a compiler used to
+produce the work, or an object code interpreter used to run it.
+
+  The "Corresponding Source" for a work in object code form means all
+the source code needed to generate, install, and (for an executable
+work) run the object code and to modify the work, including scripts to
+control those activities.  However, it does not include the work's
+System Libraries, or general-purpose tools or generally available free
+programs which are used unmodified in performing those activities but
+which are not part of the work.  For example, Corresponding Source
+includes interface definition files associated with source files for
+the work, and the source code for shared libraries and dynamically
+linked subprograms that the work is specifically designed to require,
+such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
+
+  The Corresponding Source need not include anything that users
+can regenerate automatically from other parts of the Corresponding
+Source.
+
+  The Corresponding Source for a work in source code form is that
+same work.
+
+  2. Basic Permissions.
+
+  All rights granted under this License are granted for the term of
+copyright on the Program, and are irrevocable provided the stated
+conditions are met.  This License explicitly affirms your unlimited
+permission to run the unmodified Program.  The output from running a
+covered work is covered by this License only if the output, given its
+content, constitutes a covered work.  This License acknowledges your
+rights of fair use or other equivalent, as provided by copyright law.
+
+  You may make, run and propagate covered works that you do not
+convey, without conditions so long as your license otherwise remains
+in force.  You may convey covered works to others for the sole purpose
+of having them make modifications exclusively for you, or provide you
+with facilities for running those works, provided that you comply with
+the terms of this License in conveying all material for which you do
+not control copyright.  Those thus making or running the covered works
+for you must do so exclusively on your behalf, under your direction
+and control, on terms that prohibit them from making any copies of
+your copyrighted material outside their relationship with you.
+
+  Conveying under any other circumstances is permitted solely under
+the conditions stated below.  Sublicensing is not allowed; section 10
+makes it unnecessary.
+
+  3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+
+  No covered work shall be deemed part of an effective technological
+measure under any applicable law fulfilling obligations under article
+11 of the WIPO copyright treaty adopted on 20 December 1996, or
+similar laws prohibiting or restricting circumvention of such
+measures.
+
+  When you convey a covered work, you waive any legal power to forbid
+circumvention of technological measures to the extent such circumvention
+is effected by exercising rights under this License with respect to
+the covered work, and you disclaim any intention to limit operation or
+modification of the work as a means of enforcing, against the work's
+users, your or third parties' legal rights to forbid circumvention of
+technological measures.
+
+  4. Conveying Verbatim Copies.
+
+  You may convey verbatim copies of the Program's source code as you
+receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy an appropriate copyright notice;
+keep intact all notices stating that this License and any
+non-permissive terms added in accord with section 7 apply to the code;
+keep intact all notices of the absence of any warranty; and give all
+recipients a copy of this License along with the Program.
+
+  You may charge any price or no price for each copy that you convey,
+and you may offer support or warranty protection for a fee.
+
+  5. Conveying Modified Source Versions.
+
+  You may convey a work based on the Program, or the modifications to
+produce it from the Program, in the form of source code under the
+terms of section 4, provided that you also meet all of these conditions:
+
+    a) The work must carry prominent notices stating that you modified
+    it, and giving a relevant date.
+
+    b) The work must carry prominent notices stating that it is
+    released under this License and any conditions added under section
+    7.  This requirement modifies the requirement in section 4 to
+    "keep intact all notices".
+
+    c) You must license the entire work, as a whole, under this
+    License to anyone who comes into possession of a copy.  This
+    License will therefore apply, along with any applicable section 7
+    additional terms, to the whole of the work, and all its parts,
+    regardless of how they are packaged.  This License gives no
+    permission to license the work in any other way, but it does not
+    invalidate such permission if you have separately received it.
+
+    d) If the work has interactive user interfaces, each must display
+    Appropriate Legal Notices; however, if the Program has interactive
+    interfaces that do not display Appropriate Legal Notices, your
+    work need not make them do so.
+
+  A compilation of a covered work with other separate and independent
+works, which are not by their nature extensions of the covered work,
+and which are not combined with it such as to form a larger program,
+in or on a volume of a storage or distribution medium, is called an
+"aggregate" if the compilation and its resulting copyright are not
+used to limit the access or legal rights of the compilation's users
+beyond what the individual works permit.  Inclusion of a covered work
+in an aggregate does not cause this License to apply to the other
+parts of the aggregate.
+
+  6. Conveying Non-Source Forms.
+
+  You may convey a covered work in object code form under the terms
+of sections 4 and 5, provided that you also convey the
+machine-readable Corresponding Source under the terms of this License,
+in one of these ways:
+
+    a) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by the
+    Corresponding Source fixed on a durable physical medium
+    customarily used for software interchange.
+
+    b) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by a
+    written offer, valid for at least three years and valid for as
+    long as you offer spare parts or customer support for that product
+    model, to give anyone who possesses the object code either (1) a
+    copy of the Corresponding Source for all the software in the
+    product that is covered by this License, on a durable physical
+    medium customarily used for software interchange, for a price no
+    more than your reasonable cost of physically performing this
+    conveying of source, or (2) access to copy the
+    Corresponding Source from a network server at no charge.
+
+    c) Convey individual copies of the object code with a copy of the
+    written offer to provide the Corresponding Source.  This
+    alternative is allowed only occasionally and noncommercially, and
+    only if you received the object code with such an offer, in accord
+    with subsection 6b.
+
+    d) Convey the object code by offering access from a designated
+    place (gratis or for a charge), and offer equivalent access to the
+    Corresponding Source in the same way through the same place at no
+    further charge.  You need not require recipients to copy the
+    Corresponding Source along with the object code.  If the place to
+    copy the object code is a network server, the Corresponding Source
+    may be on a different server (operated by you or a third party)
+    that supports equivalent copying facilities, provided you maintain
+    clear directions next to the object code saying where to find the
+    Corresponding Source.  Regardless of what server hosts the
+    Corresponding Source, you remain obligated to ensure that it is
+    available for as long as needed to satisfy these requirements.
+
+    e) Convey the object code using peer-to-peer transmission, provided
+    you inform other peers where the object code and Corresponding
+    Source of the work are being offered to the general public at no
+    charge under subsection 6d.
+
+  A separable portion of the object code, whose source code is excluded
+from the Corresponding Source as a System Library, need not be
+included in conveying the object code work.
+
+  A "User Product" is either (1) a "consumer product", which means any
+tangible personal property which is normally used for personal, family,
+or household purposes, or (2) anything designed or sold for incorporation
+into a dwelling.  In determining whether a product is a consumer product,
+doubtful cases shall be resolved in favor of coverage.  For a particular
+product received by a particular user, "normally used" refers to a
+typical or common use of that class of product, regardless of the status
+of the particular user or of the way in which the particular user
+actually uses, or expects or is expected to use, the product.  A product
+is a consumer product regardless of whether the product has substantial
+commercial, industrial or non-consumer uses, unless such uses represent
+the only significant mode of use of the product.
+
+  "Installation Information" for a User Product means any methods,
+procedures, authorization keys, or other information required to install
+and execute modified versions of a covered work in that User Product from
+a modified version of its Corresponding Source.  The information must
+suffice to ensure that the continued functioning of the modified object
+code is in no case prevented or interfered with solely because
+modification has been made.
+
+  If you convey an object code work under this section in, or with, or
+specifically for use in, a User Product, and the conveying occurs as
+part of a transaction in which the right of possession and use of the
+User Product is transferred to the recipient in perpetuity or for a
+fixed term (regardless of how the transaction is characterized), the
+Corresponding Source conveyed under this section must be accompanied
+by the Installation Information.  But this requirement does not apply
+if neither you nor any third party retains the ability to install
+modified object code on the User Product (for example, the work has
+been installed in ROM).
+
+  The requirement to provide Installation Information does not include a
+requirement to continue to provide support service, warranty, or updates
+for a work that has been modified or installed by the recipient, or for
+the User Product in which it has been modified or installed.  Access to a
+network may be denied when the modification itself materially and
+adversely affects the operation of the network or violates the rules and
+protocols for communication across the network.
+
+  Corresponding Source conveyed, and Installation Information provided,
+in accord with this section must be in a format that is publicly
+documented (and with an implementation available to the public in
+source code form), and must require no special password or key for
+unpacking, reading or copying.
+
+  7. Additional Terms.
+
+  "Additional permissions" are terms that supplement the terms of this
+License by making exceptions from one or more of its conditions.
+Additional permissions that are applicable to the entire Program shall
+be treated as though they were included in this License, to the extent
+that they are valid under applicable law.  If additional permissions
+apply only to part of the Program, that part may be used separately
+under those permissions, but the entire Program remains governed by
+this License without regard to the additional permissions.
+
+  When you convey a copy of a covered work, you may at your option
+remove any additional permissions from that copy, or from any part of
+it.  (Additional permissions may be written to require their own
+removal in certain cases when you modify the work.)  You may place
+additional permissions on material, added by you to a covered work,
+for which you have or can give appropriate copyright permission.
+
+  Notwithstanding any other provision of this License, for material you
+add to a covered work, you may (if authorized by the copyright holders of
+that material) supplement the terms of this License with terms:
+
+    a) Disclaiming warranty or limiting liability differently from the
+    terms of sections 15 and 16 of this License; or
+
+    b) Requiring preservation of specified reasonable legal notices or
+    author attributions in that material or in the Appropriate Legal
+    Notices displayed by works containing it; or
+
+    c) Prohibiting misrepresentation of the origin of that material, or
+    requiring that modified versions of such material be marked in
+    reasonable ways as different from the original version; or
+
+    d) Limiting the use for publicity purposes of names of licensors or
+    authors of the material; or
+
+    e) Declining to grant rights under trademark law for use of some
+    trade names, trademarks, or service marks; or
+
+    f) Requiring indemnification of licensors and authors of that
+    material by anyone who conveys the material (or modified versions of
+    it) with contractual assumptions of liability to the recipient, for
+    any liability that these contractual assumptions directly impose on
+    those licensors and authors.
+
+  All other non-permissive additional terms are considered "further
+restrictions" within the meaning of section 10.  If the Program as you
+received it, or any part of it, contains a notice stating that it is
+governed by this License along with a term that is a further
+restriction, you may remove that term.  If a license document contains
+a further restriction but permits relicensing or conveying under this
+License, you may add to a covered work material governed by the terms
+of that license document, provided that the further restriction does
+not survive such relicensing or conveying.
+
+  If you add terms to a covered work in accord with this section, you
+must place, in the relevant source files, a statement of the
+additional terms that apply to those files, or a notice indicating
+where to find the applicable terms.
+
+  Additional terms, permissive or non-permissive, may be stated in the
+form of a separately written license, or stated as exceptions;
+the above requirements apply either way.
+
+  8. Termination.
+
+  You may not propagate or modify a covered work except as expressly
+provided under this License.  Any attempt otherwise to propagate or
+modify it is void, and will automatically terminate your rights under
+this License (including any patent licenses granted under the third
+paragraph of section 11).
+
+  However, if you cease all violation of this License, then your
+license from a particular copyright holder is reinstated (a)
+provisionally, unless and until the copyright holder explicitly and
+finally terminates your license, and (b) permanently, if the copyright
+holder fails to notify you of the violation by some reasonable means
+prior to 60 days after the cessation.
+
+  Moreover, your license from a particular copyright holder is
+reinstated permanently if the copyright holder notifies you of the
+violation by some reasonable means, this is the first time you have
+received notice of violation of this License (for any work) from that
+copyright holder, and you cure the violation prior to 30 days after
+your receipt of the notice.
+
+  Termination of your rights under this section does not terminate the
+licenses of parties who have received copies or rights from you under
+this License.  If your rights have been terminated and not permanently
+reinstated, you do not qualify to receive new licenses for the same
+material under section 10.
+
+  9. Acceptance Not Required for Having Copies.
+
+  You are not required to accept this License in order to receive or
+run a copy of the Program.  Ancillary propagation of a covered work
+occurring solely as a consequence of using peer-to-peer transmission
+to receive a copy likewise does not require acceptance.  However,
+nothing other than this License grants you permission to propagate or
+modify any covered work.  These actions infringe copyright if you do
+not accept this License.  Therefore, by modifying or propagating a
+covered work, you indicate your acceptance of this License to do so.
+
+  10. Automatic Licensing of Downstream Recipients.
+
+  Each time you convey a covered work, the recipient automatically
+receives a license from the original licensors, to run, modify and
+propagate that work, subject to this License.  You are not responsible
+for enforcing compliance by third parties with this License.
+
+  An "entity transaction" is a transaction transferring control of an
+organization, or substantially all assets of one, or subdividing an
+organization, or merging organizations.  If propagation of a covered
+work results from an entity transaction, each party to that
+transaction who receives a copy of the work also receives whatever
+licenses to the work the party's predecessor in interest had or could
+give under the previous paragraph, plus a right to possession of the
+Corresponding Source of the work from the predecessor in interest, if
+the predecessor has it or can get it with reasonable efforts.
+
+  You may not impose any further restrictions on the exercise of the
+rights granted or affirmed under this License.  For example, you may
+not impose a license fee, royalty, or other charge for exercise of
+rights granted under this License, and you may not initiate litigation
+(including a cross-claim or counterclaim in a lawsuit) alleging that
+any patent claim is infringed by making, using, selling, offering for
+sale, or importing the Program or any portion of it.
+
+  11. Patents.
+
+  A "contributor" is a copyright holder who authorizes use under this
+License of the Program or a work on which the Program is based.  The
+work thus licensed is called the contributor's "contributor version".
+
+  A contributor's "essential patent claims" are all patent claims
+owned or controlled by the contributor, whether already acquired or
+hereafter acquired, that would be infringed by some manner, permitted
+by this License, of making, using, or selling its contributor version,
+but do not include claims that would be infringed only as a
+consequence of further modification of the contributor version.  For
+purposes of this definition, "control" includes the right to grant
+patent sublicenses in a manner consistent with the requirements of
+this License.
+
+  Each contributor grants you a non-exclusive, worldwide, royalty-free
+patent license under the contributor's essential patent claims, to
+make, use, sell, offer for sale, import and otherwise run, modify and
+propagate the contents of its contributor version.
+
+  In the following three paragraphs, a "patent license" is any express
+agreement or commitment, however denominated, not to enforce a patent
+(such as an express permission to practice a patent or covenant not to
+sue for patent infringement).  To "grant" such a patent license to a
+party means to make such an agreement or commitment not to enforce a
+patent against the party.
+
+  If you convey a covered work, knowingly relying on a patent license,
+and the Corresponding Source of the work is not available for anyone
+to copy, free of charge and under the terms of this License, through a
+publicly available network server or other readily accessible means,
+then you must either (1) cause the Corresponding Source to be so
+available, or (2) arrange to deprive yourself of the benefit of the
+patent license for this particular work, or (3) arrange, in a manner
+consistent with the requirements of this License, to extend the patent
+license to downstream recipients.  "Knowingly relying" means you have
+actual knowledge that, but for the patent license, your conveying the
+covered work in a country, or your recipient's use of the covered work
+in a country, would infringe one or more identifiable patents in that
+country that you have reason to believe are valid.
+
+  If, pursuant to or in connection with a single transaction or
+arrangement, you convey, or propagate by procuring conveyance of, a
+covered work, and grant a patent license to some of the parties
+receiving the covered work authorizing them to use, propagate, modify
+or convey a specific copy of the covered work, then the patent license
+you grant is automatically extended to all recipients of the covered
+work and works based on it.
+
+  A patent license is "discriminatory" if it does not include within
+the scope of its coverage, prohibits the exercise of, or is
+conditioned on the non-exercise of one or more of the rights that are
+specifically granted under this License.  You may not convey a covered
+work if you are a party to an arrangement with a third party that is
+in the business of distributing software, under which you make payment
+to the third party based on the extent of your activity of conveying
+the work, and under which the third party grants, to any of the
+parties who would receive the covered work from you, a discriminatory
+patent license (a) in connection with copies of the covered work
+conveyed by you (or copies made from those copies), or (b) primarily
+for and in connection with specific products or compilations that
+contain the covered work, unless you entered into that arrangement,
+or that patent license was granted, prior to 28 March 2007.
+
+  Nothing in this License shall be construed as excluding or limiting
+any implied license or other defenses to infringement that may
+otherwise be available to you under applicable patent law.
+
+  12. No Surrender of Others' Freedom.
+
+  If conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot convey a
+covered work so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you may
+not convey it at all.  For example, if you agree to terms that obligate you
+to collect a royalty for further conveying from those to whom you convey
+the Program, the only way you could satisfy both those terms and this
+License would be to refrain entirely from conveying the Program.
+
+  13. Use with the GNU Affero General Public License.
+
+  Notwithstanding any other provision of this License, you have
+permission to link or combine any covered work with a work licensed
+under version 3 of the GNU Affero General Public License into a single
+combined work, and to convey the resulting work.  The terms of this
+License will continue to apply to the part which is the covered work,
+but the special requirements of the GNU Affero General Public License,
+section 13, concerning interaction through a network will apply to the
+combination as such.
+
+  14. Revised Versions of this License.
+
+  The Free Software Foundation may publish revised and/or new versions of
+the GNU General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+  Each version is given a distinguishing version number.  If the
+Program specifies that a certain numbered version of the GNU General
+Public License "or any later version" applies to it, you have the
+option of following the terms and conditions either of that numbered
+version or of any later version published by the Free Software
+Foundation.  If the Program does not specify a version number of the
+GNU General Public License, you may choose any version ever published
+by the Free Software Foundation.
+
+  If the Program specifies that a proxy can decide which future
+versions of the GNU General Public License can be used, that proxy's
+public statement of acceptance of a version permanently authorizes you
+to choose that version for the Program.
+
+  Later license versions may give you additional or different
+permissions.  However, no additional obligations are imposed on any
+author or copyright holder as a result of your choosing to follow a
+later version.
+
+  15. Disclaimer of Warranty.
+
+  THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
+APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
+HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
+OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
+THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
+IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
+ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+  16. Limitation of Liability.
+
+  IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
+THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
+USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
+DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
+PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
+EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGES.
+
+  17. Interpretation of Sections 15 and 16.
+
+  If the disclaimer of warranty and limitation of liability provided
+above cannot be given local legal effect according to their terms,
+reviewing courts shall apply local law that most closely approximates
+an absolute waiver of all civil liability in connection with the
+Program, unless a warranty or assumption of liability accompanies a
+copy of the Program in return for a fee.
+
+                     END OF TERMS AND CONDITIONS
+
+            How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+state the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This program is free software: you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation, either version 3 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License
+    along with this program.  If not, see <https://www.gnu.org/licenses/>.
+
+Also add information on how to contact you by electronic and paper mail.
+
+  If the program does terminal interaction, make it output a short
+notice like this when it starts in an interactive mode:
+
+    <program>  Copyright (C) <year>  <name of author>
+    This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, your program's commands
+might be different; for a GUI interface, you would use an "about box".
+
+  You should also get your employer (if you work as a programmer) or school,
+if any, to sign a "copyright disclaimer" for the program, if necessary.
+For more information on this, and how to apply and follow the GNU GPL, see
+<https://www.gnu.org/licenses/>.
+
+  The GNU General Public License does not permit incorporating your program
+into proprietary programs.  If your program is a subroutine library, you
+may consider it more useful to permit linking proprietary applications with
+the library.  If this is what you want to do, use the GNU Lesser General
+Public License instead of this License.  But first, please read
+<https://www.gnu.org/licenses/why-not-lgpl.html>.

astro.config.mjs

@@ -1,34 +1,25 @@
 import { defineConfig } from 'astro/config';
 import react from '@astrojs/react';
-import tailwind from '@astrojs/tailwind';
 import mdx from '@astrojs/mdx';
-import rehypePrettyCode from 'rehype-pretty-code';
 import rehypeSlug from 'rehype-slug';
 import sitemap from '@astrojs/sitemap';
-
 import playformInline from '@playform/inline';
+import tailwindcss from '@tailwindcss/vite';
 
 // https://astro.build/config
 export default defineConfig({
-  site: 'https://juancman.dev/',
+  site: 'https://juanmanzanero.com',
   integrations: [
     sitemap(),
     react(),
-    tailwind({
-      applyBaseStyles: false,
-    }),
     mdx({
-      syntaxHighlight: false,
-      rehypePlugins: [
-        rehypeSlug,
-        [
-          rehypePrettyCode,
-          {
-            theme: 'catppuccin-mocha',
-          },
-        ],
-      ],
+      syntaxHighlight: 'shiki',
+      shikiConfig: { theme: 'tokyo-night' },
+      rehypePlugins: [rehypeSlug],
     }),
     playformInline(),
   ],
+  vite: {
+    plugins: [tailwindcss()],
+  },
 });

components.json

@@ -5,7 +5,7 @@
   "tsx": true,
   "tailwind": {
     "config": "tailwind.config.mjs",
-    "css": "./src/styles/globals.css",
+    "css": "./src/styles/global.css",
     "baseColor": "slate",
     "cssVariables": true,
     "prefix": ""

deploy.sh

@@ -3,4 +3,4 @@
 source ./vars.txt
 
 pnpm run build
-rsync -rtvzP -e "ssh -i ${SSH_KEY}" dist/ ${USER}@${HOST}:${DIR}
+rsync -rtvzP dist/ ${USER}@${HOST}:${DIR}

package.json

@@ -11,17 +11,17 @@
   },
   "dependencies": {
     "@astrojs/check": "^0.9.4",
-    "@astrojs/mdx": "^4.1.0",
-    "@astrojs/react": "^4.2.1",
+    "@astrojs/mdx": "^4.2.2",
+    "@astrojs/react": "^4.2.2",
     "@astrojs/rss": "^4.0.11",
-    "@astrojs/sitemap": "^3.2.1",
-    "@astrojs/tailwind": "^5.1.5",
+    "@astrojs/sitemap": "^3.3.0",
     "@playform/inline": "^0.1.1",
     "@radix-ui/react-slot": "^1.1.2",
     "@tailwindcss/typography": "^0.5.16",
-    "@types/react": "^18.3.18",
+    "@tailwindcss/vite": "^4.0.17",
+    "@types/react": "^18.3.20",
     "@types/react-dom": "^18.3.5",
-    "astro": "^5.4.2",
+    "astro": "^5.5.5",
     "class-variance-authority": "^0.7.1",
     "clsx": "^2.1.1",
     "fast-glob": "^3.3.3",
@@ -31,12 +31,11 @@
     "node-html-parser": "^6.1.13",
     "react": "^18.3.1",
     "react-dom": "^18.3.1",
-    "rehype-pretty-code": "^0.13.2",
     "rehype-slug": "^6.0.0",
-    "sanitize-html": "^2.14.0",
+    "sanitize-html": "^2.15.0",
     "sharp": "^0.33.5",
     "tailwind-merge": "^2.6.0",
-    "tailwindcss": "^3.4.17",
+    "tailwindcss": "^4.0.17",
     "tailwindcss-animate": "^1.0.7",
     "typescript": "^5.8.2"
   },

public/publickey.contact@juancman.dev-80e0fe0b452a2fb48511be1b9fb094f3c57bae57.asc

@@ -1,14 +0,0 @@
------BEGIN PGP PUBLIC KEY BLOCK-----
-
-xjMEZQiCxhYJKwYBBAHaRw8BAQdAKsyJoNrC9MIIih/2f+x2jFXe2EW+ufeN
-lIOE0wUbcFbNK2NvbnRhY3RAanVhbmNtYW4uZGV2IDxjb250YWN0QGp1YW5j
-bWFuLmRldj7CjAQQFgoAPgWCZQiCxgQLCQcICZCfsJTzxXuuVwMVCAoEFgAC
-AQIZAQKbAwIeARYhBIDg/gtFKi+0hRG+G5+wlPPFe65XAAAnYAD/conTgzwr
-wtm67uDfpSqauckqEEbiS3kCpVAMDptlc5kBAMp5qzA0RrHWwAtliwjckGta
-Je8cmSNneuO2CmwF0yoHzjgEZQiCxhIKKwYBBAGXVQEFAQEHQM2jOtm0nD9e
-Gj88A9FDxXir8tCxpM+g9FlxeTKrJuJ5AwEIB8J4BBgWCAAqBYJlCILGCZCf
-sJTzxXuuVwKbDBYhBIDg/gtFKi+0hRG+G5+wlPPFe65XAABRXQEA56u9jKY5
-ut2tlCJyauN9llxYwp45cyJNvUdoV/QaKhsBALN7snvKxUGqDoxyQi3LpEKE
-uNjlRcRwNYo3k71qw3YK
-=mkZ4
------END PGP PUBLIC KEY BLOCK-----

public/publickey.contact@juanmanzanero.com-bc93bba27f657fc49730741013ec4a1443f077a9.asc

@@ -0,0 +1,17 @@
+-----BEGIN PGP PUBLIC KEY BLOCK-----
+
+xjMEZ+WbSBYJKwYBBAHaRw8BAQdA2UkpseH3fRqNvy+BxT2R2LCvMCmGRC1C
+Ge+G/MTc33DNNWNvbnRhY3RAanVhbm1hbnphbmVyby5jb20gPGNvbnRhY3RA
+anVhbm1hbnphbmVyby5jb20+wsARBBMWCgCDBYJn5ZtIAwsJBwmQE+xKFEPw
+d6lFFAAAAAAAHAAgc2FsdEBub3RhdGlvbnMub3BlbnBncGpzLm9yZzgw9UWU
+tgBrYlE7QEuOIpn+TKFv3sXrL0ux2JtPMMTOAxUKCAQWAAIBAhkBApsDAh4B
+FiEEvJO7on9lf8SXMHQQE+xKFEPwd6kAAOhvAP9yDtaYDgAPXG6c9vpNYHMO
+e3rRjrQdczkTaW7xuvIv4AD9FRut4JK7KR7/6OQfr46ukX70r50CbDQGFSpB
+CGEgJQvOOARn5ZtIEgorBgEEAZdVAQUBAQdAZPpVrg6u3Mr5HtUW1tX0PC0O
+DmtM2xWEdbsIFLW4fX4DAQgHwr4EGBYKAHAFgmflm0gJkBPsShRD8HepRRQA
+AAAAABwAIHNhbHRAbm90YXRpb25zLm9wZW5wZ3Bqcy5vcmfzpZREDOYf2/4r
+4HTCHMAOtYtKfPreoia/HYX9c53YwQKbDBYhBLyTu6J/ZX/ElzB0EBPsShRD
+8HepAAAsPwD8C74TC7XJvpv+QxIjDeYhqeXTKcWZeYnLz/i7psALS/IA/iKA
+9ZAk6c1v2OGM5t2PfHfIjxD7JWGq/PY0Gq4wKJYJ
+=xo3U
+-----END PGP PUBLIC KEY BLOCK-----

src/components/footer.tsx

@@ -35,12 +35,12 @@ export default function Footer({ lang }: Props) {
       </section>
       <section className='w-max mx-auto flex items-center gap-12'>
         <VerticalLinkButton
-          href={`https://juancman.dev/${lang === 'es' ? 'es/' : ''}feed.xml`}
+          href={`https://juanmanzanero.com/${lang === 'es' ? 'es/' : ''}feed.xml`}
         >
           <RssIcon className='w-6' />
           RSS feed
         </VerticalLinkButton>
-        <VerticalLinkButton href='https://git.juancman.dev/juancmandev/website'>
+        <VerticalLinkButton href='https://git.juanmanzanero.com/juanmanzanero/website'>
           <Code className='w-6' />
           Source Code
         </VerticalLinkButton>

src/components/header.astro

@@ -46,7 +46,7 @@ const { lang } = Astro.props;
           decoding='sync'
           fetchpriority='high'
           class='w-auto h-auto aspect-square'
-          alt='juancmandev logo'
+          alt='Juan Manzanero logo'
         />
       </LinkButton>
     </section>

src/components/ui/button.tsx

@@ -5,7 +5,7 @@ import { cva, type VariantProps } from 'class-variance-authority';
 import { cn } from '@/lib/utils';
 
 const buttonVariants = cva(
-  'inline-flex items-center justify-center whitespace-nowrap rounded-md text-sm font-medium ring-offset-background transition-colors focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-ring focus-visible:ring-offset-2 disabled:pointer-events-none disabled:opacity-50',
+  'inline-flex items-center justify-center whitespace-nowrap rounded-md text-sm font-medium ring-offset-background transition-colors focus-visible:outline-hidden focus-visible:ring-2 focus-visible:ring-ring focus-visible:ring-offset-2 disabled:pointer-events-none disabled:opacity-50',
   {
     variants: {
       variant: {

src/content.config.ts

@@ -4,10 +4,10 @@ import { glob } from 'astro/loaders';
 const contentSchema = z.object({
   title: z.string(),
   description: z.string(),
-  image: z.string(),
-  imageCaption: z.string(),
-  date: z.coerce.date(),
-  tags: z.array(z.string()),
+  image: z.string().optional(),
+  imageCaption: z.string().optional(),
+  date: z.coerce.date().optional(),
+  tags: z.array(z.string()).optional(),
   author: z.string(),
   rss: z.boolean(),
   draft: z.boolean().optional(),

src/content/blog/en/a-better-way-for-consuming-content.mdx

@@ -1,9 +1,6 @@
 ---
 title: A Better Way for Consuming Content
 description: Get your news without visiting websites with algorithms that shows content that you don't want to see.
-tags: [Tech]
-image: /blog/a-better-way-for-consuming-content/banner.webp
-imageCaption: Newspapers. Photo by Ashni on Unsplash
 date: 2024-4-11
 author: Juan Manzanero
 rss: true
@@ -68,10 +65,10 @@ There are many options:
 ### Adding Feeds
 
 Now you need to search for the RSS URL on your favorite website, like
-[this one](https://juancman.dev/rss.xml)!
+[this one](https://juanmanzanero.com/feed.xml)!
 
 ```
-https://juancman.dev/rss.xml
+https://juanmanzanero.com/rss.xml
 ```
 
 If you open it, you'll get a weird page with code similar to HTML.
@@ -105,7 +102,7 @@ https://youtube.com/feeds/videos.xml?channel_id=[CHANNEL ID]
 
 ### My Favorite Feeds
 
-- [juancman.dev (obviously!)](https://www.juancman.dev/rss.xml)
+- [juanmanzanero.com (obviously!)](https://juanmanzanero.com/feed.xml)
 - [Astronomic Picture of the Day (apod)](https://apod.com/feed.rss)
 - [Earth Science Picture of the Day (epod)](https://feeds2.feedburner.com/EarthSciencePictureoftheDay)
 - [Erick Murphy (cool guy)](https://ericmurphy.xyz/index.xml)

src/content/blog/en/build-a-fullstack-app copy.mdx

@@ -1,18 +1,12 @@
 ---
 title: Build a fullstack web app
 description: Build a fullstack web app using Next.js as meta-framework and PostgreSQL as database.
-tags: [Next.js, PostgreSQL, Prisma, Auth.js, tailwindcss, shadcn/ui]
-image: /portfolio/build-a-fullstack-app/banner.png
-imageCaption: Banner with the tech stack used in this tutorial, Next.js, TailwindCSS, shadcn/ui, Prisma, PostgreSQL and Auth.js.
 date: 2024-1-18
 author: Juan Manzanero
 rss: true
 ---
 
-![Banner with the tech stack used in this tutorial, Next.js, TailwindCSS, shadcn/ui, Prisma, PostgreSQL and Auth.js](@/assets/portfolio/build-a-fullstack-app/banner.png)
-_Tech stack used in this tutorial_
-
-[GitHub repo](https://github.com/juancmandev/fullstack-app)
+[GitHub repo](https://github.com/juanmanzanero-com/fullstack-app)
 
 ## Content
 

src/content/blog/en/how-computers-works.mdx

@@ -1,19 +1,11 @@
 ---
 title: How Computers Works
 description: Today we use, in some way, the computer in almost every activity in our lives, it could be for work or just fun, but if we think carefully, computers are an invention from the previous century, and have changed our lives.
-tags: [Tech, Informatic]
-image: /blog/how-computers-works/banner.jpg
-imageCaption: An open laptop. Photo by Philipp Katzenberger on Unsplash
 date: 2023-5-29
 author: Juan Manzanero
 rss: true
 ---
 
-![Open laptop](@/assets/blog/how-computers-works/banner.jpg) _An open laptop. Photo by
-[Philipp Katzenberger](https://unsplash.com/@fantasyflip?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText')
-on
-[Unsplash](https://unsplash.com/photos/iIJrUoeRoCQ?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText)_
-
 Today we use, in some way, the computer in almost every activity in our lives, it could be for work or just fun, but if we think carefully, computers are an invention from the previous century, and have changed our lives.
 
 New works have appeared, new careers to study, and new problems to be solved.

src/content/blog/en/human-to-js.mdx

@@ -1,76 +0,0 @@
----
-title: Human to JS
-description: Translate human language to JavaScript code!
-tags: [ChatGPT, Next.js, JavaScript, Vercel]
-image: /portfolio/human-to-js/banner.png
-imageCaption: Human to JS Banner
-date: 2023-4-14
-author: Juan Manzanero
-rss: true
----
-
-![Human to JS banner](@/assets/portfolio/human-to-js/banner.png) _Human to JS diagram_
-
-_This project has been achieved._
-
-## Background
-
-I’m always looking to grow my career by learning new technologies as well known
-Software Engineer; however, that could be dangerous because Software Engineer is
-not about using the ultimate tech stack but making things happen.
-
-## Inspiration source
-
-I was checking Twitter until I found a tweet where a person created a side
-project over a weekend. That project is
-[SQL Translator](https://www.sqltranslate.app/), a simple UI to put text input
-describing a query; then you get the query into SQL, simple!
-
-[@whoiskatrin](https://twitter.com/whoiskatrin?ref_src=twsrc%5Etfw%7Ctwcamp%5Etweetembed%7Ctwterm%5E1634973237829599233%7Ctwgr%5Eb49b9d28e6ea7383ef16ea3c8c6040656ff0c944%7Ctwcon%5Es1_&ref_url=https%3A%2F%2Fpublish.twitter.com%2F%3Fquery%3Dhttps3A2F2Ftwitter.com2Fwhoiskatrin2Fstatus2F1634973237829599233widget%3DTweet)
-used ChatGPT API to send a prompt typed by the user, and then show SQL response
-into a component to copy to the clipboard. That was enough to get the deserved
-attention of the community.
-[Tweet link](https://twitter.com/whoiskatrin/status/1634973237829599233)
-
-## My idea
-
-> _“Why not a web app to type a prompt to generate JavaScript code?”_
-
-So I started to build my idea using this tech stack:
-
-- **Next.js**: Web framework to build the UI and Next.js provides you with an
-  API directory to communicate with ChatGPT API
-- **MUI**: To use the UI components and as a design system
-- **Formik & Yup**: To manage the state of the prompt form and create validation
-  schemas
-
-Using all these technologies I build a simple UI with a MUI Card component, then
-I created a form where I manage all the inputs with Formik, the text and select
-inputs are directly from MUI, and to create the validation schema I used Yup to
-mark as required those fields and don’t send them empty.
-
-With the UI finished, I started creating the endpoint in the API directory to
-consume ChatGPT’s API, just using a fetch
-like [@whoiskatrin](https://twitter.com/whoiskatrin?ref_src=twsrc%5Etfw%7Ctwcamp%5Etweetembed%7Ctwterm%5E1634973237829599233%7Ctwgr%5Eb49b9d28e6ea7383ef16ea3c8c6040656ff0c944%7Ctwcon%5Es1_&ref_url=https%3A%2F%2Fpublish.twitter.com%2F%3Fquery%3Dhttps3A2F2Ftwitter.com2Fwhoiskatrin2Fstatus2F1634973237829599233widget%3DTweet)’s
-project, indicating which OpenAI model to use, in this case, *text-davinci-003*,
-you can learn more about those
-models [here](https://platform.openai.com/docs/api-reference/models/list).
-Obviously, in that request, I send the prompt from the user into a string
-indicating ChatGPT to only give me the code, without comments or more results.
-
-## Added value
-
-Yes, there’re options like GitHub Copilot that resolve that problem, that’s why
-I added a select option to choose if the syntax should be an arrow function or a
-simple function.
-
-I’ll add more features, like a TypeScript option, and use a TS Interface to use
-as a reference, but now I’m working on more projects!
-
-## Inspiring people!
-
-The cool thing about side projects is that inspires people like us, we can use
-our tech skill that serves the bread on the table to transform ideas into
-products, and products into a community, as
-[@Serudda](https://twitter.com/serudda) talks in this
-[video](https://www.youtube.com/watch?v=LXgPNdw8avI&t) (video audio in Spanish).

src/content/blog/en/i-participated-in-a-hackathon.mdx

@@ -1,17 +1,11 @@
 ---
 title: I participated in a Hackathon
 description: I recently participated in a Supabase Hackathon, forming a team with people from other countries.
-tags: [Tech, Hobby, Hackaton]
-image: /blog/i-participated-in-a-hackathon/banner.png
-imageCaption: 'Tech stack used: Supabase, Next.js and Shadcn/UI, My first hackathon!'
 date: 2023-8-16
 author: Juan Manzanero
 rss: true
 ---
 
-![Tech Stack](@/assets/blog/i-participated-in-a-hackathon/banner.png) _Tech stack used:
-Supabase, Next.js and Shadcn/UI, My first hackathon!_
-
 I recently participated in a Supabase Hackathon, forming a team with people from other countries.
 
 The Hackathon thematic was free, the only main rule is to use Supabase for any

src/content/blog/en/i-will-not-continue-creating-content-in-spanish-for-my-website.mdx

@@ -1,36 +0,0 @@
----
-title: I will not continue creating content in Spanish for my website
-description:
-  I had the idea of maintaining my website in both English and Spanish; however,
-  that is giving me some trouble, like taking more time to create content.
-tags: [Personal]
-image: /blog/i-will-not-continue-creating-content-in-spanish-for-my-website/banner.jpg
-imageCaption: Letters mixed
-date: 2024-2-20
-author: Juan Manzanero
-rss: false
-draft: true
----
-
-![Letters mixed](@/assets/blog/i-will-not-continue-creating-content-in-spanish-for-my-website/banner.jpg)
-_Mixed letters. Photo by
-[Jason Leung](https://unsplash.com/@ninjason?utm_content=creditCopyText&utm_medium=referral&utm_source=unsplash)
-on
-[Unsplash](https://unsplash.com/photos/red-alphabet-decors-0sBTrm726C8?utm_content=creditCopyText&utm_medium=referral&utm_source=unsplash)_
-
-_Note: I retaked redacting in Spanish for my website, but I'll keep this post
-anyway_
-
-I had the idea of maintaining my website in both English and Spanish; however,
-that is giving me some trouble, like taking more time to create content.
-
-That's why I have decided to only create content in English for now and in the
-future.
-
-It doesn't mean that I reject my mother tongue or something like that, but just
-practicality.
-
-I'll try to update the links to my posts shared on social media, as this website
-will be just juancman.dev/blog instead of juancman.dev/[locale]/blog.
-
-However, if you want to contact me in Spanish, feel free to do it.

src/content/blog/en/next-intl-blog-template.mdx

@@ -1,18 +1,12 @@
 ---
 title: Next Intl Blog Template
 description: Start your blog in multiple languages!
-tags: [Next.js, next-intl, tailwindcss]
-image: /portfolio/next-intl-blog-template/banner.png
-imageCaption: Next Intl Blog Template banner
 date: 2023-12-18
 author: Juan Manzanero
 rss: true
 ---
 
-![Next Intl Blog Template banner](@/assets/portfolio/next-intl-blog-template/banner.png)
-_Next Intl Blog Template banner_
-
-[GitHub](https://github.com/juancmandev/next-intl-blog-template)
+[GitHub](https://github.com/juanmanzanero-com/next-intl-blog-template)
 
 [Website](https://next-intl-blog-template.vercel.app/en)
 
@@ -145,4 +139,4 @@ export default async function Page(props: TPage) {
 }
 ```
 
-[You can fork this template here](https://github.com/juancmandev/next-intl-blog-template)
+[You can fork this template here](https://github.com/juanmanzanero-com/next-intl-blog-template)

src/content/blog/en/peddler-app.mdx

@@ -1,65 +0,0 @@
----
-title: Peddler App
-description: You hear the ice cream man in his truck, you try to catch him, but the guy is already far away.
-tags: [Tech, SideProject]
-image: "/blog/peddler-app/banner.png"
-imageCaption: Peddler App provisional logo
-date: 2023-12-11
-author: Juan Manzanero
-rss: true
----
-
-![Peddler App provisional logo](@/assets/blog/peddler-app/banner.png) _Peddler App
-provisional logo_
-
-## The idea
-
-You hear the ice cream man in his truck, you try to catch him, but the guy is already far away.
-
-Why not get a notification on your phone when the ice cream man is near you? So
-you can just tap the notification and request the ice cream man to go to your
-location.
-
-That's the purpose of this app.
-
-## Overwhelming for me
-
-I'd never developed a big app just by myself, but I want to try and see what
-happens.
-
-I want to follow the Indie Hacker way, sharing in public the progress, and
-getting feedback from the community.
-
-This post is the first step before designing in Figma or even creating the
-landing page, so I want to hear if you're interested, why you're not, or what
-would be great for the app.
-
-## Starting small
-
-I really want to start small, launching a Minimum Viable Product (MVP), with the
-next features:
-
-- User registration and login
-- Two types of users, peddlers and customers
-- Peddlers
-  - If the user is a peddler (wants to sell), redirect to the peddler form
-  - Peddlers can create a profile with the name of their company and products
-    that offer, for example ice cream, candy, etc
-  - Once the registration is finished, peddlers can start routes
-  - The app gets the location of the peddler, showing it on a map
-  - The backend will detect if the peddler enters a radius of a customer, and
-    send a push notification to the customer
-  - Once the peddler has a request, the app will show the location of the
-    requesting customer on the map
-  - The peddler can go to the destination, and fulfill the transaction
-- Customers
-  - Customers can just create a profile with their name or alias, and set
-    locations, for example: house
-  - Once a peddler is near, the backend will send a notification to the customer
-  - The customer taps and confirms the notification
-
-Of course, customers would change notifications settings and more, but that's
-the core idea.
-
-For the MVP I don't want to implement in-app payments, but of course, it could
-be a future feature.

src/content/blog/en/rewind-2023-and-future-plans.mdx

@@ -1,19 +1,11 @@
 ---
 title: Rewind 2023 and future plans
 description: My rewind for 2023 and my plans for 2024 and beyond.
-tags: [Thoughts]
-image: /blog/rewind-2023-and-future-plans/banner.jpg
-imageCaption: A sunset with a sign, photo by Javier Allegue Barros on Unsplash
 date: 2023-12-16
 author: Juan Manzanero
 rss: true
 ---
 
-![A sunset with a sign](@/assets/blog/rewind-2023-and-future-plans/banner.jpg) _Photo by
-[Javier Allegue Barros](https://unsplash.com/@soymeraki?utm_content=creditCopyText&utm_medium=referral&utm_source=unsplash)
-on
-[Unsplash](https://unsplash.com/photos/silhouette-of-road-signage-during-golden-hour-C7B-ExXpOIE?utm_content=creditCopyText&utm_medium=referral&utm_source=unsplash)_
-
 My rewind for 2023 and my plans for 2024 and beyond.
 
 I hope you are having a good time this holiday.

src/content/blog/en/the-monotony-of-social-media.mdx

@@ -1,21 +1,15 @@
 ---
 title: The Monotony of Social Media
-description: Abstracting human interaction using software has caused many problems that didn’t exist before.
-tags: [Thoughts]
-image: /blog/the-monotony-of-social-media/banner.jpg
-imageCaption: Person checking social media. Photo by Austin Distel on Unsplash
+description:
+  Abstracting human interaction using software has caused many problems that
+  didn’t exist before.
 date: 2023-7-17
 author: Juan Manzanero
 rss: true
 ---
 
-![Person checking social media](@/assets/blog/the-monotony-of-social-media/banner.jpg)
-_Person checking social media. Photo by
-[Austin Distel](https://unsplash.com/@austindistel?utm_content=creditCopyText&utm_medium=referral&utm_source=unsplash)
-on
-[Unsplash](https://unsplash.com/photos/person-using-both-laptop-and-smartphone-tLZhFRLj6nY?utm_content=creditCopyText&utm_medium=referral&utm_source=unsplash)_
-
-Abstracting human interaction using software has caused many problems that didn’t exist before.
+Abstracting human interaction using software has caused many problems that
+didn’t exist before.
 
 It’s obvious, a lot of interactions on the Internet occurs through social media,
 letting you send friend requests, chat, or share memes and photos. However,

src/content/blog/en/website-2.0.mdx

@@ -1,18 +1,12 @@
 ---
 title: The Reason to Create a Version 2.0 of my Website
 description: I commited some errors when creating the first version of my website, here I will share what I have learned.
-tags: [Tech]
-image: /blog/website-2.0/banner.png
-imageCaption: Tech Stack of this website. Next.js, Vercel, React.js, TypeScript and TailwindCSS
 date: 2023-4-7
 author: Juan Manzanero
 rss: false
 draft: true
 ---
 
-![Tech stack](@/assets/blog/website-2.0/banner.png) _Tech Stack of this website.
-Next.js, Vercel, React.js, TypeScript and TailwindCSS_
-
 I commited some errors when creating the first version of my website, here I will share what I have learned.
 
 The first version of my website was one of my biggest projects so fat, but

src/content/blog/en/website-migrated-to-astro.mdx

@@ -1,17 +1,11 @@
 ---
 title: Website migrated to Astro
 description: I migrated this website to Astro, so I can test it and I really like it the features of Astro.
-tags: [Astro]
-image: /portfolio/website-migrated-to-astro/banner.png
-imageCaption: Next Intl Blog Template banner
 date: 2024-6-26
 author: Juan Manzanero
 rss: true
 ---
 
-![Banner showing the tech stack](@/assets/portfolio/website-migrated-to-astro/banner.png)
-_Tech stack used. Astro, React, TailwindCSS, MDX_
-
 So yeah, I proved this tool for building static websites, as Vercel has been taking weird decisions about the direction of the development of Next.js.
 
 That, and I realized that I just need a full static website, no need of SSR even for the Microblog page, as I don't post daily, I can just redeploy the website, so the last post is rendered.

src/content/blog/en/workarise.mdx

@@ -1,74 +0,0 @@
----
-title: Workarise
-description: Workarise Web App, manage tasks with your team.
-tags: [React.js, Vite.js, MUI, Firebase, GCP, Node.js]
-image: /portfolio/workarise/banner.png
-imageCaption: Workarise Banner
-date: 2023-4-13
-author: Juan Manzanero
-rss: true
----
-
-![Workarise Banner](@/assets/portfolio/workarise/banner.png) _Workarise Banner_
-
-[Website](https://workarise.com)
-
-## Overview
-
-[Workarise](http://workarise.com) is a Team Manager Software as a Service to
-create task cards assigning people, set a start and due date, add attachments
-files, etc.
-
-You can use the Calendar to see the tasks' due dates and schedule Google Meet
-events authorizing the use of your Google Calendar. You can edit and delete
-events which sync with your Google Calendar and guests' Google Calendars. The
-Gantt provides you with a timeline to check task duration.
-
-The web app is developed with [React.js](https://react.dev/),
-using [Vite.js](https://vitejs.dev/) to run the development environment. For
-functionality like modals, and popovers we use [MUI](https://mui.com/). To
-manage the state of components we’re using useContext.
-
-To create Google Meet events and sync the calendar we'd develop a small Node.js
-API to use Google OAuth 2 API, as we need to prompt our users to give access to
-their Google Calendars.
-
-Currently, Workarise is in the first version,
-using [Firebase](https://firebase.google.com/) to authenticate users and store
-raw data and files. Firebase
-uses [Firestore](https://firebase.google.com/docs/firestore), a NoSQL DB,
-however we’re developing an API using [Django](https://www.djangoproject.com/)
-running on [Cloud Run](https://cloud.google.com/run) connected
-to [Cloud SQL](https://cloud.google.com/sql) to a MySQL instance, as we’ll be
-using a SQL DB in the future. Currently the web app and landing are deployed on
-Firebase Hosting, but we’ll move the landing page to Vercel, and it’ll be
-updated to use Next.js in the future to optimize SEO and publish blog posts.
-
-## My impact in Workarise
-
-Currently, we’re developing an MVP, and everyone is working part-time on this
-project. I joined in December, but before there wasn’t a product that users can
-use, so as I was the only Frontend Engineer at that moment I taked full
-responsibility for delivering something that can be considered an MVP.
-
-It took me like 3 months to achieve that, I updated some dependencies of the
-project to improve the development flow, and I suggested using Firebase as
-Backend and Hosting.
-
-Thanks to all this we got our first users and feedback, so we’re working on that
-feedback to keep improving our app, our users like the design and simplicity!
-
-At the moment there’re 3 engineers in the team, 2 on the front (including me)
-and 1 on the back, but I’m helping to our Backend Engineer to deploy on GCP to
-production the API and DB, and I'm guiding the new Frontend to deliver new
-features, he’d developed the responsive design and some features to complement
-the task cards.
-
-I’m happy to test my skills in this project, it’s not easy to take more
-responsibility with less than 2 years of labor experience, and it’d help me to
-grow a lot in these months.
-
-Even if the market doesn’t consider my years of experience as a senior, I think
-that doesn’t matter at all, the only thing that matters is that you can
-understand why you’re using code, to create solutions and reach people across
-their computers.

src/content/blog/es/como-funcionan-las-computadoras.mdx

@@ -1,19 +1,11 @@
 ---
 title: Cómo Funcionan las Computadoras
 description: Hoy en día usamos, de alguna manera, una computadora en casi toda actividad de nuestras vidas, volviéndose indispensables.
-tags: [Tech, Informatic]
-image: /blog/how-computers-works/banner.jpg
-imageCaption: Una laptop abierta. Foto de Philipp Katzenberger en Unsplash
 date: 2023-5-29
 author: Juan Manzanero
 rss: true
 ---
 
-![Una laptop abierta](@/assets/blog/how-computers-works/banner.jpg) _Una laptop abierta. Foto de
-[Philipp Katzenberger](https://unsplash.com/@fantasyflip?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText')
-en
-[Unsplash](https://unsplash.com/photos/iIJrUoeRoCQ?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText)_
-
 Hoy en día usamos, de alguna manera, una computadora en casi toda actividad de nuestras vidas, podría ser para trabajo o solo por diversión, pero si lo pensamos con cuidado, las computadoras son un invento del siglo pasado, y han cambiado nuestras vidas.
 
 Nuevos empleos han aparecido, nuevas carreras por estudiar, nuevos problemas por resolver.

src/content/blog/es/construye-una-app-fullstack.mdx

@@ -1,18 +1,12 @@
 ---
 title: Construye una App Fullstack
 description: Construye una app fullstack usando Next.js como meta-framework y PostgreSQL como base de datos.
-tags: [Next.js, PostgreSQL, Prisma, Auth.js, tailwindcss, shadcn/ui]
-image: /portfolio/build-a-fullstack-app/banner.png
-imageCaption: "Banner con el teck stack usado en este tutorial, Next.js, TailwindCSS, shadcn/ui, Prisma, PostgreSQL y Auth.js."
 date: 2024-1-18
 author: Juan Manzanero
 rss: true
 ---
 
-![Banner con el teck stack usado en este tutorial, Next.js, TailwindCSS, shadcn/ui, Prisma, PostgreSQL y Auth.js.](@/assets/portfolio/build-a-fullstack-app/banner.png)
-_Tech stack usado en este tutorial_
-
-[GitHub repo](https://github.com/juancmandev/fullstack-app)
+[GitHub repo](https://github.com/juanmanzanero-com/fullstack-app)
 
 # Contenido
 
@@ -1198,4 +1192,3 @@ Como puedes ver, crear una app fullstack con Next.js es muy fácil.
 
 Por supuesto, se puede mejorar, agregando validación del lado del servidor para los inputs, agregando paginación para los posts en el home, etc.
 
-Si quieres que trabajemos juntos, envíame un correo a [contact@juancman.dev](mailto:contact@juancman.dev).

src/content/blog/es/human-to-js.mdx

@@ -1,49 +0,0 @@
----
-title: Human to JS
-description: ¡Traduce lenguaje humano a código JavaScript!
-tags: [ChatGPT, Next.js, JavaScript, Vercel]
-image: /portfolio/human-to-js/banner.png
-imageCaption: Human to JS Banner
-date: 2023-4-14
-author: Juan Manzanero
-rss: true
----
-
-![Human to JS banner](@/assets/portfolio/human-to-js/banner.png) _Human to JS diagram_
-
-_Este proyecto ha sido archivado._
-
-## Retrospectiva
-
-Siempre estoy buscando crecer mi carrera aprendiendo nuevas tecnologías como buen Ingeniero en Software; sin embargo, eso puede ser peligroso ya que la Ingeniería en Software no es sobre usar el último tech stack, sino de hacer que las cosas ocurran.
-
-## Fuente de inspiración
-
-Estaba revisando Twitter hasta que encontré un tweet de una persona que había creado un **side project** en un fin de semana. Ese proyecto es [SQL Translator](https://www.sqltranslate.app/), una simple UI para escribir un texto describiendo una consulta, entonces obtienes la consulta en código SQL, ¡simple!
-
-[@woiskatring](https://twitter.com/whoiskatrin?ref_src=twsrc%5Etfw%7Ctwcamp%5Etweetembed%7Ctwterm%5E1634973237829599233%7Ctwgr%5Eb49b9d28e6ea7383ef16ea3c8c6040656ff0c944%7Ctwcon%5Es1_&ref_url=https%3A%2F%2Fpublish.twitter.com%2F%3Fquery%3Dhttps3A2F2Ftwitter.com2Fwhoiskatrin2Fstatus2F1634973237829599233widget%3DTweet) usó la API de ChatGPT para enviar un prompt escrito por el user, devolviendo una respuesta en SQL dentro de un component para copiar al portapapeles. Eso fue suficiente para obtener la atención merecida por la comunidad. [Tweet link](https://twitter.com/whoiskatrin/status/1634973237829599233))
-
-## Mi idea
-
-> _¿Por qué no una web app para escribir un prompt y genera código JavaScript?_
-
-Así que comencé a construir mi idea usando este tech stack:
-
-- **Next.js**: Framework web para construir la UI y como Next.js provee un directorio API para comunicarte con la API de ChatGPT
-- **MUI**: Para usar los UI components como sistema de diseño
-- **Fromik & Yup**: Para manejar el estado del formulario del prompt y crear esquemas de validación
-- **react-syntax-highlighter**: Para mostrar la respuesta de ChatGPT
-
-Usando todas estas tecnologías construí una UI simple usando el MUI Card component, entonces creé el form donde manejé todos los inputs con Formik, los inputs de tipo text y select son los por defecto de MUI, y para crear el esquema de validación usé Yup para marcar como required aquellos inputs para no enviarlos vacíos.
-
-Con la UI finalizada, comencé a crear el endpoint en el directorio de la API para consumir la API de ChatGPT, tan solo usando un fetch como en el proyecto de [@whoiskatrin](https://twitter.com/whoiskatrin?ref_src=twsrc%5Etfw%7Ctwcamp%5Etweetembed%7Ctwterm%5E1634973237829599233%7Ctwgr%5Eb49b9d28e6ea7383ef16ea3c8c6040656ff0c944%7Ctwcon%5Es1_&ref_url=https%3A%2F%2Fpublish.twitter.com%2F%3Fquery%3Dhttps3A2F2Ftwitter.com2Fwhoiskatrin2Fstatus2F1634973237829599233widget%3DTweet). indicando qué modelo de OpenAI utilizar, en este caso _text-davinci-003_, puedes aprender más de los esos modelos [aquí](https://platform.openai.com/docs/api-reference/models/list). Obviamente en la petición envié el prompt del user dentro de un string indicando a ChatGPT que solo me de el código, sin comentarios o resultados adicionales.
-
-## Valor añadido
-
-Sí, hay opciones como GitHub Copilot que resuelven ese problema, y eso es por qué agregué la opción de escoger qué tipo de sintaxis usar, arrow function o simple function.
-
-Añadiré más features, como una opción para TypeScript, y usar una TS Interface para que se use como referencia, ¡pero ahora estoy trabajando en más proyectos!
-
-## Inspirando personas
-
-Lo genial de los side projects is que inspira personas como nosotros, podemos usar nuestras habilidades técnicas que llevan el pan a la mesa para transformar ideas en productos, y productos en comunidades, tal como [@Serudda](https://twitter.com/serudda) habla en este [video](https://www.youtube.com/watch?v=LXgPNdw8avI&t).

src/content/blog/es/la-monotonia-de-las-redes-sociales.mdx

@@ -1,20 +1,11 @@
 ---
 title: La Monotonia de las Redes Sociales
 description: La abstracción de la interacción humana mediante software ha causado muchos problemas que antes no existían.
-tags: [Thoughts]
-image: /blog/the-monotony-of-social-media/banner.jpg
-imageCaption: Persona checando sus redes sociales. Foto de Austin Distel en Unsplash
 date: 2023-7-17
 author: Juan Manzanero
 rss: true
 ---
 
-![Persona checando sus redes sociales](@/assets/blog/the-monotony-of-social-media/banner.jpg)
-_Persona checando sus redes sociales. Foto de
-[Austin Distel](https://unsplash.com/@austindistel?utm_content=creditCopyText&utm_medium=referral&utm_source=unsplash)
-en
-[Unsplash](https://unsplash.com/photos/person-using-both-laptop-and-smartphone-tLZhFRLj6nY?utm_content=creditCopyText&utm_medium=referral&utm_source=unsplash)_
-
 Es evidente que muchas interacciones en Internet ocurren a través de las redes sociales,
 lo que te permite enviar solicitudes de amistad, chatear o compartir memes y fotos.
 

src/content/blog/es/next-intl-blog-template.mdx

@@ -1,18 +1,12 @@
 ---
 title: Next Intl Blog Template
 description: ¡Comienza tu blog en múltiples idiomas!
-tags: [Next.js, next-intl, tailwindcss]
-image: /portfolio/next-intl-blog-template/banner.png
-imageCaption: Next Intl Blog Template banner
 date: 2023-12-18
 author: Juan Manzanero
 rss: true
 ---
 
-![Next Intl Blog Template banner](@/assets/portfolio/next-intl-blog-template/banner.png)
-_Next Intl Blog Template banner_
-
-[GitHub](https://github.com/juancmandev/next-intl-blog-template)
+[GitHub](https://github.com/juanmanzanero-com/next-intl-blog-template)
 
 [Website](https://next-intl-blog-template.vercel.app/en)
 
@@ -35,9 +29,9 @@ Este template es una extensión de [next-intl](https://next-intl-docs.vercel.app
 Puedes agregar o remover locales en el archivo `src/lang/locales.ts`.
 
 ```ts title="src/lang/locales.ts"
-export type locales = "en" | "es";
+export type locales = 'en' | 'es';
 
-export const localesList: locales[] = ["en", "es"];
+export const localesList: locales[] = ['en', 'es'];
 ```
 
 Solo agrega o remueve un locale de la constante `locales`, y agrega o remueve el locale de la lista.
@@ -48,7 +42,7 @@ La lista es usada para la generación de rutas estáticas en
 `src/app/[locale]/layout.tsx`.
 
 ```ts title="src/app/[locale]/layout.tsx"
-import { localesList } from "@/lang/locales";
+import { localesList } from '@/lang/locales';
 
 export function generateStaticParams() {
   return localesList.map((locale) => ({ locale }));
@@ -61,7 +55,7 @@ Recuerda actualizar el matcher en `src/middleware.ts`.
 //...
 
 export const config = {
-  matcher: ["/", "/(en|es)/:path*"],
+  matcher: ['/', '/(en|es)/:path*'],
 };
 ```
 
@@ -76,15 +70,15 @@ Dentro crea el archivo .mdx con un nombre único, el nombre será usado como slu
 Para crear una sección de blog, usarás la función _getAllContent_ en tu ruta, por ejemplo: `src/app/[locale]/blog/[slug]/page.tsx`.
 
 ```tsx title="src/app/[locale]/blog/[slug]/page.tsx"
-import { Mdx } from "@/components";
-import { TParamsLocale, TPage, TSlugLang } from "@/types";
-import { Metadata } from "next";
-import { getAllContent, getContent } from "@/utils/getContent";
+import { Mdx } from '@/components';
+import { TParamsLocale, TPage, TSlugLang } from '@/types';
+import { Metadata } from 'next';
+import { getAllContent, getContent } from '@/utils/getContent';
 
 export async function generateStaticParams(
-  props: TParamsLocale,
+  props: TParamsLocale
 ): Promise<TSlugLang[]> {
-  const blogs = await getAllContent(props.params.locale, "blog");
+  const blogs = await getAllContent(props.params.locale, 'blog');
 
   if (!blogs) return [];
 
@@ -105,7 +99,7 @@ Puedes obtener la metadata del archivo `.mdx` también.
 //...
 
 export async function generateMetadata(props: TPage): Promise<Metadata> {
-  const blog = await getContent(props.params.locale, "blog", props.params.slug);
+  const blog = await getContent(props.params.locale, 'blog', props.params.slug);
 
   if (!blog) return {};
 
@@ -124,7 +118,7 @@ Entonces, renderiza el contenido usando el componente _Mdx_.
 //...
 
 export default async function Page(props: TPage) {
-  const post = await getContent(props.params.locale, "blog", props.params.slug);
+  const post = await getContent(props.params.locale, 'blog', props.params.slug);
 
   if (!post) return null;
 
@@ -132,8 +126,4 @@ export default async function Page(props: TPage) {
 }
 ```
 
-[Puedes hacer un fork de este template aquí](https://github.com/juancmandev/next-intl-blog-template)
-
-## Contacto
-
-Si te interesa **trabajar juntos** en un website con internacionalización con Next.js, envíame un correo a [contact@juancman.dev](mailto:contact@juancman.dev)
+[Puedes hacer un fork de este template aquí](https://github.com/juanmanzanero-com/next-intl-blog-template)

src/content/blog/es/participe-en-una-hackaton.mdx

@@ -1,17 +1,11 @@
 ---
 title: Participé en una Hackaton
 description: Recientemente participé en un Hackathon de Supabase, formando un equipo con personas de otros países.
-tags: [Tech, Hobby, Hackaton]
-image: /blog/i-participated-in-a-hackathon/banner.png
-imageCaption: "Tech stack utilizado: Supabase, Next.js y Shadcn/UI, ¡mi primera hackathon!"
 date: 2023-8-16
 author: Juan Manzanero
 rss: true
 ---
 
-![Tech Stack](@/assets/blog/i-participated-in-a-hackathon/banner.png) _Tech stack used:
-Supabase, Next.js and Shadcn/UI, My first hackathon!_
-
 Recientemente participé en un [Hackathon de Supabase](https://supabase.com/blog/supabase-lw8-hackathon),
 formando un equipo con personas de otros países, uno de Bangladesh y otro de Brasil,
 utilizando inglés para comunicarnos en Discord.

src/content/blog/es/peddler-app.mdx

@@ -1,54 +0,0 @@
----
-title: Peddler App
-description: Escuchas al heladero en su camioneta, intentas alcanzarlo, pero ya está lejos.
-tags: [Tech, SideProject]
-image: /blog/peddler-app/banner.png
-imageCaption: Logo provisional de Peddler App
-date: 2023-12-11
-author: Juan Manzanero
-rss: true
----
-
-![Logo provisional de Peddler App](@/assets/blog/peddler-app/banner.png) _Logo provisional de Peddler App_
-
-## La idea
-
-Escuchas al heladero en su camioneta, intentas alcanzarlo, pero ya está lejos.
-
-¿Por qué no recibir una notificación en tu celular cuando el heladero está cerca de ti?, así puedes tocar la
-notificación y solicitar al heladero que pase en tu ubicación.
-
-Ese es el propósito de esta app.
-
-## Abrumador para mi
-
-Nunca he desarrollado una app grande por mi mismo, pero quiero intentarlo y ver qué ocurre.
-
-Quiero seguir el camino Indie Hacker, compartiendo en público el progreso, y recibiendo feedback
-de la comunidad.
-
-Este post es el primer paso antes de diseñarlo en Figma o incluso crear la landing page, así que
-quiero escuchar si te interesa, por qué no, o que sería genial para la app.
-
-## Empezando pequeño
-
-Realmente quiero empezar pequeño, lanzando un Minimum Viable Product (MVP), con las siguientes funcionalidades:
-
-- Registro de usuarios y login
-- Dos tipos de usuarios, "peddlers" (vendedores ambulantes) y clientes
-- Peddlers
-  - Si el usuario es peddler (quiere vender), redireccionar al formulario de peddlers
-  - Peddlers pueden crear un perfil con el nombre de su empresa y productos que ofrece, por ejemplo helado, dulces, etc
-  - Una vez que el registro es finalizado, peddlers pueden iniciar rutas
-  - La app obtiene la ubicación del peddler, mostrándolo en el mapa
-  - El backend detectará si el peddler entra en el radio de un cliente, y enviará una notificación push al cliente
-  - Una vez que el peddler tiene una solicitud, la app mostrará la ubicación del cliente solicitante en el mapa
-  - El peddler puede ir a la ubicación, y completar la transacción
-- Clientes
-  - Clientes pueden crear una perfil con su nombre o alias, y registrar ubicaciones, por ejemplo: casa
-  - Una vez que un peddler está cerca, el backend enviará una notificación push al cliente
-  - El cliente toca y confirma la notificación
-
-Por supuesto, clientes pueden cambiar la configuración de las notificaciones, pero esa es la idea core.
-
-Para el MVP no quiero implementar pagos dentro de la app, pero desde luego, podría ser un feature futuro.

src/content/blog/es/rewind-2023-y-planes-futuros.mdx

@@ -1,19 +1,11 @@
 ---
 title: Rewind 2023 y Planes Futuros
 description: Mi rewind del 2023 y mis planes para el 2024 y más allá.
-tags: [Thoughts]
-image: /blog/rewind-2023-and-future-plans/banner.jpg
-imageCaption: Puesta de sol con un letrero, foto de Javier Allegue Barros en Unsplash
 date: 2023-12-16
 author: Juan Manzanero
 rss: true
 ---
 
-![Puesta de sol con un letrero](@/assets/blog/rewind-2023-and-future-plans/banner.jpg) _Foto de
-[Javier Allegue Barros](https://unsplash.com/@soymeraki?utm_content=creditCopyText&utm_medium=referral&utm_source=unsplash)
-en
-[Unsplash](https://unsplash.com/photos/silhouette-of-road-signage-during-golden-hour-C7B-ExXpOIE?utm_content=creditCopyText&utm_medium=referral&utm_source=unsplash)_
-
 Mi rewind del 2023 y mis planes para el 2024 y más allá.
 
 Espero que la estés pasando bien en estas fechas.

src/content/blog/es/una-mejor-forma-de-consumir-contenido.mdx

@@ -1,19 +1,11 @@
 ---
 title: Una Mejor Forma de Consumir Contenido
 description: Obtén tus noticias sin visitar websites con algoritmos que muestran contenido que no quieres ver.
-tags: [Tech]
-image: /blog/a-better-way-for-consuming-content/banner.webp
-imageCaption: Periódicos. Foto de Ashni en Unsplash
 date: 2024-4-11
 author: Juan Manzanero
 rss: true
 ---
 
-![Periódicos](@/assets/blog/a-better-way-for-consuming-content/banner.webp) _Foto de
-[Ashni](https://unsplash.com/@ashni_ahlawat?utm_content=creditCopyText&utm_medium=referral&utm_source=unsplash)
-en
-[Unsplash](https://unsplash.com/photos/text-ePWaAwUn80k?utm_content=creditCopyText&utm_medium=referral&utm_source=unsplash)_
-
 Obtén tus noticias sin visitar websites con algoritmos que muestran contenido que no quieres ver.
 
 ## Algoritmos que dictan lo que ves
@@ -67,10 +59,10 @@ mi opción favorita como ~~Pecador~~ usuario de Apple
 
 ### Agregando Feeds
 
-Ahora debes buscar por el link RSS de tu website favorito, ¡[como este](https://juancman.dev/es/rss.xml)!
+Ahora debes buscar por el link RSS de tu website favorito, ¡[como este](https://juanmanzanero.com/es/feed.xml)!
 
 ```
-https://juancman.dev/es/rss.xml
+https://juanmanzanero.com/es/feed.xml
 ```
 
 Si lo abres, verás una página rara con código similar a HTML.
@@ -102,7 +94,7 @@ https://youtube.com/feeds/videos.xml?channel_id=[CHANNEL ID]
 
 ### Mis Feeds Favoritos
 
-- [juancman.dev (¡obviamente!)](https://www.juancman.dev/es/rss.xml)
+- [juanmanzanero.com (¡obviamente!)](https://juanmanzanero.com/es/feed.xml)
 - [Astronomic Picture of the Day (apod)](https://apod.com/feed.rss)
 - [Earth Science Picture of the Day (epod)](https://feeds2.feedburner.com/EarthSciencePictureoftheDay)
 - [Erick Murphy](https://ericmurphy.xyz/index.xml)

src/content/blog/es/website-2.0.mdx

@@ -1,18 +1,12 @@
 ---
 title: La Razón para Crear una Versión 2.0 de mi Website
 description: Cometí algunos errores al crear la primera versión de mi sitio web, aquí compartiré lo que he aprendido.
-tags: [Tech]
-image: /blog/website-2.0/banner.png
-imageCaption: Tech Stack usado para este sitio web. Next.js, Vercel, React.js, TypeScript and TailwindCSS
 date: 2023-4-7
 author: Juan Manzanero
 rss: false
 draft: true
 ---
 
-![Tech stack](@/assets/blog/website-2.0/banner.png) _Tech Stack of this website.
-Next.js, Vercel, React.js, TypeScript and TailwindCSS_
-
 La primera versión de mi sitio web fue uno de mis mayores proyectos hasta ahora, pero ahora que tengo más experiencia como ingeniero Frontend, me doy cuenta de que no hice suficiente investigación para crear un sitio web con un blog.
 
 ---

src/content/blog/es/website-migrado-a-astro.mdx

@@ -1,17 +1,11 @@
 ---
 title: Website migrado a Astro
 description: Migré este website a Astro, de tal forma para probarlo, me terminó gustando.
-tags: [Astro]
-image: /portfolio/website-migrated-to-astro/banner.png
-imageCaption: Next Intl Blog Template banner
 date: 2024-6-26
 author: Juan Manzanero
 rss: true
 ---
 
-![Banner mostrando el tech stack](@/assets/portfolio/website-migrated-to-astro/banner.png)
-_Tech stack usado. Astro, React, TailwindCSS, MDX_
-
 Migré este website a Astro, de tal forma para probarlo, me terminó gustando.
 
 Probé esta herramienta para construir website estáticos, ya que Vercel ha estado tomando decisiones raras sobre la dirección del desarrollo de Next.js.

src/content/blog/es/workarise.mdx

@@ -1,40 +0,0 @@
----
-title: Workarise
-description: Workarise Web App, administra tareas con tu equipo.
-tags: [React.js, Vite.js, MUI, Firebase, GCP, Node.js]
-image: /portfolio/workarise/banner.png
-imageCaption: Workarise Banner
-date: 2023-4-13
-author: Juan Manzanero
-rss: true
----
-
-![Workarise Banner](@/assets/portfolio/workarise/banner.png) _Workarise Banner_
-
-[Website](https://workarise.com)
-
-## Descripción General
-
-[Workarise](https://workarise.com) es un Software como Servicio para administrar equipos mediante task cards asignadas a personas, establece una fecha de inicio y final, agregar archivos, etc.
-
-Puedes usar el Calendario para ver las fechas de entrega de las tareas y agendar eventos de Google Meet autorizando el uso de tu Google Calendar. Puedes editar y borrar eventos los cuales se sincronizan con tu Google Calendar y el de los invitados. El Gantt te provee con una línea del tiempo para ver la duración de las tareas.
-
-La web app está desarrollada con [React.js](https://react.dev/), usando [Vite.js](https://vitejs.dev/) para correr el entorno de desarrollo. Para funcionalidades como modals y popovers usamos [MUI](https://mui.com/). Para manejar el estado de los componentes usamos useContext.
-
-Para crear eventos Google Meet y sincronizar el calendario hemos desarrollado una pequeña API con Node.js para usar la API de Google OAuth 2, ya que necesitamos pedir permiso para acceder al Google Calendar del user.
-
-Actualmente, Workarise está en su primera versión, usando [Firebase](https://firebase.google.com/) para autenticar a los users, guardar datos y archivos. Firebase utiliza [Firestore](https://firebase.google.com/docs/firestore), una Base de Datos NoSQL, sin embargo estamos desarrollando una API con [Django](https://www.djangoproject.com/) corriendo en [Cloud Run](https://cloud.google.com/run)) conectado a [Cloud SQL](https://cloud.google.com/sql) a una instancia MySQL, ya que usaremos una Base de Datos SQL en el futuro. Actualmente la web app y la landing están desplegadas en Firebase Hosting, pero moveremos la landing a Vercel, y será actualizada a Next.js in el futuro para optimizar el SEO y publicar blog posts.
-
-## Mi impacto en Workarise
-
-Actualmente, estamos desarrollando un MVP, y todos estamos a tiempo parcial en este proyecto. Me uní en Diciembre, pero antes no había un producto que los users pudieran usar, y como era el único Ingeniero Frontend en ese momento tomé toda la responsabilidad de entregar algo que pudiera considerarse un MVP.
-
-Me tomó alrededor de 3 meses para conseguir eso, actualicé algunas de las dependencias del proyecto para mejorar el flujo de desarrollo, y sugerí usar Firebase como Backend y Hosting.
-
-Gracias a todo esto obtuvimos nuestros primeros users y feedback, así que ahora estamos trabajando con ese feedback para mantener mejorando nuestra app, ¡a nuestros users les gusta el diseño y la simplicidad!
-
-Ahora mismo hay 3 engineers en el equipo, 2 en el front (incluyéndome) y 1 en el back, pero estoy ayudando a nuestra Backend Engineer para desplegar en GCP a producción la API y Base de Datos, y estoy guiando al nuevo Frontend Engineer para entregar nuevos features, él ha desarrollado el responsive design y algunos features que complementan las task cards.
-
-Estoy feliz de poner a prueba mis habilidades en este proyecto, no es fácil tomar más responsabilidad con menos de 2 años de experiencia laboral, y me ha ayudado a crecer mucho en estos meses.
-
-Incluso si el mercado no considera mis años como senior, creo que eso no importa tanto, lo único que importa es que puedas entender por qué usas código, para crear soluciones y alcanzar a las personas a través de sus computadoras.

src/content/pages/en/contact.mdx

@@ -13,18 +13,8 @@ Just change `[at]` for `@` and `[dot]` for `.`. This is for preventing web
 crawlers from getting my email:
 
 ```
-contact[at]juancman[dot]dev
+contact[at]juanmanzanero[dot]com
 ```
 
-You may [download my PGP key](/publickey.contact@juancman.dev-80e0fe0b452a2fb48511be1b9fb094f3c57bae57.asc) to validate my emails.
+You may [download my PGP key](/publickey.contact@juanmanzanero.com-bc93bba27f657fc49730741013ec4a1443f077a9.asc) to validate my emails.
 
-## Social media
-
-If you want to talk about contracting me, you may check my career:
-
-- [LinkedIn](https://www.linkedin.com/in/juancmandev)
-
-You may check my GitHub, but I have also my own Gitea instance:
-
-- [GitHub](https://github.com/juancmandev)
-- [Gitea](https://git.juancman.dev/juancmandev)

src/content/pages/es/contacto.mdx

@@ -13,18 +13,7 @@ Solo cambia `[at]` por `@` y `[dot]` por `.`. Esto es para evitar que web
 crawlers obtengan mi email.
 
 ```
-contact[at]juancman[dot]dev
+contact[at]juanmanzanero[dot]com
 ```
 
-Puedes [descargar mi PGP key](/publickey.contact@juancman.dev-80e0fe0b452a2fb48511be1b9fb094f3c57bae57.asc) para validar mis emails.
-
-## Redes sociales
-
-Si quieres hablar sobre contratarme, puedes revisar mi carrera:
-
-- [LinkedIn](https://www.linkedin.com/in/juancmandev)
-
-Puedes revisar mi GitHub, aunque igual tengo mi propia instancia de Gitea:
-
-- [GitHub](https://github.com/juancmandev)
-- [Gitea](https://git.juancman.dev/juancmandev)
+Puedes [descargar mi PGP key](/publickey.contact@juanmanzanero.com-bc93bba27f657fc49730741013ec4a1443f077a9.asc) para validar mis emails.

src/content/videos/la-privacidad-en-la-era-actual.mdx

@@ -0,0 +1,164 @@
+---
+title: La Privacidad en la Era Actual
+description: En la era de los datos, estos mismos valen más de lo que crees.
+image: /blog/how-computers-works/banner.jpg
+imageCaption: Video thumbnail.
+date: 3/28/2025
+author: Juan Manzanero
+rss: true
+---
+
+Es dicícil hablar sobre privacidad en estos tiempos, ya que por lo general, la
+gente confunde este concepto con secretismo.
+
+> Si no estoy haciendo algo ilegal, ¿por qué querría ocultar lo que hago?
+
+Es lo que suelen responder, o sino, responden con:
+
+> Para que preocuparse si todos nuestros datos ya están expuestos
+
+O suelen responder con frases similares.
+
+Antes de indagar, es importante aclarar qué es privacidad y qué es secretismo.
+
+## Privacidad
+
+La privacidad es una necesidad y un derecho humano, todas las personas queremos
+privacidad para ciertas cosas.
+
+Por ejemplo, cuando vamos al baño solemos cerrar la puerta cuando hay otras
+personas.
+
+¿Para qué cerrar la puerta?, si todos sabemos que se hace en un baño.
+
+Aún así, sabemos que lidiar con nuestras necesidades es algo íntimo, y es por
+eso que necesitamos privacidad, no necesariamente debes hacer algo malo como
+para no querer hacerlo público.
+
+## Secretismo
+
+El secretismo es lo que muchas personas que cometen crímenes intentan hacer,
+mantener en secreto sus planes y movimientos.
+
+Pero no todos queremos cometer un crímen, simplemente queremos ejercer nuestro
+derecho a la privacidad.
+
+## La privacidad es un espectro
+
+Si realmente quieres mantener tu vida 100% privada, entonces no deberías usar
+Internet, ni vivir en una ciudad o pueblo.
+
+Pero no se trata de tener al 100% la privacidad, sino de tener hábitos para
+mantener un nivel de privacidad deseado.
+
+No es el mismo nivel de privacidad requerido por un periodista en un país donde
+la libertad de expresión no es prioridad (como México), al nivel de privacidad
+que probablemente tu necesitas, llevando una vida de menos riesgo.
+
+A esto se le conoce como _OpSec_ (Operation Security), y consiste en identificar
+qué información no queremos compatir y cómo reducir la cantidad de información
+que compartimos.
+
+Algo muy sencillo, sería no usar tu nombre real en una cuenta que has creado, o
+usar un email para el trabajo y otro para asuntos personales.
+
+Te apuesto que ya aplicas un nivel de OpSec en tu vida, pero incluso llevando
+una vida normal, puede no ser suficiente, aunque no hagas algo ilegal.
+
+## Tus datos son valiosos
+
+Personalmente no me gusta compartir mi número de celular, ya que constantemente
+me llega spam, desde publicidad hasta estafas.
+
+Cuando aplico a un trabajo y me piden mi número, pido por favor que toda
+comunicación sea por email, ya que en mi email tengo un mejor control sobre el
+spam, cosa que no es tan fácil hacer con un número de celular, aún activando el
+filtro de spam.
+
+Otro punto importante, es que el número de celular puede ser suplantado mediante
+SIM swap, en donde el perpetrador llama a la compañía de teléfono a la que
+pertenece tu número, se hace pasar por ti diciendo que le han robado el celular.
+
+Normalmente para que la compañía se asegure que eres tú, te hacen ciertas
+"preguntas de seguridad", como por ejemplo, cómo se llama tu mascota.
+
+Y si eres de esas personas que usan redes sociales como si fuese una
+autobiografía, pues esa información puede que la tenga el perpetrador.
+
+Con tu número podrían acceder a tus cuentas de banco, ya que por lo general para
+tener una cuenta bancaria se necesita un número de teléfono.
+
+Y ni hablemos de la autenticación por SMS, ya que ni siquiera están encriptados,
+por lo que cualquier persona podría leerlos sin problemas (esto incluye los
+mensajes enviados mediante _Messages_ de Apple).
+
+## La gente no se interesa, ya que se requiere algo de esfuerzo
+
+Hace tiempo Apple lanzó una actualización en iOS, en donde te aparece un pop-up,
+preguntándote si estás de acuerdo en que la app que usas acceda a información
+extra fuera de la app.
+
+No es de sorprenderse que la mayoría de las personas seleccionaban la opción que
+lo impedía.
+
+Y ese es el punto de la privacidad en esta época, que si fuera tan simple como
+seleccionar una opción, todos lo harían.
+
+Pero no es tan simple, se requiere desde investigar, hasta formar hábitos.
+
+Y es por eso que la mayoría de las personas se comportan de forma cínica o
+pesimista ante este tema.
+
+Es más fácil decir que te da igual que se sepa que tu perro se llama firulais, a
+formar hábitos, como no compartir toda tu vida en redes sociales.
+
+No necesitas de la noche a la mañana ya ejercer un nivel de OpSec alto, debe ser
+a tu ritmo y estar conciente, que **tus datos valen mucho**.
+
+Y en efecto, no es fácil, porque aumentando tu OpSec debes de dejar ir cierto
+nivel de conveniencia.
+
+Puedes empezar conociendo alternativas a las herramientas que ya usas.
+
+## Alternativas
+
+Por ejemplo, no es buena idea usar el mismo email para todas las cuentas que
+creas, pero es tedioso tener que crear un nuevo email cada vez que quieres
+registrarte en un website.
+
+Pero existe Software, como [SimpleLogin](https://simplelogin.io/), un Software
+Open Source con el que puedes crear email aliases que redireccionan a tu email
+principal, de esta forma manteniendo un email único para cada cuenta, pero
+teniendo todos tus emails en un mismo inbox.
+
+También es buena idea usar un email que no venda tus datos, como
+[ProtonMail](https://proton.me/mail), que si bien, no ofrecen la misma cantidad
+de almacenamiento como Gmail o Outlook, pero no escanean tus emails, y tus
+emails son encriptados.
+
+Otro buen paso es cambiando tu browser, ya que es lo que más usas en tu
+computadora.
+
+Ni Chrome ni Edge son buenas opciones, ya que es bien sabido que Google y
+Microsoft recolectan mucha información sobre ti.
+
+Como alternativas puedes probar [Brave](https://brave.com/), que es un browser
+en base Chromium al igual que Chrome y Edge, con un AdBlocker integrado y
+mejores opciones de privacidad implementadas por defecto.
+
+La otra alternativa para browsers es Firefox, pero últimamente Mozilla (la
+empresa que desarrolla Firefox) ha tomado una dirección cuestionable, pero la
+buena noticia es que existen alternativas en base a Firefox, como
+[LibreWolf](https://librewolf.net/), que es una versión de Firefox con un fuerte
+enfoque en la privacidad, y viene con uBlock Origin como add-on pre-instalado.
+
+En un futuro haré videos haciendo reviews de las miles de alternativas para apps
+del día al día, incluso hay unas que mejoran la experiencia, comenta de qué te
+gustaría que hable, así me ayudas a hackear el algoritmo de YouTube y este video
+será recomendado a más gente.
+
+Antes de irme quisiera citar esta frase de **Edward Snowden**:
+
+> Argumentar que no te importa la privacidad porque no tienes nada que ocultar
+> no es diferente de decir que no te importa la libertad de expresión porque no
+> tienes nada que decir.

src/content/videos/nadie-entiende-la-privacidad.mdx

@@ -1,184 +0,0 @@
----
-title: Nadie Entiende la Privacidad
-description: Hablar de privacidad es complicado, ya que muy pocos la entienden.
-tags:
-  - Tech
-  - Freedom
-  - Libre
-image: /blog/how-computers-works/banner.jpg
-imageCaption: Video thumbnail.
-date: 7/25/2024
-author: Juan Manzanero
-rss: true
----
-
-![Open laptop](@/assets/blog/how-computers-works/banner.jpg) _An open laptop.
-Photo by
-[Philipp Katzenberger](https://unsplash.com/@fantasyflip?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText')
-on
-[Unsplash](https://unsplash.com/photos/iIJrUoeRoCQ?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText)_
-
-## Lo que los normies dicen al escuchar "privacidad"
-
-"¿Por qué te interesa la privacidad?, ¿acaso haces algo ilegal?"
-
-"A mi no me interesa la privacidad, ni que tuviese algo que esconder."
-
-"De todas formas somos espiados, no vale la pena preocuparse por la privacidad."
-
-Estas son solo algunas de las respuestas más comunes cuando se menciona la
-palabra "privacidad", pero esto solo aplica en el ecosistema digital.
-
-## No es que tengas algo que ocultar, la privacidad es un derecho humano
-
-Curioso, porque la mayoria de las personas cuando vamos al baño, cerramos la
-puerta; son muy contadas las personas a las que permitiríamos entrar.
-
-¿Por qué?, digo, todos sabemos lo que se hace en un baño, pero aún así, es un
-espacio personal donde queremos estar a solas.
-
-Y es que de eso se trata la privacidad, es una necesidad humana, un derecho.
-
-La gente confunde privacidad con secretismo, creen que por querer ocultar algo,
-es porque sabemos que es malo.
-
-Pero ir al baño a satisfacer nuestras necesidas fisiológicas no es algo ilegal.
-
-Entonces, ¿por qué la gente en general es tan cínica con respecto a la
-privacidad?
-
-## La conveniencia de los servicios de las Big Tech a cambio de tus datos
-
-Bueno, no es sorpresa que la mayoría de estas personas son normies, gente que
-usa Windows/macOS en sus PCs, quienes usan todos los servicios "gratuitos" de
-Google, Facebook, Microsoft y Apple.
-
-Estas empresas, las conocidas como "Big Tech" no son organizaciones sin ánimos
-de lucro que crean servicios gratuitos, para nada.\_createMdxContent
-
-Al contrario, son de las empresas más poderosas que han existido en la historia
-de la humanidad, y su valor en la bolsa no deja de crecer.
-
-Y es simple, aunque puedas pagar por algunas funcionalidades premium en sus
-servicios, la realidad es que su verdadero producto eres **TÚ**, para ser más
-específico, tus datos.
-
-Google Chrome y Microsoft Edge no son gratuitos, recolectan tus datos para
-venderte anuncios personalizados.
-
-Tus fotos que guardas en Google Photos son analizadas por Google, pero dirás que
-no te tomas fotos sin ropa...
-
-## No hizo algo ilegal, pero fue castigado
-
-No necesariamente debes evitar subir ese tipo de fotos (sin prejuicios), prueba
-de ello está este caso de un padre de un bebé en San Francisco, California.
-
-En resumidas cuentas, un padre tomó fotos de los genitales de su hijo debido a
-un problema, se las envió a su doctor de confianza para que realizara un
-diagnóstico (esto fue durante la pandemia, en 2021).
-
-El problema fue que el padre tenía su celular con Android con el backup de fotos
-con Google Photos, y dicha foto fue subida a los servers de Google.
-
-Google desde luego tiene bots que analizan las fotos que son subidas para evitar
-almacenar cosas ilegales, como pornografía infantil, y es debido a esto que el
-padre fue flaggeado por el algoritmo de Google como un criminal.
-
-Su cuenta de Google fue deshabilitada, perdió acceso a su celular y a todos sus
-datos que tenía almacenados en los servicios de Google, y desde luego, Google
-notificó a la policía.
-
-Después del juicio, el jurado declaró que no se había cometido crimen alguno,
-pero Google se negó a restaurar el acceso a la cuenta del padre.
-
-Esta persona no tenía algo que esconder, y aún así fue castigado por una Big
-Tech, no solo prohibiendo acceso a su cuenta, sino incluso notificando a la
-policía.
-
-Y este es el problema cuando delegas tus fotos a una empresa que analiza cada
-imagen que subes, estás a la merced de los "Términos y Condiciones", o en este
-caso, a la interpretación de un bot de los Términos y Condiciones.
-
-Desde luego, nadie quiere que usen los servers de Google para guardar contenido
-ilegal, pero estas medidas terminan afectando a personas que no cometieron un
-crimen.
-
-## Preocuparse por la privacidad es como preocuparse por tu salud, poco a poco antes que sea demasiado tarde
-
-Lo sé, comenzar a preocuparse por la privacidad es intimidante, ya que es un
-tema en el que hay que indagar bastante, ya que la mayoría de las personas son
-muy ignorantes al respecto, pero no es necesario formatear todos tus drivers y
-comenzar a usar alguna distro de Linux enfocada en privacidad desde el día cero.
-Puedes comenzar dando pequeños pasos.
-
-Este tema no es uno de blanco y negro, de ignorancia total o absoluta paranoia,
-es más bien un espectro, en donde puedes situarte poco a poco más del lado de la
-privacidad, pero sin llegar a ser extremista.
-
-## Primeros pasos y alternativas
-
-Por ejemplo, comienza cambiando tu navegador de Internet, en lugar de Chrome o
-Edge, podrías usar Brave, o mejor aún, Firefox con un User.js como BetterFox,
-otra alternativa es LibreWolf, un fork de Firefox con mejoras en seguridad y
-privacidad.
-
-Igual lo ideal es que no uses el gestor de contraseñas que viene por defecto en
-tu navegador, lo ideal es que uses uno independiente como Bitwarden o Proton
-Pass, estos cuentan con add-ons para navegadores basados en Chrome y Firefox.
-
-De igual manera un gran paso que puedes tomar es cambiando tu email en lugar de
-utilizar Outlook o Gmail, una buena alternativa es Proton Mail.
-
-A su vez, intenta usar menos redes sociales, o como mínimo no compartas lo que
-estás haciendo en ese momento, ya que puedes revelar información que no te
-gustaría que sea usada en tu contra.
-
-## Sigue así
-
-Una vez que hayas tomados estos primeros pasos, lo ideal es que liberes por
-completo tus dispositivos.
-
-En tu computadora para empezar, instalando alguna distro de Linux, una muy buena
-para gente novata en Linux es Linux Mint, basada en una de las distros más
-populares (Ubuntu) pero sin las malas decisiones que ha implementado Canonical
-(la empresa detrás de Ubuntu).
-
-De igual manera tu celular es un dispositivo muy delicado, y desafortunadamente
-difícil de liberar.
-
-Para empezar, si usas un iPhone, lo mejor que podrías hacer es jailbreakearlo,
-pero no es muy viable usar un iPhone si lo que te preocupa es la privacidad.
-
-Y sí, Apple profesa mucho que los iPhones son seguros, pero eso es mentira
-(hablaré más de esto en el futuro).
-
-El dispositivo ideal sería un Android, en específico un Google Pixel reciente,
-ya que estos se pueden instalar un Custom ROM de Android, una buena opción es
-GrapheneOS.
-
-Repito, no hace falta que tomes todos estos pasos de una, puedes ir poco a poco.
-
-## No caigas en la trampa del cinismo o el pesimismo
-
-Pero dirás: "las empresas ya tienen mis datos, de nada me sirve preocuparme
-ahora".
-
-Eso es una estupidez, es como que alguien venga a golpearte y tu no te defiendas
-ya que ya te golpearon; no, lo primero que haces es defenderte.
-
-De eso se trata la privacidad hoy en día, es un tema de defensa de los derechos,
-no querer ocultar actividades ilegales.
-
-Curiosamente, los políticos se preocupan más por su privacidad, y no
-necesariamente para ocultar sus obras de caridad, pero el gobierno es quien más
-va a querer restar bloqueos para poder espiar a sus ciudadanos, tal es el caso
-de Estados Unidos, o en casos más extremos; China y Corea del Norte.
-
-En fin, espero que con este video pienses dos veces cuando escuches a un normie
-que no tiene nada que esconder, con lo cual puedes responder "si bien no tengo
-algo que esconder, tampoco tengo algo en particular que quiera compartir
-contigo".
-
-No permitas que 1984 de George Orwell pase de ser ciencia ficción a una
-predicción del futuro.

src/layouts/Layout.astro

@@ -3,7 +3,7 @@ import Header from '@/components/header.astro';
 import Navigation from '@/components/navigation';
 import Footer from '@/components/footer';
 import { getLangFromUrl } from '@/i18n/utils';
-import '@/styles/globals.css';
+import '@/styles/global.css';
 
 interface Props {
   title: string;
@@ -35,7 +35,7 @@ const { title, description } = Astro.props;
       lang === 'en' && (
         <link
           rel='alternate'
-          title='juancmandev'
+          title='Juan Manzanero'
           type='application/rss+xml'
           href={new URL('feed.xml', Astro.site)}
         />
@@ -45,7 +45,7 @@ const { title, description } = Astro.props;
       lang === 'es' && (
         <link
           rel='alternate'
-          title='juancmandev'
+          title='Juan Manzanero'
           type='application/rss+xml'
           href={new URL('feed.xml', `${Astro.site}/es/`)}
         />

src/pages/es/feed.xml.ts

@@ -10,7 +10,7 @@ import type { ImageMetadata } from 'astro';
 const markdownParser = new MarkdownIt();
 
 const imagesBlog = import.meta.glob<{ default: ImageMetadata }>(
-  '/src/assets/blog/**/**/*.{jpeg,jpg,png,gif,webp}'
+  '/src/assets/blog/**/*.{jpeg,jpg,png,gif,webp}'
 );
 
 export async function GET(context: any) {
@@ -59,6 +59,7 @@ export async function GET(context: any) {
       title: post.data.title,
       pubDate: post.data.date,
       description: post.data.description,
+      author: post.data.author || 'Juan Manzanero',
       link: `/blog/${post.id.split('.')[0]}/`,
       content: sanitizeHtml(html.toString(), {
         allowedTags: sanitizeHtml.defaults.allowedTags.concat(['img']),
@@ -68,17 +69,17 @@ export async function GET(context: any) {
 
   return rss({
     xmlns: { atom: 'http://www.w3.org/2005/Atom' },
-    title: 'juancmandev',
+    title: 'Juan Manzanero',
     description: 'Bienvenido a mi dominio, extraño.',
     site: `${context.site}es/`,
     customData: [
       '<language>es-mx</language>',
       `<image>
-          <url>https://juancman.dev/logo.png</url>
-          <title>juancmandev</title>
-          <link>https://juancman.dev</link>
+          <url>${context.site}/logo.png</url>
+          <title>Juan Manzanero</title>
+          <link>${context.site}</link>
       </image>`,
-      `<atom:link href="${context.site}es/feed.xml" rel="self" type="application/rss+xml"/>`,
+      `<atom:link href="${context.site}/es/feed.xml" rel="self" type="application/rss+xml"/>`,
     ].join(''),
     items,
     trailingSlash: false,

src/pages/es/index.astro

@@ -7,9 +7,9 @@ import { sortContentByDate } from '@/utils/sorts';
 import { getCollection } from 'astro:content';
 
 const pageData = {
-  title: 'juancmandev',
+  title: 'Juan Manzanero',
   description:
-    'Bienvenido a mi dominio, extraño. Soy juancmandev; Desarrollador Web, entusiasta de Linux, y defensor de la privacidad.',
+    'Bienvenido a mi dominio, extraño. Soy Juan Manzanero; Desarrollador Web, entusiasta de Linux, y defensor de la privacidad.',
 };
 
 const allPosts = await getCollection('blog', ({ data }) => data.draft !== true);
@@ -33,7 +33,7 @@ const lang = getLangFromUrl(Astro.url);
   <div class='prose prose-invert max-w-3xl mx-auto'>
     <h1 class='text-primary'>Bienvenido a mi dominio, extraño.</h1>
     <p>
-      Soy <strong class='text-primary'>juancmandev</strong>; <strong
+      Soy <strong class='text-primary'>Juan Manzanero</strong>; <strong
         >Desarrollador Web</strong
       >, entusiasta de <strong>Linux</strong> y defensor de la <strong
         >privacidad.</strong

src/pages/feed.xml.ts

@@ -10,7 +10,7 @@ import type { ImageMetadata } from 'astro';
 const markdownParser = new MarkdownIt();
 
 const imagesBlog = import.meta.glob<{ default: ImageMetadata }>(
-  '/src/assets/blog/**/**/*.{jpeg,jpg,png,gif,webp}'
+  '/src/assets/blog/**/*.{jpeg,jpg,png,gif,webp}'
 );
 
 export async function GET(context: any) {
@@ -59,6 +59,7 @@ export async function GET(context: any) {
       title: post.data.title,
       pubDate: post.data.date,
       description: post.data.description,
+      author: post.data.author || 'Juan Manzanero',
       link: `/blog/${post.id.split('.')[0]}/`,
       content: sanitizeHtml(html.toString(), {
         allowedTags: sanitizeHtml.defaults.allowedTags.concat(['img']),
@@ -68,17 +69,17 @@ export async function GET(context: any) {
 
   return rss({
     xmlns: { atom: 'http://www.w3.org/2005/Atom' },
-    title: 'juancmandev',
+    title: 'Juan Manzanero',
     description: 'Welcome to my domain, stranger.',
     site: context.site,
     customData: [
       '<language>en-us</language>',
       `<image>
-          <url>https://juancman.dev/logo.png</url>
-          <title>juancmandev</title>
-          <link>https://juancman.dev</link>
+          <url>${context.site}/logo.png</url>
+          <title>Juan Manzanero</title>
+          <link>${context.site}</link>
       </image>`,
-      `<atom:link href="${context.site}feed.xml" rel="self" type="application/rss+xml"/>`,
+      `<atom:link href="${context.site}/feed.xml" rel="self" type="application/rss+xml"/>`,
     ].join(''),
     items,
     trailingSlash: false,

src/pages/index.astro

@@ -7,9 +7,9 @@ import { getLangFromUrl } from '@/i18n/utils';
 import PostItemList from '@/components/post-items-list';
 
 const pageData = {
-  title: 'juancmandev',
+  title: 'Juan Manzanero',
   description:
-    'Welcome to my domain, stranger. I am juancmandev; Web Developer, Linux enthusiast, and privacy defender.',
+    'Welcome to my domain, stranger. I am Juan Manzanero; Web Developer, Linux enthusiast, and privacy defender.',
 };
 
 const allPosts = await getCollection('blog', ({ data }) => data.draft !== true);

src/pages/microblog.astro

@@ -3,7 +3,7 @@ import MicroblogItem from '@/components/microblog-item.astro';
 import Layout from '@/layouts/Layout.astro';
 import { createServerClient } from '@/utils/pocketbase';
 
-const pb = createServerClient('https://pb.juancman.dev/');
+const pb = createServerClient('https://pb.juanmanzanero.com/');
 const data = await pb.collection('microblogs').getFullList({
   expand: 'tags',
   sort: '-published',

src/pages/robots.txt.ts

@@ -4,7 +4,7 @@ const robotsTxt = `
 User-agent: *
 Allow: /
 
-Sitemap: ${new URL('sitemap-index.xml', 'https://juancman.dev').href}
+Sitemap: ${new URL('sitemap-index.xml', 'https://juanmanzanero.com').href}
 `.trim();
 
 export const GET: APIRoute = () => {

src/styles/global.css

@@ -0,0 +1,111 @@
+@import 'tailwindcss';
+
+@plugin 'tailwindcss-animate';
+@plugin '@tailwindcss/typography';
+
+@custom-variant dark (&:is(.dark *));
+
+@theme {
+  --font-*: initial;
+  --font-sans: Helvetica, Arial, sans-serif;
+
+  --color-border: #eee;
+  --color-input: #00adb5;
+  --color-ring: #00adb5;
+  --color-background: #222831;
+  --color-foreground: #eee;
+
+  --color-primary: #00adb5;
+  --color-primary-foreground: #000;
+
+  --color-secondary: #393e46;
+  --color-secondary-foreground: #eee;
+
+  --color-destructive: #ff2e63;
+  --color-destructive-foreground: #eee;
+
+  --color-muted: #393e46;
+  --color-muted-foreground: #eee;
+
+  --color-accent: #00adb5;
+  --color-accent-foreground: #eee;
+
+  --color-popover: #393e46;
+  --color-popover-foreground: #eee;
+
+  --color-card: #393e46;
+  --color-card-foreground: #eee;
+
+  --radius-lg: 8px;
+  --radius-md: 4px;
+  --radius-sm: 2px;
+}
+
+@utility container {
+  margin-inline: auto;
+  padding-inline: 2rem;
+  @media (width >= --theme(--breakpoint-sm)) {
+    max-width: none;
+  }
+  @media (width >= 1400px) {
+    max-width: 1400px;
+  }
+}
+
+/*
+  The default border color has changed to `currentColor` in Tailwind CSS v4,
+  so we've added these compatibility styles to make sure everything still
+  looks the same as it did with Tailwind CSS v3.
+
+  If we ever want to remove these styles, we need to add an explicit border
+  color utility to any element that depends on these defaults.
+*/
+@layer base {
+  *,
+  ::after,
+  ::before,
+  ::backdrop,
+  ::file-selector-button {
+    border-color: var(--color-gray-200, currentColor);
+  }
+}
+
+@layer base {
+  * {
+    @apply border-border;
+    scroll-margin-top: 60px;
+  }
+  body {
+    @apply bg-background text-foreground;
+  }
+  .prose {
+    @apply max-w-none;
+  }
+  li {
+    overflow-wrap: break-word
+  }
+  [data-rehype-pretty-code-figure] {
+    @apply bg-[#1e1e2e] rounded-md pt-4;
+  }
+  [data-rehype-pretty-code-figure] figcaption {
+    @apply m-0 mb-2 px-4 pb-4 border-b-[0.5px] border-secondary;
+  }
+  [data-rehype-pretty-code-figure] pre {
+    @apply py-3 px-4;
+  }
+  [data-rehype-pretty-code-figure] pre > code > span {
+    @apply pr-4;
+  }
+  [data-rehype-pretty-code-fragment] {
+    @apply relative my-5 rounded-md border border-border/20 bg-[#282c34];
+  }
+  code::after, code::before {
+    display: none;
+  }
+  .prose code {
+    @apply rounded-md border border-border/20 font-normal p-0.5 bg-secondary before:content-none after:content-none;
+  }
+  .prose pre > code {
+    @apply bg-transparent border-none;
+  }
+}

src/styles/globals.css

@@ -1,40 +0,0 @@
-@tailwind base;
-@tailwind components;
-@tailwind utilities;
-
-@layer base {
-  * {
-    @apply border-border;
-    scroll-margin-top: 60px;
-  }
-  body {
-    @apply bg-background text-foreground;
-  }
-  .prose {
-    @apply max-w-none;
-  }
-  li {
-    overflow-wrap: break-word
-  }
-  [data-rehype-pretty-code-figure] {
-    @apply bg-[#1e1e2e] rounded-md pt-4;
-  }
-  [data-rehype-pretty-code-figure] figcaption {
-    @apply m-0 mb-2 px-4 pb-4 border-b-[0.5px] border-secondary;
-  }
-  [data-rehype-pretty-code-figure] pre {
-    @apply py-3 px-4;
-  }
-  [data-rehype-pretty-code-figure] pre > code > span {
-    @apply pr-4;
-  }
-  [data-rehype-pretty-code-fragment] {
-    @apply relative my-5 rounded-md border border-border/20 bg-[#282c34];
-  }
-  .prose code {
-    @apply rounded-md border border-border/20 font-normal p-0.5 bg-secondary before:content-none after:content-none;
-  }
-  .prose pre > code {
-    @apply bg-transparent border-none;
-  }
-}

src/types/post-item.ts

@@ -1,6 +1,6 @@
 type TPostItem = {
   id: string;
-  date: Date | string;
+  date: Date | string | undefined;
   title: string;
   type: 'blog' | 'portfolio' | 'videos';
   lang: string;

src/utils/format-date.ts

@@ -27,7 +27,12 @@ const meses = [
   'Diciembre',
 ];
 
-export default function formatDate(date: Date | string, lang: string) {
+export default function formatDate(
+  date: Date | string | undefined,
+  lang: string
+) {
+  if (date === undefined) return '';
+
   const newDate = new Date(date);
   const month = months[newDate.getMonth()];
   const mes = meses[newDate.getMonth()];

tailwind.config.mjs

@@ -1,61 +0,0 @@
-/** @type {import('tailwindcss').Config} */
-module.exports = {
-  darkMode: ['class'],
-  content: ['./src/**/*.{astro,html,js,jsx,md,mdx,svelte,ts,tsx,vue}'],
-  prefix: '',
-  theme: {
-    fontFamily: {
-      sans: ['Helvetica', 'Arial', 'sans-serif'],
-    },
-    container: {
-      center: true,
-      padding: '2rem',
-      screens: {
-        '2xl': '1400px',
-      },
-    },
-    extend: {
-      colors: {
-        border: '#eee',
-        input: '#00adb5',
-        ring: '#00adb5',
-        background: '#222831',
-        foreground: '#eee',
-        primary: {
-          DEFAULT: '#00adb5',
-          foreground: '#000',
-        },
-        secondary: {
-          DEFAULT: '#393e46',
-          foreground: '#eee',
-        },
-        destructive: {
-          DEFAULT: '#ff2e63',
-          foreground: '#eee',
-        },
-        muted: {
-          DEFAULT: '#393e46',
-          foreground: '#eee',
-        },
-        accent: {
-          DEFAULT: '#00adb5',
-          foreground: '#eee',
-        },
-        popover: {
-          DEFAULT: '#393e46',
-          foreground: '#eee',
-        },
-        card: {
-          DEFAULT: '#393e46',
-          foreground: '#eee',
-        },
-      },
-      borderRadius: {
-        lg: '8px',
-        md: '4px',
-        sm: '2px',
-      },
-    },
-  },
-  plugins: [require('tailwindcss-animate'), require('@tailwindcss/typography')],
-};