<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Forem: Pamela Gilmour</title>
    <description>The latest articles on Forem by Pamela Gilmour (@pamgilmour).</description>
    <link>https://forem.com/pamgilmour</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F444072%2F4d115131-65b4-48a9-a4b4-8058ae085730.jpg</url>
      <title>Forem: Pamela Gilmour</title>
      <link>https://forem.com/pamgilmour</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/pamgilmour"/>
    <language>en</language>
    <item>
      <title>I Built a Fullstack App With Custom MCP Server Integration</title>
      <dc:creator>Pamela Gilmour</dc:creator>
      <pubDate>Thu, 05 Mar 2026 15:55:46 +0000</pubDate>
      <link>https://forem.com/pamgilmour/i-built-a-fullstack-app-with-custom-mcp-server-integration-98f</link>
      <guid>https://forem.com/pamgilmour/i-built-a-fullstack-app-with-custom-mcp-server-integration-98f</guid>
      <description>&lt;p&gt;I first heard of the model context protocol last year (I think? 😶‍🌫️) at a networking event and was eager to build something with it.&lt;/p&gt;

&lt;p&gt;I have previously built an mcp server prototype for public apis at my previous job and I recently ran into some downtime at work so I jumped at the chance of building something new and go deeper with my learning hoping to build another mcp tool.&lt;/p&gt;

&lt;p&gt;So I built this simple app as a learning project. It's essentially collects data the user give it and the chat bot uses the Anthropic Claude API to query the given data. It's not a terribly creative concept or interface but I definitely had a lot of fun putting it together.&lt;/p&gt;

&lt;p&gt;I recorded a demo of the flow which can be viewed on yt:&lt;br&gt;


  &lt;iframe src="https://www.youtube.com/embed/GdRVBWv2w8k"&gt;
  &lt;/iframe&gt;


&lt;/p&gt;

&lt;p&gt;It's also live here: &lt;a href="https://p-11-one.vercel.app/" rel="noopener noreferrer"&gt;https://p-11-one.vercel.app/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>learning</category>
      <category>showdev</category>
      <category>mcp</category>
    </item>
    <item>
      <title>Intake Form using React and Django</title>
      <dc:creator>Pamela Gilmour</dc:creator>
      <pubDate>Tue, 15 Sep 2020 03:47:45 +0000</pubDate>
      <link>https://forem.com/pamgilmour/intake-form-using-react-1hi8</link>
      <guid>https://forem.com/pamgilmour/intake-form-using-react-1hi8</guid>
      <description>&lt;p&gt;Links to deployed:&lt;br&gt;
frontend &lt;a href="https://virtualcharms.github.io/consult-app/" rel="noopener noreferrer"&gt;https://virtualcharms.github.io/consult-app/&lt;/a&gt;&lt;/p&gt;
&lt;h2&gt;
  
  
  Why?
&lt;/h2&gt;

&lt;p&gt;As our lives get increasingly productive, many people are not able to make time for themselves, and specifically, to keep up on healthcare appointments. A digital intake form would be useful for users who would rather fill out an intake form at home or on their own time and be able to receive results and treatment plans remotely.&lt;/p&gt;

&lt;p&gt;The pandemic and life in quarantine has seen the use of e-health and remote medicine skyrocket as a lifeline for both clients/patients and practitioners alike.&lt;/p&gt;

&lt;p&gt;Brief Demo:&lt;br&gt;
&lt;iframe src="https://player.vimeo.com/video/457968447" width="710" height="399"&gt;
&lt;/iframe&gt;
&lt;/p&gt;

&lt;p&gt;I got started on a digital intake form for an independent health practitioner or even as a liasion to an EHR, a.k.a: an electronic health record app or website.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Planning Process
&lt;/h2&gt;

&lt;p&gt;I came up with this idea as a practitioner myself, as a solution for my own practice, in order to keep in touch with my existing clients (we all have crazy schedules) and to inspire potential clients to try out a new method of client and practitioner interaction through this digital version.&lt;/p&gt;

&lt;p&gt;When I first plotted out the course of this project, I knew that it would be a grand undertaking so I broke it down into individual components and decided to tackle the most technical heavy aspect of the project. But looking back, this part of the project may have been the most challenging part of the project.  &lt;/p&gt;

&lt;h2&gt;
  
  
  App Features
&lt;/h2&gt;

