Interim commit; content work
- Changed most instances of DJS Consulting to Bit Badger Solutions - Split home page out into separate pages to make it shorter / easier to read - Added myPrayerJournal to the list of applications - Lots of content editing, link fixing, and some new content
This commit is contained in:
parent
ecfd96e2bc
commit
0918c272b0
@ -72,6 +72,9 @@ p {
|
||||
.content {
|
||||
font-size: 1.1rem;
|
||||
}
|
||||
.auto {
|
||||
margin: 0 auto;
|
||||
}
|
||||
@media all and (min-width: 68rem) {
|
||||
.content {
|
||||
width: 66rem;
|
||||
|
@ -43,7 +43,7 @@ const APPS = [
|
||||
},
|
||||
{
|
||||
heading: 'What We Still Do',
|
||||
narrative: 'DJS Consulting hosts this site; we also publish sermons to their podcast feed weekly.'
|
||||
narrative: 'Bit Badger Solutions hosts this site; we also publish sermons to their podcast feed weekly.'
|
||||
}
|
||||
]
|
||||
},
|
||||
@ -71,7 +71,7 @@ const APPS = [
|
||||
heading: 'What We Did (2012)',
|
||||
narrative: `In July 2012, we began hosting the site, as well as continuing support for theme updates. This
|
||||
joined her military wife blog
|
||||
<a href="/applications/hard-corps-wife" title="Hard Corps Wife • DJS Consulting">Hard Corps
|
||||
<a href="/solutions/hard-corps-wife" title="Hard Corps Wife • DJS Consulting">Hard Corps
|
||||
Wife</a>, which we had begun hosting in mid-2011.`
|
||||
},
|
||||
{
|
||||
@ -111,8 +111,8 @@ const APPS = [
|
||||
indexText: 'Politics, health, podcasts and more',
|
||||
paragraphs: [
|
||||
`Dr. Melissa Clouthier saw our work with
|
||||
<a href="/applications/cassy-fiano" title="Cassy Fiano • DJS Consulting">Cassy</a>’s site, and asked
|
||||
us to help her move off Blogger as well. Melissa blogs from the political right, but also covers health issues and
|
||||
<a href="/solutions/cassy-fiano" title="Cassy Fiano | Bit Badger Solutions">Cassy</a>’s site, and asked us
|
||||
to help her move off Blogger as well. Melissa blogs from the political right, but also covers health issues and
|
||||
social media. She had been blogging for a several years, and wanted to bring her old content with her to her new
|
||||
site.`
|
||||
],
|
||||
@ -125,12 +125,12 @@ const APPS = [
|
||||
},
|
||||
{
|
||||
heading: 'What We Still Do',
|
||||
narrative: 'DJS Consulting continues to provide WordPress upgrades, backups, and theme tweaks.'
|
||||
narrative: 'Bit Badger Solutions continues to provide WordPress upgrades, backups, and theme tweaks.'
|
||||
}
|
||||
],
|
||||
footnotes: [
|
||||
`<em>(NOTE: The thumbnail of the site represents a new skin on the original theme; while the theme is the same,
|
||||
DJS Consulting did not create the graphics.)</em>`
|
||||
Bit Badger Solutions did not create the graphics.)</em>`
|
||||
]
|
||||
},
|
||||
{
|
||||
@ -193,14 +193,14 @@ const APPS = [
|
||||
},
|
||||
{
|
||||
heading: 'What We Still Do',
|
||||
narrative: `DJS Consulting still hosts Futility Closet, ensuring that the underlying server receives performance
|
||||
and security upgrades, monitoring site performance, and maintaining regular backups.`
|
||||
narrative: `Bit Badger Solutions still hosts Futility Closet, ensuring that the underlying server receives
|
||||
performance and security upgrades, monitoring site performance, and maintaining regular backups.`
|
||||
}
|
||||
],
|
||||
quotes: {
|
||||
name: 'Greg Ross',
|
||||
from: 'Futility Closet',
|
||||
full: `DJS Consulting has been an absolute godsend for Futility Closet. We have been with them since 2010,
|
||||
full: `Bit Badger Solutions has been an absolute godsend for Futility Closet. We have been with them since 2010,
|
||||
initially setting up and maintaining the site on a Rackspace VPS, and then hosting it completely.
|
||||
Daniel’s never failed in being friendly, knowledgeable, thoughtful, and farsighted. I’ve
|
||||
literally lost count of the number of times he’s saved us from one emergency or another, always with
|
||||
@ -269,22 +269,22 @@ const APPS = [
|
||||
},
|
||||
{
|
||||
heading: 'What We Still Do',
|
||||
narrative: `DJS Consulting maintained the server, keeping it current with performance and security upgrades. We
|
||||
also provided support to the primary 3 bloggers, when they had questions about WordPress or how the
|
||||
site was performing. The site closed in August of 2011, as the primary authors moved on to other
|
||||
endeavors.`
|
||||
narrative: `Bit Badger Solutions maintained the server, keeping it current with performance and security
|
||||
upgrades. We also provided support to the primary 3 bloggers, when they had questions about WordPress
|
||||
or how the site was performing. The site closed in August of 2011, as the primary authors moved on to
|
||||
other endeavors.`
|
||||
}
|
||||
]
|
||||
},
|
||||
{
|
||||
id: 'linux',
|
||||
name: 'Linux Resources',
|
||||
url: '//techblog.djs-consulting.com/linux/',
|
||||
url: 'https://blog.bitbadger.solutions/linux/',
|
||||
active: true,
|
||||
categoryId: 1,
|
||||
noAboutLink: true,
|
||||
frontPageText: 'Handy information for Linux folks',
|
||||
frontPageOrder: 2
|
||||
frontPageOrder: 3
|
||||
},
|
||||
{
|
||||
id: 'mindy-mackenzie',
|
||||
@ -316,6 +316,29 @@ const APPS = [
|
||||
}
|
||||
]
|
||||
},
|
||||
{
|
||||
id: 'my-prayer-journal',
|
||||
name: 'myPrayerJournal',
|
||||
url: 'https://prayerjournal.me',
|
||||
active: true,
|
||||
categoryId: 1,
|
||||
frontPageText: 'Minimalist personal prayer journal',
|
||||
frontPageOrder: 2,
|
||||
indexText: 'Minimalist personal prayer journal',
|
||||
paragraphs: [
|
||||
`to be written`
|
||||
],
|
||||
activity: [
|
||||
{
|
||||
heading: 'What We Did',
|
||||
narrative: 'Wrote it'
|
||||
},
|
||||
{
|
||||
heading: 'What We Still Do',
|
||||
narrative: 'Host it'
|
||||
}
|
||||
]
|
||||
},
|
||||
{
|
||||
id: 'nsx',
|
||||
name: 'Not So Extreme Makeover: Community Edition',
|
||||
@ -352,7 +375,7 @@ const APPS = [
|
||||
generated schedules and reports that were used to track the execution of the project.<br><br>
|
||||
After we recovered, Love INC expressed an interest in a version that would allow them to handle these
|
||||
same areas on an ongoing basis; this was the genesis of
|
||||
<a href="/applications/tcms" title="The Clearinghouse Management System • DJS Consulting">TCMS</a>.`
|
||||
<a href="/solutions/tcms" title="The Clearinghouse Management System | Bit Badger Solutions">TCMS</a>.`
|
||||
},
|
||||
{
|
||||
heading: 'What We Still Do',
|
||||
@ -373,7 +396,7 @@ const APPS = [
|
||||
indexText: 'Southern Baptist church in Gulfport, Mississippi',
|
||||
paragraphs: [
|
||||
`Olivet Baptist Church’s pastor saw our work with
|
||||
<a href="/applications/bay-vista" title="Bay Vista Baptist Church • DJS Consulting">Bay Vista</a>, and asked
|
||||
<a href="/solutions/bay-vista" title="Bay Vista Baptist Church | Bit Badger Solutions">Bay Vista</a>, and asked
|
||||
us what would be involved with setting up something similar for his church. Olivet did not currently have a
|
||||
website.`
|
||||
],
|
||||
@ -392,7 +415,7 @@ const APPS = [
|
||||
},
|
||||
{
|
||||
heading: 'What We Still Do',
|
||||
narrative: `DJS Consulting hosts this site; we also publish sermons to their podcast feed weekly.`
|
||||
narrative: `Bit Badger Solutions hosts this site; we also publish sermons to their podcast feed weekly.`
|
||||
}
|
||||
]
|
||||
},
|
||||
@ -405,10 +428,10 @@ const APPS = [
|
||||
categoryId: 1,
|
||||
indexText: 'Photography services in Albuquerque, New Mexico',
|
||||
paragraphs: [
|
||||
`Michelle Summers (yes, Daniel’s wife) had been photographing her children for years. When her sons were on
|
||||
sports teams, she was disappointed with the cost of team photography, and felt that she could do a better job at a
|
||||
lower cost. Thus was born Photography by Michelle. She specializes in outdoor photography of families, children,
|
||||
and sports teams, as well as maternity photography and holiday cards.`
|
||||
`Michelle Summers had been photographing her children for years. When her sons were on sports teams, she was
|
||||
disappointed with the cost of team photography, and felt that she could do a better job at a lower cost. Thus was
|
||||
born Photography by Michelle. She specializes in outdoor photography of families, children, and sports teams, as
|
||||
well as maternity photography and holiday cards.`
|
||||
],
|
||||
activity: [
|
||||
{
|
||||
@ -455,7 +478,7 @@ const APPS = [
|
||||
heading: 'What We Did (2011)',
|
||||
narrative: `We rewrote this application using ASP MVC 3 backed by a PostgreSQL database, building the security
|
||||
additions from the ground up, and posturing it for an interface with
|
||||
<a href="/applications/virtual-prayer-room" title="Virtual Prayer Room • DJS Consulting">Virtual
|
||||
<a href="/solutions/virtual-prayer-room" title="Virtual Prayer Room | Bit Badger Solutions">Virtual
|
||||
Prayer Room</a>.`
|
||||
},
|
||||
{
|
||||
@ -493,7 +516,7 @@ const APPS = [
|
||||
},
|
||||
{
|
||||
heading: 'What We Still Do',
|
||||
narrative: `DJS Consulting continues to provide backups and WordPress updates for Riehl World News.`
|
||||
narrative: `Bit Badger Solutions continues to provide backups and WordPress updates for Riehl World News.`
|
||||
}
|
||||
]
|
||||
},
|
||||
@ -510,40 +533,40 @@ const APPS = [
|
||||
must be tracked, along with their needs; these needs must be verified; resources for goods and services must be
|
||||
known; volunteers must be known and sent communications to keep them involved. All of this adds up to a
|
||||
significant recordkeeping (i.e., paperwork) burden.`,
|
||||
`TCMS addresses these issues by providing a repository for all clearinghouse operation needs. It can eliminate
|
||||
duplication of work, as well as link clients with goods and services. It also provides the means to communicate
|
||||
with volunteers, either en masse or using selective criteria. This allows the recordkeeping requirement to be
|
||||
smaller and quicker, giving more time for the actual helping of clients. It uses WordPress for its front end; this
|
||||
can provide organizations with a web presence that they can maintain without having to employ a web guru, using
|
||||
`TCMS addressed these issues by providing a repository for all clearinghouse operation needs. It helped eliminate
|
||||
duplication of work, and also linke clients with goods and services. It also provided the means to communicate
|
||||
with volunteers, either en masse or using selective criteria. This allowed the recordkeeping requirement to be
|
||||
smaller and quicker, giving more time for the actual helping of clients. It used WordPress for its front end; this
|
||||
provided organizations with a web presence that they could maintain without having to employ a web guru, using
|
||||
WordPress’s <abbr title="What You See Is What You Get">WYSIWYG</abbr> editor and management tools.`,
|
||||
`TCMS was decommissioned in 2014.`
|
||||
]
|
||||
},
|
||||
{
|
||||
id: 'tech-blog',
|
||||
name: 'DJS Consulting Tech Blog',
|
||||
url: 'https://techblog.djs-consulting.com',
|
||||
name: 'The Bit Badger Blog',
|
||||
url: 'https://blog.bitbadger.solutions',
|
||||
active: true,
|
||||
categoryId: 3,
|
||||
frontPageText: 'Technical information (AKA “geek stuff”) from DJS Consulting',
|
||||
frontPageText: 'Technical information (“geek stuff”) from Bit Badger Solutions',
|
||||
frontPageOrder: 3,
|
||||
indexText: 'Geek stuff from DJS Consulting',
|
||||
indexText: 'Geek stuff from Bit Badger Solutions',
|
||||
paragraphs: [
|
||||
`The DJS Consulting Tech Blog grew from Daniel’s personal experience with learning and using the Linux
|
||||
operating system. His first experience with blogging consisted of pages that had to be edited every time a new
|
||||
post was made. The initial posts were titled “My Linux Adventure,” and existed as a copy of this
|
||||
home-grown blog. The DJS Consulting Tech Blog has that, plus tech tips regarding many different computer
|
||||
products. It covers web servers, databases, programming languages (a lot of PHP), and open-source software. DJS
|
||||
Consulting also hosts 64-bit RPM builds of xine, a Linux multimedia player; the tech blog, via the RSS feed for
|
||||
that category, can deliver notices of updated versions directly to subscribed users. Finally, it also contains
|
||||
notices of new versions of DJS Consulting-developed WordPress plug-ins (“Daniel’s Dropdowns”
|
||||
<em>(inactive, as its functionality is now part of the WordPress core)</em> and “HCSB Verse of the Day
|
||||
(Plus)”).`,
|
||||
`The Bit Badger Blog grew from Daniel’s personal experience with learning and using the Linux operating
|
||||
system. His first experience with blogging consisted of pages that had to be edited every time a new post was
|
||||
made. The initial posts were titled “My Linux Adventure,” and existed as a copy of this home-grown
|
||||
blog. The Bit Badger Blog has that, plus tech tips regarding many different computer products. It covers web
|
||||
servers, databases, programming languages, and open-source software. Bit Badger Solutions also hosts 64-bit RPM
|
||||
builds of xine, a Linux multimedia player; the blog, via the RSS feed for that category, can deliver notices of
|
||||
updated versions directly to subscribed users. Finally, it also contains notices of new versions of Bit Badger
|
||||
Solutions-developed WordPress plug-ins (“Daniel’s Dropdowns” <em>(inactive, as its functionality
|
||||
is now part of the WordPress core)</em> and “HCSB Verse of the Day (Plus)”).`,
|
||||
`The original theme, “Almost Spring,” started as a pastel green and orange theme for WordPress.
|
||||
However, it was customized to match the original look and feel of those initial static pages that served as the
|
||||
blog from 2004-2006, and was converted to a BlogEngine.NET theme when we changed blogging platforms. When we went
|
||||
back to WordPress, we changed to a simple theme called “Mantra,” which has unobtrusive social media
|
||||
integration.`
|
||||
integration. It is now a statically-generated site, utilizing <a href="https://hexo.io">Hexo</a>, and its code is
|
||||
<a href="https://github.com/danieljsummers/blog.bitbadger.solutions">open source</a>.`
|
||||
]
|
||||
},
|
||||
{
|
||||
@ -576,21 +599,21 @@ const APPS = [
|
||||
categoryId: 1,
|
||||
indexText: 'Gives prayer warriors access to requests from wherever they may be, and sends them daily updates',
|
||||
paragraphs: [
|
||||
`Many churches have prayer rooms - rooms set aside for people to come in to pray. Hoffmantown Church in
|
||||
`Many churches have prayer rooms – rooms set aside for people to come in to pray. Hoffmantown Church in
|
||||
Albuquerque, New Mexico was one of these churches. However, they had seen the use of this physical prayer room
|
||||
dwindling over the years. People had become less willing to drive to the church, especially at night, and security
|
||||
became an issue as well; either prayer warriors had to know how to disable the security system, or the church
|
||||
would have to remain unlocked.`,
|
||||
`Having seen our work with the
|
||||
<a href="/applications/nsx/" title="Not So Extreme Makeover: Community Edition • DJS Consulting">Not So
|
||||
Extreme Makeover: Community Edition</a>, the church contacted us to see if something similar could be developed to
|
||||
help their prayer ministry. The resulting application that was developed extends the prayer room to wherever the
|
||||
prayer warrior can get an Internet connection! Prayer warriors can enlist right from the site, and must be
|
||||
approved. Requests and updates are tracked by date/time, and warriors can record when they’ve prayed for a
|
||||
request from the site, or from clicking a link in the daily e-mail they receive with requests from their interest
|
||||
areas. As many prayer needs are confidential, security and confidentiality are very important. Virtual Prayer Room
|
||||
ensures these by providing varying security levels for prayer warriors and the ability to mark each request as
|
||||
confidential.`,
|
||||
<a href="/solutions/nsx/" title="Not So Extreme Makeover: Community Edition | Bit Badger Solutions">Not So Extreme
|
||||
Makeover: Community Edition</a>, the church contacted us to see if something similar could be developed to help
|
||||
their prayer ministry. The resulting application that was developed extended the prayer room to wherever the
|
||||
prayer warrior can get an Internet connection! Prayer warriors could enlist right from the site, and had to be
|
||||
approved. Requests and updates were tracked by date/time, and warriors could record when they’ve prayed for
|
||||
a request from the site, or from clicking a link in the daily e-mail they received with requests from their
|
||||
interest areas. As many prayer needs are confidential, security and confidentiality were very important. Virtual
|
||||
Prayer Room ensured these by providing varying security levels for prayer warriors and the ability to mark each
|
||||
request as confidential.`,
|
||||
`In 2016, Hoffmantown Church elected to begin using another package for their prayer requests. While a few other
|
||||
churches had expressed interest in it, none ultimately decided to use it; so, in 2017, Virtual Prayer Room was
|
||||
officially decommissioned.`
|
||||
|
@ -1,11 +1,11 @@
|
||||
<template lang="pug">
|
||||
article
|
||||
page-title(title='All Solutions')
|
||||
h1 All Solutions
|
||||
h2 Active Solutions
|
||||
application-list-item(v-for='app in current' :app='app' :key='app.id')
|
||||
h2 Past Solutions
|
||||
application-list-item(v-for='app in past' :app='app' :key='app.id')
|
||||
article.content.auto
|
||||
page-title(title='All Solutions')
|
||||
h1 All Solutions
|
||||
h2 Active Solutions
|
||||
application-list-item(v-for='app in current' :app='app' :key='app.id')
|
||||
h2 Past Solutions
|
||||
application-list-item(v-for='app in past' :app='app' :key='app.id')
|
||||
</template>
|
||||
|
||||
<script>
|
||||
|
@ -1,39 +1,34 @@
|
||||
<template lang="pug">
|
||||
article
|
||||
page-title(title='Not Found (404)')
|
||||
h1 Not Found (404)
|
||||
p.
|
||||
Looks like you've stumbled into the part of this site where we have no content to give you. Of course, you could
|
||||
have hit an actual link that we moved, but missed setting up redirection for it. If that is the case, one of the
|
||||
links below may be what you need.
|
||||
ul
|
||||
li.
|
||||
The #[strong Linux Software Repository] used to be at #[tt /linux/software], but can now be found at
|
||||
#[a(href='https://hosted.djs-consulting.com/software') https://hosted.djs-consulting.com/software]. This
|
||||
includes the OpenSUSE ISOs, SQLDeveloper .deb packages, and Xine RPMs.
|
||||
li.
|
||||
The #[strong My Linux Adventure] and #[strong DJS Consulting Tech Blog] blogs used to be at #[tt /linux/blog],
|
||||
but both have been combined into the latter, and can be found at
|
||||
#[a(href='https://techblog.djs-consulting.com') https://techblog.djs-consulting.com].
|
||||
li.
|
||||
#[strong Kathie York]'s portfolio, formerly at #[tt /hosted/kathieyork], is now at
|
||||
#[a(href='https://hosted.djs-consulting.com/kathieyork') https://hosted.djs-consulting.com/kathieyork].
|
||||
li.
|
||||
#[strong Daniel J. Summers]'s personal site, formerly at #[tt /personal] (and a really ancient copy at
|
||||
#[tt /old_personal]), is now at #[a(href='https://daniel.summershome.org') https://daniel.summershome.org].
|
||||
li.
|
||||
The #[strong Not So Extreme Makeover: Community Edition] archive site, previously at
|
||||
#[tt /archived/notsoextreme_org], can now be found at
|
||||
#[a(href='https://hosted.djs-consulting.com/archive/notsoextreme_org') https://hosted.djs-consulting.com/archive/notsoextreme_org].
|
||||
article.content.auto
|
||||
page-title(title='Not Found (404)')
|
||||
h1 Not Found (404)
|
||||
p.
|
||||
Looks like you've stumbled into the part of this site where we have no content to give you. Of course, you could
|
||||
have hit an actual link that we moved, but missed setting up redirection for it. If that is the case, one of the
|
||||
links below may be what you need.
|
||||
ul
|
||||
li: p.
|
||||
The #[strong Linux Software Repository] used to be at #[tt /linux/software], but can now be found at
|
||||
#[a(href='https://hosted.djs-consulting.com/software') https://hosted.djs-consulting.com/software]. This
|
||||
includes the OpenSUSE ISOs, SQLDeveloper .deb packages, and Xine RPMs.
|
||||
li: p.
|
||||
The #[strong My Linux Adventure] and #[strong DJS Consulting Tech Blog] blogs used to be at #[tt /linux/blog],
|
||||
but both have been combined into #[em The Bit Badger Blog], which can be found at
|
||||
#[a(href='https://blog.bitbadger.solutions') https://blog.bitbadger.solutions].
|
||||
li: p.
|
||||
#[strong Kathie York]'s portfolio, formerly at #[tt /hosted/kathieyork], is now at
|
||||
#[a(href='https://hosted.djs-consulting.com/kathieyork') https://hosted.djs-consulting.com/kathieyork].
|
||||
li: p.
|
||||
#[strong Daniel J. Summers]'s personal site, formerly at #[tt /personal] (and a really ancient copy at
|
||||
#[tt /old_personal]), is now at #[a(href='https://daniel.summershome.org') https://daniel.summershome.org].
|
||||
li: p.
|
||||
The #[strong Not So Extreme Makeover: Community Edition] archive site, previously at
|
||||
#[tt /archived/notsoextreme_org], can now be found at
|
||||
#[a(href='https://hosted.djs-consulting.com/archive/notsoextreme_org') https://hosted.djs-consulting.com/archive/notsoextreme_org].
|
||||
</template>
|
||||
|
||||
<script>
|
||||
import PageTitle from './PageTitle.vue'
|
||||
|
||||
export default {
|
||||
name: 'four-oh-four',
|
||||
components: {
|
||||
PageTitle
|
||||
}
|
||||
name: 'four-oh-four'
|
||||
}
|
||||
</script>
|
||||
|
@ -1,125 +1,34 @@
|
||||
<template lang="pug">
|
||||
div.home
|
||||
article.content
|
||||
article.content.auto
|
||||
page-title(title='Welcome!')
|
||||
p.
|
||||
DJS Consulting can develop an interactive web application to fit almost any need.
|
||||
#[router-link(to='/solutions' title='All Solutions') View the complete list of our solutions!]
|
||||
p.home-lead Bit Badger Solutions develops the site you need to enable your success!
|
||||
p These solutions can take several different forms.
|
||||
h2 Process Automation and User Engagement
|
||||
p.
|
||||
Computers can be used to augment or automate nearly any process; could you think of generating bank statements,
|
||||
processing mailing lists, or tracking orders without some form of automation? We develop web-based solutions to
|
||||
automate #[em your] processes, ensuring that your business constraints are satisfied; these systems can run on the
|
||||
Internet or your private network. For Internet-facing solutions, we engineer solutions that allow them to interact
|
||||
with you securely, presented in an engaging manner. And, by "engagement," we are not describing intrusive page
|
||||
pop-ups and other #[span.strike marketing gimmicks] web annoyances; we determine an optimal user experience for
|
||||
#[em your] customers, and tailor the solution to work for both of you.
|
||||
p Several of our projects fit this description.
|
||||
ul
|
||||
li.
|
||||
#[router-link(:to="{ name: 'Application', params: { app: 'virtual-prayer-room' } }" title="Virtual Prayer Room") Virtual Prayer Room]
|
||||
helped the prayer ministry of
|
||||
#[a(href="http://www.hoffmantown.org" title="Hoffmantown Church in Albuquerque, NM") Hoffmantown Church] enable
|
||||
their prayer warriors to have access to requests wherever they are, even in their inbox once a day!
|
||||
li.
|
||||
#[router-link(:to="{ name: 'Application', params: { app: 'tcms' } }" title="TCMS") TCMS] was an application that
|
||||
helped organizations such as #[a(href="http://www.loveincabq.org") Love INC of South Albuquerque] connect people
|
||||
with needs to people who can help fulfill those needs. TCMS sprung from the
|
||||
#[a(href="http://hosted.djs-consulting.com/archive/notsoextreme_org" title="Not So Extreme Makeover: Community Edition (Archive)") Not So Extreme Makeover: Community Edition]
|
||||
in Albuquerque, New Mexico during spring break 2008; we not only developed the public presence, but a private
|
||||
system called #[router-link(:to="{ name: 'Application', params: { app: 'nsx' } }" title="NSX") NSXapp] that
|
||||
enabled the management of the volunteers, families, and things for this massive effort.
|
||||
li.
|
||||
We continue to offer
|
||||
#[router-link(:to="{ name: 'Application', params: { app: 'prayertracker' } }" title="PrayerTracker DJS Consulting") PrayerTracker],
|
||||
a free-to-use web application that helps Sunday School classes (or other small groups) generate a prayer request
|
||||
list; it provides a central place for list management and continuity.
|
||||
h2
|
||||
| Information Publicizing
|
||||
small: em (including WordPress)
|
||||
Do you have a process that requires recording the same thing multiple times? Do you have information in different
|
||||
places, but you need it all together? This solution is for you.
|
||||
#[router-link(to='/about/process-automation-solutions' title='Process Automation Solutions') Learn more about how our solutions automate processes and engage users].
|
||||
h2 Information Publicizing and Blogging
|
||||
p.
|
||||
In the early days of the World Wide Web, it was known as the "information superhighway." From its inception, the
|
||||
web's primary goal is information. The open nature of the Internet allows anyone, anywhere to say anything,
|
||||
provided they can connect a machine to the network. In fact, there are software products to handle everything
|
||||
except creating the content; all you have to bring is the ability to form a coherent thought, and type that
|
||||
thought into a box. #[a(href="https://wordpress.org" title="WordPress") WordPress] is one of the most popular
|
||||
#[abbr(title="Web Log") blog]ging platforms in use today; it allows authors to concentrate on the content of
|
||||
their websites, rather than forcing authors to turn into programmers.
|
||||
h3 Custom-Built Sites
|
||||
ul
|
||||
li.
|
||||
We developed and maintained the site for
|
||||
#[a(href="http://www.emeraldmountainchristianschool.org") Emerald Mountain Christian School] for 9 years, where
|
||||
they had information about the type of curriculum they teach, the school's 40+-year history, a calendar of
|
||||
events, and how to get more information.
|
||||
li.
|
||||
We built and maintained the site for #[a(href="http://www.summershome.org") Photography by Michelle], which had
|
||||
information, prices, and samples of the photographer's work, as well as the ability for customers to view proofs
|
||||
and make photo selections online.
|
||||
li.
|
||||
The sites for #[a(href="//bayvista.org" title="Bay Vista Baptist Church") Bay Vista Baptist Church] and
|
||||
#[a(href="//olivetbaptist.org" title="Olivet Baptist Church") Olivet Baptist Church] utilize a "static site
|
||||
generator," where the entire site is generated from source files, then served. It requires no back-end database,
|
||||
which means that the server can send them as fast as its clients can take them. These two sites even have a
|
||||
generated podcast feed! Adding content to these types of sites requires a bit more technical knowledge beyond
|
||||
"typing text in a box," but it is a great way to build ultra-fast, scalable web sites.
|
||||
li.
|
||||
This site is a single-page application (SPA) utilizing the #[a(href="//vuejs.org") Vue.js] JavaScript framework.
|
||||
The application pages are generated based on an internal data set, and the other pages are simple text
|
||||
components. Its bundling means that the initial page is small, and after the initial load, it runs entirely in
|
||||
the browser or on a phone or tablet. Sites that reference external data sets would still need to access the
|
||||
Internet to retrieve data, but this is much more efficient than having to download the entire page every single
|
||||
click. (It's even #[a(href="https://github.com/danieljsummers/djs-consulting.com") open source] if you want to
|
||||
see how we did it.)
|
||||
h3 WordPress Design, Customization, and Support
|
||||
ul
|
||||
li.
|
||||
We helped
|
||||
#[router-link(:to="{ name: 'Application', params: { app: 'cassy-fiano' } }" title="Cassy Fiano") Cassy Fiano]
|
||||
and #[a(href="http://melissablogs.com" title="Dr. Melissa Clouthier | Information Pollination") Dr.Melissa Clouthier]
|
||||
both move their blogs from Blogspot to their own domains.
|
||||
li.
|
||||
We migrated
|
||||
#[router-link(:to="{ name: 'Application', params: { app: 'liberty-pundits' } }" title="Liberty Pundits") Liberty Pundits]
|
||||
from a custom blog platform to WordPress, and set up and maintained their server, which routinely cleared
|
||||
100,000 hits per day in its prime.
|
||||
li.
|
||||
For #[a(href="//www.futilitycloset.com" title="Futility Closet") Futility Closet], we moved their site from a
|
||||
shared hosting platform to its own #[abbr(title="Virtual Private Server") VPS], to enable it to handle its
|
||||
ever-increasing traffic.
|
||||
li.
|
||||
TCMS and NSXapp both used WordPress as their front end, which also provided a public web presence that the
|
||||
customers could update themselves.
|
||||
From its inception, the Web has been about information. Do you need to get information out about an upcoming
|
||||
event? Are you wanting to start blogging, or breathe some fresh life into an existing blog? Those are but a few
|
||||
of the problems that this solution solves.
|
||||
#[router-link(to='/about/information-publicizing-solutions' title='Information Publicizing Solutions') Find out more about our information publicizing and blogging solutions]
|
||||
(including WordPress and statically-generated sites).
|
||||
h2 Web Services and APIs
|
||||
p.
|
||||
On our #[a(href="//techblog.djs-consulting.com" title="DJS Consulting Tech Blog") tech blog] you can browse the
|
||||
#[a(href="//techblog.djs-consulting.com/category/wordpress" title="WordPress | DJS Consulting Tech Blog") WordPress]
|
||||
category for information on plug-ins, and you'll find that the themes on all of the WordPress blogs linked on the
|
||||
right have been customized.
|
||||
h2 Web Services
|
||||
p.
|
||||
A web service is a way of using the Internet to provide or accept information that makes sense to computers; this
|
||||
allows other sites or applications to consume information from, or provide information to, your service. This
|
||||
enables communication between applications, without having to establish any communication channels other than the
|
||||
ones that web browsers already use. It isn't the best fit for every application, but when it is useful, it is
|
||||
#[em very] useful.
|
||||
p.
|
||||
Photography by Michelle has a web service that a desktop application utilizes to create the online proof sets
|
||||
right from the computer where the images reside. We also
|
||||
#[a(href="//techblog.djs-consulting.com/2010/4040-web-service.html" title="40/40 Web Service") wrote a service]
|
||||
for the 2010
|
||||
#[a(href="http://erlc.com/4040/" title="40/40 Prayer Vigil | Ethics and Religious Liberty Commission of the Southern Baptist Convention") 40/40 Prayer Vigil],
|
||||
which was utilized by several sites to display the current day's (or hour's) prayer focus, and
|
||||
#[a(href="//techblog.djs-consulting.com/2012/4040-web-service-for-2012.html" title="40/40 Web Service for 2012") wrote one for 2012]
|
||||
as well. #[i (As the ERLC does not host these any more, this service is no longer active.)]
|
||||
Do you have a need for multiple computers to talk to each other? Do you have an interesting data set that you want
|
||||
to make available to the public? A web service or API may be just the solution for you.
|
||||
#[router-link(to='/about/web-services-solutions' title='Web Services and API Solutions') Learn about web services, along with examples of current solutions].
|
||||
h2 Legacy Data Sharing
|
||||
p.
|
||||
Our background in mainframe applications gives us a knowledgeable perspective on retrieving information from
|
||||
older, “legacy” systems. This data can be migrated to a more modern relational or document database,
|
||||
where a web application can retrieve the information; in some cases, the data can even be exposed as a web service
|
||||
in place. These types of systems are often a great way for companies to expose their data to their customers,
|
||||
without having to move their day-to-day system from its current environment. While we currently have no active
|
||||
projects along these lines, our developers have done them in the past for other organizations; sadly, none can be
|
||||
linked publicly.
|
||||
Do you have data that's old — and by “old,” we aren’t talking “iPhone 6 old,”
|
||||
we’re talking “this data
|
||||
#[a(href='https://en.wikipedia.org/wiki/Age_of_candidacy#United_States' title='Age of Candidacy (United States) | Wikipedia') could run for President]”
|
||||
old? Just because the information is in an older “legacy” system doesn’t mean it has to stay
|
||||
there.
|
||||
#[router-link(to='/about/legacy-data' title='Legacy Data Sharing Solutions') Learn how our solutions can help get this data where you and your customers can access it more easily].
|
||||
h2 Why Web-Based?
|
||||
p.
|
||||
Developing a web-based solution has many advantages, whether that application can be used just on a local, private
|
||||
@ -135,9 +44,14 @@ div.home
|
||||
li.
|
||||
Web-based solutions are easy to implement in a step-by-step fashion, so your most critical needs can be
|
||||
addressed and deployed first. Enhancements are generally easy to do as well.
|
||||
h2 What's With the Name “Bit Badger”?
|
||||
p.
|
||||
We'd be happy to discuss your information technology needs, and how we may be able to help you. Just
|
||||
#[a(href="mailto:daniel@djs-consulting.com") e-mail us] and let us know what we can do for you!
|
||||
Link goes here
|
||||
h2 What Next
|
||||
p.
|
||||
We’d be happy to discuss your information technology needs, and which of our solutions are right for you.
|
||||
Just #[a(href='mailto:daniel@djs-consulting.com') e-mail us] and let us know what we can do for you! You can also
|
||||
#[router-link(to='/solutions' title='All Solutions') browse a complete list of our current and previous solutions].
|
||||
app-sidebar
|
||||
</template>
|
||||
|
||||
@ -155,14 +69,16 @@ export default {
|
||||
</script>
|
||||
|
||||
<style>
|
||||
.home article.content {
|
||||
margin: auto;
|
||||
}
|
||||
@media all and (min-width: 80rem) {
|
||||
.home {
|
||||
display: flex;
|
||||
flex-flow: row;
|
||||
align-items: flex-start;
|
||||
justify-content: space-around;
|
||||
}
|
||||
}
|
||||
.home-lead {
|
||||
font-size: 1.3rem;
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
|
83
src/components/about/InformationPublicizing.vue
Normal file
83
src/components/about/InformationPublicizing.vue
Normal file
@ -0,0 +1,83 @@
|
||||
<template lang="pug">
|
||||
article.content.auto
|
||||
page-title(title='Information Publicizing Solutions')
|
||||
h1 Information Publicizing and Blogging
|
||||
p.
|
||||
In the early days of the World Wide Web, it was known as the "information superhighway." From its inception, the
|
||||
web's primary goal is information. The open nature of the Internet allows anyone, anywhere to say anything,
|
||||
provided they can connect a machine to the network. In fact, there are software products to handle everything
|
||||
except creating the content; all you have to bring is the ability to form a coherent thought, and type that
|
||||
thought into a box. #[a(href='https://wordpress.org' title='WordPress') WordPress] is one of the most popular
|
||||
#[abbr(title='Web Log') blog]ging platforms in use today; it allows authors to concentrate on the content of
|
||||
their websites, rather than forcing authors to turn into programmers.
|
||||
h2 Custom-Built Sites
|
||||
ul
|
||||
li: p.
|
||||
We developed and maintained the site for
|
||||
#[a(href='http://www.emeraldmountainchristianschool.org') Emerald Mountain Christian School]
|
||||
#[small (#[router-link(:to="{ name: 'Application', params: { app: 'emerald-mountain-christian-school' } }" title='Emerald Mountain Christian School | Bit Badger Solutions') about])]
|
||||
for 9 years, where they had information about the type of curriculum they teach, the school's 40+-year history, a
|
||||
calendar of events, and how to get more information.
|
||||
li: p.
|
||||
We built and maintained the site for #[a(href='http://www.summershome.org') Photography by Michelle]
|
||||
#[small (#[router-link(:to="{ name: 'Application', params: { app: 'photography-by-michelle' } }" title='Photography by Michelle | Bit Badger Solutions') about])],
|
||||
which had information, prices, and samples of the photographer's work, as well as the ability for customers to
|
||||
view proofs and make photo selections online.
|
||||
li: p.
|
||||
The sites for #[a(href='https://bayvista.org' title='Bay Vista Baptist Church') Bay Vista Baptist Church]
|
||||
#[small (#[router-link(:to="{ name: 'Application', params: { app: 'bay-vista' } }" title='Bay Vista Baptist Church | Bit Badger Solutions') about])]
|
||||
and
|
||||
#[a(href='https://olivetbaptist.org' title='Olivet Baptist Church') Olivet Baptist Church]
|
||||
#[small (#[router-link(:to="{ name: 'Application', params: { app: 'olivet-vista' } }" title='Olivet Baptist Church | Bit Badger Solutions') about])]
|
||||
utilize a "static site generator," where the entire site is generated from source files, then served. It requires
|
||||
no back-end database, which means that the server can send them as fast as its clients can take them. These two
|
||||
sites even have a generated podcast feed! Adding content to these types of sites requires a bit more technical
|
||||
knowledge beyond "typing text in a box," but it is a great way to build ultra-fast, scalable web sites.
|
||||
li: p.
|
||||
This site is a single-page application (SPA) utilizing the #[a(href='https://vuejs.org') Vue.js] JavaScript
|
||||
framework. The application pages are generated based on an internal data set, and the other pages are simple text
|
||||
components. Its bundling means that the initial page is small, and after the initial load, it runs entirely in
|
||||
the browser or on a phone or tablet. Sites that reference external data sets would still need to access the
|
||||
Internet to retrieve data, but this is much more efficient than having to download the entire page every single
|
||||
click. (It's even #[a(href='https://github.com/danieljsummers/djs-consulting.com') open source] if you want to
|
||||
see how we did it.)
|
||||
h2 WordPress Design, Customization, and Support
|
||||
ul
|
||||
li: p.
|
||||
We helped
|
||||
#[router-link(:to="{ name: 'Application', params: { app: 'cassy-fiano' } }" title='Cassy Fiano | Bit Badger Solutions') Cassy Fiano]
|
||||
and #[a(href='http://melissablogs.com' title='Dr. Melissa Clouthier | Information Pollination') Dr.Melissa Clouthier]
|
||||
#[small (#[router-link(:to="{ name: 'Application', params: { app: 'dr-melissa-clouthier' } }" title='Dr. Melissa Clouthier | Bit Badger Solutions') about])]
|
||||
both move their blogs from Blogspot to their own domains.
|
||||
li: p.
|
||||
We migrated
|
||||
#[router-link(:to="{ name: 'Application', params: { app: 'liberty-pundits' } }" title='Liberty Pundits') Liberty Pundits]
|
||||
from a custom blog platform to WordPress, and set up and maintained their server, which routinely cleared 100,000
|
||||
hits per day in its prime.
|
||||
li: p.
|
||||
For #[a(href='https://www.futilitycloset.com' title='Futility Closet') Futility Closet]
|
||||
#[small (#[router-link(:to="{ name: 'Application', params: { app: 'futility-closet' } }" title='Futility Closet | Bit Badger Solutions') about])],
|
||||
we moved their site from a shared hosting platform to its own #[abbr(title='Virtual Private Server') VPS], to
|
||||
enable it to handle its ever-increasing traffic.
|
||||
li: p.
|
||||
#[router-link(:to="{ name: 'Application', params: { app: 'tcms' } }" title='TCMS | Bit Badger Solutions') TCMS]
|
||||
and
|
||||
#[router-link(:to="{ name: 'Application', params: { app: 'nsx' } }" title='NSXapp | Bit Badger Solutions') NSXapp]
|
||||
both used WordPress as their front end, which also provided a public web presence that the customers could update
|
||||
themselves.
|
||||
p.
|
||||
On #[em: a(href='https://blog.bitbadger.solutions' title='The Bit Badger Blog') The Bit Badger Blog] you can browse
|
||||
the
|
||||
#[a(href='https://blog.bitbadger.solutions/category/wordpress' title='WordPress | The Bit Badger Blog') WordPress]
|
||||
category for information on plug-ins, and we have supported theme customizations for nearly all of the WordPress
|
||||
sites linked on the sidebar/footer of the home page.
|
||||
p
|
||||
br
|
||||
router-link(to='/' title='Home') « Home
|
||||
</template>
|
||||
|
||||
<script>
|
||||
export default {
|
||||
name: 'information-publicizing'
|
||||
}
|
||||
</script>
|
22
src/components/about/LegacyData.vue
Normal file
22
src/components/about/LegacyData.vue
Normal file
@ -0,0 +1,22 @@
|
||||
<template lang="pug">
|
||||
article.content.auto
|
||||
page-title(title='Legacy Data Solutions')
|
||||
h1 Legacy Data Sharing
|
||||
p.
|
||||
Our background in mainframe applications gives us a knowledgeable perspective on retrieving information from
|
||||
older, “legacy” systems. This data can be migrated to a more modern relational or document database,
|
||||
where a web application can retrieve the information; in some cases, the data can even be exposed as a web service
|
||||
in place. These types of systems are often a great way for companies to expose their data to their customers,
|
||||
without having to move their day-to-day system from its current environment. While we currently have no active
|
||||
projects along these lines, our developers have done them in the past for other organizations; sadly, none can be
|
||||
linked publicly.
|
||||
p
|
||||
br
|
||||
router-link(to='/' title='Home') « Home
|
||||
</template>
|
||||
|
||||
<script>
|
||||
export default {
|
||||
name: 'legacy-data'
|
||||
}
|
||||
</script>
|
43
src/components/about/ProcessAutomation.vue
Normal file
43
src/components/about/ProcessAutomation.vue
Normal file
@ -0,0 +1,43 @@
|
||||
<template lang="pug">
|
||||
article.content.auto
|
||||
page-title(title='Process Automation Solutions')
|
||||
h1 Process Automation and User Engagement
|
||||
p.
|
||||
Computers can be used to augment or automate nearly any process; could you think of generating bank statements,
|
||||
processing mailing lists, or tracking orders without some form of automation? We develop web-based solutions to
|
||||
automate #[em your] processes, ensuring that your business constraints are satisfied; these systems can run on the
|
||||
Internet or your private network. For Internet-facing solutions, we engineer solutions that allow them to interact
|
||||
with you securely, presented in an engaging manner. And, by "engagement," we are not describing intrusive page
|
||||
pop-ups and other #[span.strike marketing gimmicks] web annoyances; we determine an optimal user experience for
|
||||
#[em your] customers, and tailor the solution to work for both of you.
|
||||
p Several of our solutions fit this description.
|
||||
ul
|
||||
li: p.
|
||||
#[router-link(:to="{ name: 'Application', params: { app: 'virtual-prayer-room' } }" title='Virtual Prayer Room | Bit Badger Solutions') Virtual Prayer Room]
|
||||
helped the prayer ministry of
|
||||
#[a(href='http://www.hoffmantown.org' title='Hoffmantown Church in Albuquerque, NM') Hoffmantown Church] enable
|
||||
their prayer warriors to have access to requests wherever they are, even in their inbox once a day!
|
||||
li: p.
|
||||
#[router-link(:to="{ name: 'Application', params: { app: 'tcms' } }" title='TCMS | Bit Badger Solutions') TCMS]
|
||||
was an application that helped organizations such as
|
||||
#[a(href='http://www.loveincabq.org') Love INC of South Albuquerque] connect people with needs to people who can
|
||||
help fulfill those needs. TCMS sprung from the
|
||||
#[a(href='http://hosted.djs-consulting.com/archive/notsoextreme_org' title='Not So Extreme Makeover: Community Edition (Archive)') Not So Extreme Makeover: Community Edition]
|
||||
in Albuquerque, New Mexico during spring break 2008; we not only developed the public presence, but a private
|
||||
system called #[router-link(:to="{ name: 'Application', params: { app: 'nsx' } }" title='NSXapp | Bit Badger Solutions') NSXapp]
|
||||
that enabled the management of the volunteers, families, and things for this massive effort.
|
||||
li: p.
|
||||
We continue to offer #[a(href='https://prayer.djs-consulting.com' title='PrayerTracker') PrayerTracker]
|
||||
#[small (#[router-link(:to="{ name: 'Application', params: { app: 'prayer-tracker' } }" title='PrayerTracker | Bit Badger Solutions') about])],
|
||||
a free-to-use web application that helps Sunday School classes (or other small groups) generate a prayer request
|
||||
list; it provides a central place for list management and continuity.
|
||||
p
|
||||
br
|
||||
router-link(to='/' title='Home') « Home
|
||||
</template>
|
||||
|
||||
<script>
|
||||
export default {
|
||||
name: 'process-automation'
|
||||
}
|
||||
</script>
|
37
src/components/about/WebServices.vue
Normal file
37
src/components/about/WebServices.vue
Normal file
@ -0,0 +1,37 @@
|
||||
<template lang="pug">
|
||||
div
|
||||
page-title(title='Web Services and API Solutions')
|
||||
h1 Web Services and APIs
|
||||
article.content.auto
|
||||
p.
|
||||
A web service is a way of using the Internet to provide or accept information that makes sense to computers; this
|
||||
allows other sites or applications to consume information from, or provide information to, your service. This
|
||||
enables communication between applications, without having to establish any communication channels other than the
|
||||
ones that web browsers already use. It isn't the best fit for every application, but when it is useful, it is
|
||||
#[em very] useful.
|
||||
p.
|
||||
An #[abbr(title='Application Programming Interface') API] can be a synonym for a web service, but it can also be
|
||||
a generally accessible way of providing data. For example, Twitter has a public API, which other applications can
|
||||
use to display tweets on their site.
|
||||
ul
|
||||
li: p.
|
||||
#[router-link(:to="{ name: 'Application', params: { app: 'photography-by-michelle' } }" title='Photography by Michelle | Bit Badger Solutions') Photography by Michelle]
|
||||
had a private web API that a desktop application utilized to create the online proof sets right from the
|
||||
computer where the images resided.
|
||||
li: p.
|
||||
We
|
||||
#[a(href='https://blog.bitbadger.solutions/2010/4040-web-service.html' title='40/40 Web Service | The Bit Badger Blog') wrote a service]
|
||||
for the 2010
|
||||
#[a(href='http://erlc.com/4040/' title='40/40 Prayer Vigil | Ethics and Religious Liberty Commission of the Southern Baptist Convention') 40/40 Prayer Vigil],
|
||||
which was utilized by several sites to display the current day's (or hour's) prayer focus, and
|
||||
#[a(href='https://blog.bitbadger.solutions/2012/4040-web-service-for-2012.html' title='40/40 Web Service for 2012 | The Bit Badger Blog') wrote one for 2012]
|
||||
as well. #[i (As the ERLC does not host these any more, this service is no longer active.)]
|
||||
li: p.
|
||||
#[a(href='https://prayerjournal.me') myPrayerJournal]
|
||||
#[small (#[router-link(:to="{ name: 'Application', params: { app: 'my-prayer-journal' } }" title='myPrayerJournal | Bit Badger Solutions') about])]
|
||||
is a #[abbr(title='Single Page Application') SPA] which only downloads the structure of the site the first time
|
||||
you go there, then utilizes a stateless API to access data from the browser.
|
||||
p
|
||||
br
|
||||
router-link(to='/' title='Home') « Home
|
||||
</template>
|
@ -1,11 +1,15 @@
|
||||
// The Vue build version to load with the `import` command
|
||||
// (runtime-only or standalone) has been set in webpack.base.conf with an alias.
|
||||
import Vue from 'vue'
|
||||
|
||||
import App from './App'
|
||||
import router from './router'
|
||||
import PageTitle from './components/PageTitle'
|
||||
|
||||
Vue.config.productionTip = false
|
||||
|
||||
Vue.component('page-title', PageTitle)
|
||||
|
||||
/* eslint-disable no-new */
|
||||
new Vue({
|
||||
el: '#app',
|
||||
|
@ -1,10 +1,13 @@
|
||||
import Vue from 'vue'
|
||||
import Router from 'vue-router'
|
||||
|
||||
import Home from '@/components/Home'
|
||||
import Application from '@/components/Application'
|
||||
import ApplicationList from '@/components/ApplicationList'
|
||||
import FourOhFour from '@/components/FourOhFour'
|
||||
import Home from '@/components/Home'
|
||||
import InformationPublicizing from '@/components/about/InformationPublicizing'
|
||||
import ProcessAutomation from '@/components/about/ProcessAutomation'
|
||||
import WebServices from '@/components/about/WebServices'
|
||||
|
||||
Vue.use(Router)
|
||||
|
||||
@ -12,6 +15,9 @@ export default new Router({
|
||||
mode: 'history',
|
||||
routes: [
|
||||
{ path: '/', name: 'Home', component: Home },
|
||||
{ path: '/about/information-publicizing-solutions', name: 'InformationPublicizing', component: InformationPublicizing },
|
||||
{ path: '/about/process-automation-solutions', name: 'ProcessAutomation', component: ProcessAutomation },
|
||||
{ path: '/about/web-services-solutions', name: 'WebServices', component: WebServices },
|
||||
{ path: '/solutions/:app', name: 'Application', component: Application, props: true },
|
||||
{ path: '/solutions', name: 'ApplicationList', component: ApplicationList },
|
||||
{ path: '*', name: 'FourOhFour', component: FourOhFour }
|
||||
|
Loading…
Reference in New Issue
Block a user