&lt;p&gt;There are 2 main features of this project app:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;a backend (built with Django) that houses intake questions and potentially, protected client responses.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;a frontend (built with React) that displays questions brought in from the backend and that receives and saves the client’s responses from inputs.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Highs and Lows:
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Challenges
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Coming back to React after a few weeks away was a little scary but went well.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;This project was especially challenging for me. After my last several projects, I tried to try out something different this time and I definitely came up against far more road blocks.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Triumphs
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Returning to React was not as scary as I thought it would be and I was really excited to pick up Bootstrap for the first time with relative ease.&lt;/li&gt;
&lt;li&gt;Building the back-end with Django was chill. I did try out a new-to-me thing called enum as a choice field.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Things I would do differently
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;I think the biggest lesson learned from this project is that, when it comes to coding, things that seem straight forward are usually never straight forward. In the future I will prefer to err on over planning instead of getting stuck mid-project because of lack of planning.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Once I get thru this part of the app I will like to be able to add User Auth and get my app to be HIPPAA compliant!&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
    </item>
    <item>
      <title>My first React App</title>
      <dc:creator>Pamela Gilmour</dc:creator>
      <pubDate>Tue, 04 Aug 2020 16:49:54 +0000</pubDate>
      <link>https://forem.com/pamgilmour/my-first-react-app-pal</link>
      <guid>https://forem.com/pamgilmour/my-first-react-app-pal</guid>
      <description>&lt;p&gt;&lt;a href="https://vimeo.com/444606094" rel="noopener noreferrer"&gt;Project2v1&lt;/a&gt; from &lt;a href="https://vimeo.com/user120810422" rel="noopener noreferrer"&gt;Pamela Gilmour&lt;/a&gt; on &lt;a href="https://vimeo.com" rel="noopener noreferrer"&gt;Vimeo&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://virtualcharms-horoscope.herokuapp.com/" rel="noopener noreferrer"&gt;https://virtualcharms-horoscope.herokuapp.com/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;What is it?&lt;/p&gt;

&lt;p&gt;I am venturing into tech from holistic health and part of my job is to be knowledgeable of any healing modality that I come across. Astrology is a vast and deep field with a rich history. People for millennia have accessed astrology as well as countless other divination methods to improve their lives, enhance their luck and find love. Most of the astrologers I personally follow, their work is influenced by psychology at some level (usually either professional or academically). Today, astrology is becoming more and more prominent in pop-culture, no longer confined to one page at the back of a newspaper or magazine. I am seeing more and more horoscope apps and I love them all. It’s exciting for me to see these traditionally and inherently esoteric institutions merging with technology AND this is the very crux of my own creative work.  &lt;/p&gt;

&lt;p&gt;So as I was preparing for my second project, creating a React app that accesses an API, I went searching for an API that resonated with me. I found this delightful horoscope API (&lt;a href="http://ohmanda.com/api/horoscope/" rel="noopener noreferrer"&gt;http://ohmanda.com/api/horoscope/&lt;/a&gt;) in a google search, and got to coding my app.&lt;/p&gt;

&lt;p&gt;My Process:&lt;/p&gt;

&lt;p&gt;This was my second project so I incorporated my time-management lessons from my last project and first, actually looked at what my deadline was before I got emotionally invested. I created my own deadlines accordingly and wrote up a simple MVP that I thought would be achievable in the timeframe given.&lt;/p&gt;

&lt;p&gt;Features:&lt;/p&gt;

&lt;p&gt;My app is a simple horoscope app: It has a welcome greeting, a header so you know what you are looking at and a list of the zodiac signs in a colorful card-like layout, with an image and range of birthdates for each sign accordingly. So, in order to read your horoscope, you just click on the card of your Sun sign and VOILA! You get a horoscope message from the horoscope API! How cute!&lt;/p&gt;

&lt;p&gt;Lessons Learned:&lt;/p&gt;

&lt;p&gt;I was able to incorporate some basic CSS grid, with which I tried out several different layouts. I decided with a list format because it was the least awkward experience.&lt;/p&gt;

&lt;p&gt;With my first pass of code, I made a component for each zodiac sign, but decided that was not the best use of React and so went back and refactored my code to be simpler and more dynamic. CLEAN &amp;amp; DRY!&lt;/p&gt;

&lt;p&gt;Stretch Goals:&lt;br&gt;
Now that I have the beginnings of a hip, bright, and colorful horoscope app, on a free weekend in the future, I will be replacing the images with those that I will have illustrated myself (&lt;a href="https://virtualcharms.github.io/fortune-click/" rel="noopener noreferrer"&gt;https://virtualcharms.github.io/fortune-click/&lt;/a&gt;), optimizing load speed, thinking up more features to make the page more interactive and informative and maybe even playing with the layout more.&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
